Re: PO files FAQ
Hi, I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: 1) Not always LANG variable works. Sometimes is necessary to use another variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx 2) In order to test the translation it is necessary to test if the language use to make the translation is accepted by lyx. I.e. if the language is in the text file languages. 3) If the language used to make the translation is in the text file languages, it is not necessary to compile lyx. In this case is enough to compile the po file, with the command msgfmt that is part of the gettext packet. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html http://gnuwin32.sourceforge.net/packages/gettext.htm Bye Ramon
Re: PO files FAQ
I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: the best would be if you get file from svn http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization and write the patch with your comments against that file. i was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. pavel
Re: PO files FAQ
On Mon, 5 Mar 2007, Pavel Sanda wrote: I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: the best would be if you get file from svn http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization and write the patch with your comments against that file. i was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. What page? It's possible to automatically have the wiki page embed something from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
What page? It's possible to automatically have the wiki page embed something from SVN. http://wiki.lyx.org/Devel/POFAQ pavel
Re: PO files FAQ
Am Montag, 5. März 2007 20:34 schrieb Ramon Flores: Hi, I think it is a very good idea to write this FAQ, and to put it in the wiki. That would be the fourth place where this is documented. Please have a look at this bug: http://bugzilla.lyx.org/show_bug.cgi?id=3314 So I would like to make some comments: 1) Not always LANG variable works. Sometimes is necessary to use another variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx That should be filed as a mandriva bug. It should not be needed to set KDE_LANG. Only setting LANG (or LC_MESSAGES or LC_ALL) should work. Georg
Re: PO files FAQ
On Mon, 5 Mar 2007, Pavel Sanda wrote: What page? It's possible to automatically have the wiki page embed something from SVN. http://wiki.lyx.org/Devel/POFAQ I added this code to the wiki page white-space=pre background-color=#ee (:includesvn README.localization :) The wiki page now embeds the latest version from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
Hi, I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: 1) Not always LANG variable works. Sometimes is necessary to use another variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx 2) In order to test the translation it is necessary to test if the language use to make the translation is accepted by lyx. I.e. if the language is in the text file "languages". 3) If the language used to make the translation is in the text file "languages", it is not necessary to compile lyx. In this case is enough to compile the po file, with the command "msgfmt" that is part of the gettext packet. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html http://gnuwin32.sourceforge.net/packages/gettext.htm Bye Ramon
Re: PO files FAQ
> I think it is a very good idea to write this FAQ, and to put it in the wiki. > > So I would like to make some comments: the best would be if you get file from svn http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization and write the patch with your comments against that file. i was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. pavel
Re: PO files FAQ
On Mon, 5 Mar 2007, Pavel Sanda wrote: I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: the best would be if you get file from svn http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization and write the patch with your comments against that file. i was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. What page? It's possible to automatically have the wiki page embed something from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
> What page? It's possible to automatically have the wiki page embed > something from SVN. http://wiki.lyx.org/Devel/POFAQ pavel
Re: PO files FAQ
Am Montag, 5. März 2007 20:34 schrieb Ramon Flores: > Hi, > > I think it is a very good idea to write this FAQ, and to put it in the wiki. That would be the fourth place where this is documented. Please have a look at this bug: http://bugzilla.lyx.org/show_bug.cgi?id=3314 > So I would like to make some comments: > > 1) Not always LANG variable works. Sometimes is necessary to use another > variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, > and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: > a) KDE_LANG=xx_CC lyx > b) LC_ALL=xx_CC lyx That should be filed as a mandriva bug. It should not be needed to set KDE_LANG. Only setting LANG (or LC_MESSAGES or LC_ALL) should work. Georg
Re: PO files FAQ
On Mon, 5 Mar 2007, Pavel Sanda wrote: What page? It's possible to automatically have the wiki page embed something from SVN. http://wiki.lyx.org/Devel/POFAQ I added this code to the wiki page >>white-space=pre background-color=#ee<< (:includesvn README.localization :) >><< The wiki page now embeds the latest version from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
I wrote a small FAQ for the po files. I would be glad if someone could have a glance at i made small changes. see attached patch. pavel --- PO FAQ 2007-02-24 14:37:44.0 +0100 +++ PO FAQ.new 2007-02-24 14:38:38.0 +0100 @@ -10,9 +10,12 @@ 1) WHERE DO I START? The file you need to edit it an xx.po file where xx stands for your language's two letter -code. German would be for example de.po and Polish pl.po. -If you want to start from scratch than you should obtain a copy of the lyx.pot file. +code. For list of country codes look at: +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 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? @@ -23,18 +26,17 @@ many tools to assist the translator. - 3) WHAT I NEED TO TRANSLATE? If your using a simple text editor you should translate the strings that appear in the msgid line -and write the translation into the msgstr line. You can also add #, fuzzy in order to mark a -translation as fuzzy. It is recommended that you would take a look at another .po file - that -way you can get an idea of what to do. -If your using a specialized po editor then you will see in it the untranslated strings and a +and write the translation into the msgstr line. Note that #, fuzzy line is just a hint +for translation from compiler - in order to get the translation of the current item working +you have to delete this line. It is recommended that you would take a look at another .po file - +that way you can get an idea of what to do. +If you are using a specialized po editor then you will see in it the untranslated strings and a place to write your translation for them. - 4) WHAT SHOULD I DO WITH THE '', '|', '$, AND '%' CHARACTERS? '' stands for underlined characters (shortcut) in dialog boxes. @@ -46,30 +48,36 @@ and resolve possible conflicts of the same shortcut chars in one menu... - 5) WHAT IS pocheck.pl AND HOW DO I USE IT? This is a small script located in the PO directory of the source that helps you find common errors in your translation. In order to use this script you have to have perl. -6) HOW CAN I TEST MY TRANSLATION? +6) HOW CAN I TEST MY TRANSLATION? In order to test your translation you need to obtain the LyX source (from the SVN) and replace the existing .po with yours. Afterwards, you should compile and install (if you don't install it won't work) LyX (check the INSTALL file for your OS). -Now, run LyX using the appropriate LANG variable: +For running LyX with your translation, use the appropriate LANG variable: In Linux: LANG=xx_CC lyx In MS Windows you need to change the bat file and write: set LANG=xx_CC xx stands for your language code. CC stands for your country code. +Most comfortable way to see your updated translation during the editation, is running(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 +For basic idea how the translation works you can look http://en.wikipedia.org/wiki/Gettext . +Just for detailed reference you can look at http://www.gnu.org/software/gettext/manual/gettext.html . Written by Ran Rutenberg 2007 -I greatly appreciate all those who helped me and assisted me in this subject. \ No newline at end of file +I greatly appreciate all those who helped me and assisted me in this subject.
Re: PO files FAQ
Uwe Stöhr a écrit : JMarc, could this also be added to branch? Yes, as soon as it has stabilized on trunk. Thanks for doing it Ran. JMarc
Re: PO files FAQ
Ran: It looks fine but there are a a few things I would consider to change in the patch: ran, maybe you can get in touch with diff and patch comands, you'll need it in the future for sure :) e.g.: diff -u README.localization README.localization.new updates.txt or cat updates.txt |patch ... i know ... winning the price for misusing cat :) Uwe: But not everything. Provide a patch to the current version: http://www.lyx.org/trac/browser/lyx-devel/trunk/README.po-files and I will commit this immediately. ok, attached patch including remarks from ran. pavel --- README.localization 2007-02-24 18:50:42.0 +0100 +++ README.localization.new 2007-02-24 19:09:09.0 +0100 @@ -18,8 +18,10 @@ 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 -file. +If you want to start from scratch then you should obtain a copy of the lyx.pot +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? @@ -33,14 +35,14 @@ 3) WHAT DO I NEED TO TRANSLATE? -If your using a simple text editor you should translate the strings that appear -in the msgid line and write the translation into the msgstr line. Note that a -#, fuzzy line is just a hint for translation from compiler - in order to get -the translation of the current item working you have to delete this line. It is -recommended that you would take a look at another .po file - that way you can -get an idea of what to do. If your using a specialized po editor then you will -see in it the untranslated strings and a place to write your translation for -them. +If you are using a simple text editor you should translate the strings that +appear in the msgid line and write the translation into the msgstr line. Note +that a #, fuzzy line is just a hint for translation from compiler - in order +to get the translation of the current item working you have to delete this +line. It is recommended that you would take a look at another .po file - that +way you can get an idea of what to do. If your using a specialized po editor +then you will see in it the untranslated strings and a place to write your +translation for them. 4) WHAT SHOULD I DO WITH THE '', '|', '$, AND '%' CHARACTERS? @@ -70,7 +72,7 @@ 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 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: On Linux: LANG=xx_CC lyx @@ -79,6 +81,13 @@ xx stands for your language code. CC stands for your country code. So to get, 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 For some basic idea on how the translation works, you can look at
Re: PO files FAQ
On Sat, 24 Feb 2007, Jean-Marc Lasgouttes wrote: Uwe Stöhr a écrit : JMarc, could this also be added to branch? Yes, as soon as it has stabilized on trunk. As Ran had put the text here initially, http://wiki.lyx.org/Devel/POFAQ I simply added a link from that page into the SVN repository. No need to delete anything. However, if the name of the page is modified, please fix the link or ask me to fix the link. (Personally I like README.localization). cheers /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
> I wrote a small FAQ for the po files. I would be glad if someone could > have a glance at i made small changes. see attached patch. pavel --- PO FAQ 2007-02-24 14:37:44.0 +0100 +++ PO FAQ.new 2007-02-24 14:38:38.0 +0100 @@ -10,9 +10,12 @@ 1) WHERE DO I START? The file you need to edit it an xx.po file where xx stands for your language's two letter -code. German would be for example de.po and Polish pl.po. -If you want to start from scratch than you should obtain a copy of the lyx.pot file. +code. For list of country codes look at: +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 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? @@ -23,18 +26,17 @@ many tools to assist the translator. - 3) WHAT I NEED TO TRANSLATE? If your using a simple text editor you should translate the strings that appear in the msgid line -and write the translation into the msgstr line. You can also add "#, fuzzy" in order to mark a -translation as fuzzy. It is recommended that you would take a look at another .po file - that -way you can get an idea of what to do. -If your using a specialized po editor then you will see in it the untranslated strings and a +and write the translation into the msgstr line. Note that "#, fuzzy" line is just a hint +for translation from compiler - in order to get the translation of the current item working +you have to delete this line. It is recommended that you would take a look at another .po file - +that way you can get an idea of what to do. +If you are using a specialized po editor then you will see in it the untranslated strings and a place to write your translation for them. - 4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS? '&' stands for underlined characters (shortcut) in dialog boxes. @@ -46,30 +48,36 @@ and resolve possible conflicts of the same shortcut chars in one menu... - 5) WHAT IS pocheck.pl AND HOW DO I USE IT? This is a small script located in the PO directory of the source that helps you find common errors in your translation. In order to use this script you have to have perl. -6) HOW CAN I TEST MY TRANSLATION? +6) HOW CAN I TEST MY TRANSLATION? In order to test your translation you need to obtain the LyX source (from the SVN) and replace the existing .po with yours. Afterwards, you should compile and install (if you don't install it won't work) LyX (check the INSTALL file for your OS). -Now, run LyX using the appropriate LANG variable: +For running LyX with your translation, use the appropriate LANG variable: In Linux: LANG=xx_CC lyx In MS Windows you need to change the bat file and write: set LANG=xx_CC xx stands for your language code. CC stands for your country code. +Most comfortable way to see your updated translation during the editation, is running(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 +For basic idea how the translation works you can look http://en.wikipedia.org/wiki/Gettext . +Just for detailed reference you can look at http://www.gnu.org/software/gettext/manual/gettext.html . Written by Ran Rutenberg 2007 -I greatly appreciate all those who helped me and assisted me in this subject. \ No newline at end of file +I greatly appreciate all those who helped me and assisted me in this subject.
Re: PO files FAQ
Uwe Stöhr a écrit : JMarc, could this also be added to branch? Yes, as soon as it has stabilized on trunk. Thanks for doing it Ran. JMarc
Re: PO files FAQ
>Ran: >It looks fine but there are a a few things I would consider to change in the >patch: ran, maybe you can get in touch with diff and patch comands, you'll need it in the future for sure :) e.g.: "diff -u README.localization README.localization.new > updates.txt" or "cat updates.txt |patch" ... i know ... winning the price for misusing cat :) > Uwe: > But not everything. Provide a patch to the current version: > http://www.lyx.org/trac/browser/lyx-devel/trunk/README.po-files > and I will commit this immediately. ok, attached patch including remarks from ran. pavel --- README.localization 2007-02-24 18:50:42.0 +0100 +++ README.localization.new 2007-02-24 19:09:09.0 +0100 @@ -18,8 +18,10 @@ 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 -file. +If you want to start from scratch then you should obtain a copy of the lyx.pot +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? @@ -33,14 +35,14 @@ 3) WHAT DO I NEED TO TRANSLATE? -If your using a simple text editor you should translate the strings that appear -in the msgid line and write the translation into the msgstr line. Note that a -"#, fuzzy" line is just a hint for translation from compiler - in order to get -the translation of the current item working you have to delete this line. It is -recommended that you would take a look at another .po file - that way you can -get an idea of what to do. If your using a specialized po editor then you will -see in it the untranslated strings and a place to write your translation for -them. +If you are using a simple text editor you should translate the strings that +appear in the msgid line and write the translation into the msgstr line. Note +that a "#, fuzzy" line is just a hint for translation from compiler - in order +to get the translation of the current item working you have to delete this +line. It is recommended that you would take a look at another .po file - that +way you can get an idea of what to do. If your using a specialized po editor +then you will see in it the untranslated strings and a place to write your +translation for them. 4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS? @@ -70,7 +72,7 @@ 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 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: On Linux: LANG=xx_CC lyx @@ -79,6 +81,13 @@ xx stands for your language code. CC stands for your country code. So to get, 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 For some basic idea on how the translation works, you can look at
Re: PO files FAQ
On Sat, 24 Feb 2007, Jean-Marc Lasgouttes wrote: Uwe Stöhr a écrit : JMarc, could this also be added to branch? Yes, as soon as it has stabilized on trunk. As Ran had put the text here initially, http://wiki.lyx.org/Devel/POFAQ I simply added a link from that page into the SVN repository. No need to delete anything. However, if the name of the page is modified, please fix the link or ask me to fix the link. (Personally I like README.localization). cheers /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
