Add Benjamin Piwowarski to contributors. Welcome to LyX!

[lyx.git] / README.localization

diff --git a/README.localization b/README.localization
index a3b57f84c2a3eab9f18005d7dbdc81992fa8c596..c0e1a031ef6112c748ed620a27fd1ff6ce0acbbf 100644 (file)
--- a/README.localization
+++ b/README.localization
@@ -29,7 +29,7 @@ There are basically two source trees you can start to work with - trunk
 (development version) and branch (stable version). Unless the development
 version is shortly before release it is better idea to start your translating
 work on the stable version. If you have no idea how to get those trees you
-can follow http://www.lyx.org/HowToUseSVN page.
+can follow http://www.lyx.org/HowToUseGIT page.
 
 
 2) HOW DO I EDIT PO FILES?
@@ -115,7 +115,7 @@ files run make update-po.
 
 Send your edited xx.po file to po-updates@lyx.org.
 
-Also you can check http://www.lyx.org/trac/browser/lyx-devel/trunk to track
+Also you can check http://www.lyx.org/trac/browser/lyxgit/?rev=master to track
 changes or watch updates.
 
 
@@ -162,3 +162,12 @@ lib/examples/localization_test.lyx in LyX and read its instructions.
 The problematic strings can be then fixed in the .po file. For inspiration the
 typical places in .po files, where to fix the translation, can be seen on the
 following commit: http://www.lyx.org/trac/changeset/38169 .
+
+If you need to manually regenerate layouttranslations file from .po files run
+`make ../lib/layouttranslations' in po directory. Python polib library is
+needed for building the output file.
+
+Q: Running make ../lib/layouttranslations return with just saying
+   ../lib/layouttranslations is up to date.
+A: To force regerenation, use something like (XX is your language)
+   make -W XX.po ../lib/layouttranslations