anne/lyx_mirror
1
0
Fork 0
mirror of https://git.lyx.org/repos/lyx.git synced 2024-11-22 01:59:02 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

README.localization: updates from Pavel Sanda

Browse Source 
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@17394 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
Uwe Stöhr 2007-03-02 21:48:13 +00:00
parent 4f4c5d4954
commit 71e1fe570b
1 changed files with 20 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.localization
View File

@ -18,8 +18,10 @@ of country codes look at:
http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC222 http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC222
If you want to start from scratch than you should obtain a copy of the lyx.pot If you want to start from scratch then you should obtain a copy of the lyx.pot
file. and name it after your language. German would be for example de.po and Polish
pl.po. This file is generated in the "po" directory of the source tree during
the compilation.
2) HOW DO I EDIT PO FILES? 2) HOW DO I EDIT PO FILES?
@ -33,14 +35,14 @@ as they have many tools to assist the translator.
3) WHAT DO I NEED TO TRANSLATE? 3) WHAT DO I NEED TO TRANSLATE?
If your using a simple text editor you should translate the strings that appear If you are using a simple text editor you should translate the strings that
in the msgid line and write the translation into the msgstr line. Note that a appear in the msgid line and write the translation into the msgstr line. Note
"#, fuzzy" line is just a hint for translation from compiler - in order to get that a "#, fuzzy" line is just a hint for translation from compiler - in order
the translation of the current item working you have to delete this line. It is to get the translation of the current item working you have to delete this
recommended that you would take a look at another .po file - that way you can line. It is recommended that you would take a look at another .po file - that
get an idea of what to do. If your using a specialized po editor then you will way you can get an idea of what to do. If your using a specialized po editor
see in it the untranslated strings and a place to write your translation for then you will see in it the untranslated strings and a place to write your
them. translation for them.
4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS? 4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS?
@ -70,7 +72,7 @@ to have the script language Perl installed.
In order to test your translation you need to obtain the LyX sources (from the In order to test your translation you need to obtain the LyX sources (from the
SVN repository) and replace the existing .po with yours. Afterwards, you should SVN repository) and replace the existing .po with yours. Afterwards, you should
compile and install LyX (check the INSTALL file for your OS). If you don't compile and install LyX (check the INSTALL file for your OS). If you don't
install LyX it won't work. For running LyX with your translation, use the install LyX it won't work. In order to run LyX with your translation, use the
appropriate LANG variable: appropriate LANG variable:
On Linux: LANG=xx_CC lyx On Linux: LANG=xx_CC lyx
@ -79,6 +81,13 @@ appropriate LANG variable:
xx stands for your language code. CC stands for your country code. So to get, xx stands for your language code. CC stands for your country code. So to get,
e.g., Czech, the code is "cs_CZ". e.g., Czech, the code is "cs_CZ".
The most comfortable way to see your updated translation while editing, is
running (in linux):
1. "make xx.po" in po directory to compile updated xx.po translation
2. "make install" in root lyx tree to copy xx.gmo into the appropriate location
(or do it by hand...)
7) REFERENCES 7) REFERENCES
For some basic idea on how the translation works, you can look at For some basic idea on how the translation works, you can look at