forgot this in previous revision.

[lyx.git] / README.localization

diff --git a/README.localization b/README.localization
index f3db12bf7de16420cff70b98e78b31c61fc92c78..89b0645a5e01bcdcbfadaefce4905ba50b7e2bdd 100644 (file)
--- a/README.localization
+++ b/README.localization
@@ -12,7 +12,7 @@ and dialog items, console messages) into their native language.
 
 1) WHERE DO I START?
 
-The file you need to edit it an xx.po file where xx stands for your language's
+The file you need to edit is an xx.po file where xx stands for your language's
 two letter code. For a list of languages codes look at:
 
   http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#Language-Codes
@@ -59,8 +59,8 @@ These chars should be somehow used in your translations, however you'll have to
 invent your own working shortcuts for dialog and menu entries and resolve 
 possible conflicts of the same shortcut chars in one menu... 
 
-Note also that there are already used global shortcuts (such as p k x c m s) and
-you should avoid to use these characters for first-level menu shortcuts.
+Note also that there are already used global shortcuts (such as p k x c m s a)
+and you should avoid to use these characters for first-level menu shortcuts.
 
 '$' and '%' are usually used as handlers for formatting or variables to be 
 inserted into the strings. Character sequences like %1$s or %1$d MUST also 
@@ -115,7 +115,14 @@ Also you can check http://www.lyx.org/trac/browser/lyx-devel/trunk to track
 changes or watch updates.
 
 
-8) REFERENCES
+8) SHALL ALL THE UNUSED STRINGS AT THE BOTTOM OF .PO FILE BE REMOVED,
+   OR SHALL THEY STAY?
+
+As you wish. They can be reused for generating fuzzy hints, when completely
+new strings appear, no other function.
+
+
+9) REFERENCES
 
 For some basic idea on how the translation works, you can look at