Re: Fwd: readme updates
Pavel == Pavel Sanda [EMAIL PROTECTED] writes: Pavel Sanda schrieb: For the patch to readme.localization, could you please send this as separate patch to the devel list for approval. i wonder what is this list for then :) I'm only unsure if I'm allowed to commit anything else than docs and po files because of the release freeze we are in. Your changes are reasonable I just want to have the OK from someone else. regards Uwe Pavel please see the attached patch pavel Looks good to me except maybe: - On Linux: LANG=xx_CC lyx + On Linux: export LANG=xx_CC lyx I do not thing the 'export' is needed. Does it change something for you? (when typing all in the same line) JMarc
Re: Fwd: readme updates
Looks good to me except maybe: - On Linux: LANG=xx_CC lyx + On Linux: export LANG=xx_CC lyx I do not thing the 'export' is needed. Does it change something for you? (when typing all in the same line) $ unset LANG $ lyx -english menus $ LANG=cs_CZ $ lyx -english menus $ export LANG=cs_CZ $ lyx -czech menus pavel
Re: Fwd: readme updates
Pavel Sanda wrote: $ unset LANG $ lyx -english menus $ LANG=cs_CZ $ lyx -english menus $ export LANG=cs_CZ $ lyx -czech menus $ LANG=cs_CZ lyx -czech menus Jürgen
Re: Fwd: readme updates
(when typing all in the same line) bah, i should be more attentive. sorry. fixed patch attached. pavel Index: README.localization === --- README.localization (revision 19005) +++ README.localization (working copy) @@ -14,9 +14,9 @@ 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. For a list -of country codes look at: +of languages 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#Language-Codes 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 @@ -40,7 +40,7 @@ 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 +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. @@ -83,17 +83,38 @@ 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 +1. make xx.gmo in the 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...) +For advanced users - if you want to remerge your files against current source +files run make update-po. -7) REFERENCES +7) HOW TO CONTRIBUTE MY WORK? + +You can manually use diff utility to make patch; usually the most comfortable +way is to run something like (after you edit xx.po): + + svn diff xx.po xx.po.patch + +This file should be sent to [EMAIL PROTECTED] + +Also you can check http://www.lyx.org/trac/browser/lyx-devel/trunk to track +changes or watch updates. + + +8) REFERENCES + For some basic idea on how the translation works, you can look at http://en.wikipedia.org/wiki/Gettext -For detailed reference, have a look at +For detailed reference (including full list of country and language codes), +have a look at http://www.gnu.org/software/gettext/manual/gettext.html + + +Consider subscribing to the documentation list at [EMAIL PROTECTED] (rather +silent one) or developer's mailing list lyx-devel@lists.lyx.org (high volume).Index: po/README === --- po/README (revision 19005) +++ po/README (working copy) @@ -1,56 +1,3 @@ -This file is intended to provide information about the different translation -files. If you want to make one for your language, please read -Help-Customization for more information, and the information below. - -How can I update an existing po file? -- - -It requires a bit of work to get started, but once you are set up, -the procedure should be relatively easy: - -1) Getting ready - -Get and install gettext (available from ftp://alpha.gnu.org). Read the -documentation for gettext. Then get the latest LyX distribution including -patches, and unpack it in your home directory. It is yet better if you checkout -the CVS version of LyX. -Read the README in the LyX distribution. -Check the mailing list archives to learn what is going on at the moment. -Consider subscribing to the developer's mailing list, [EMAIL PROTECTED] - -2) Preparing a patch - -Now do (where XX stands for the code of your language): - -cp -R lyx-*.*.* lyx.new - (Which makes a copy of the source distribution for -you to change, but you should work in a CVS workarea) - cd lyx.new/po/ - - make XX.pox - (It merges the po file into the temporary file XX.pox) -emacs XX.pox - (Using po-mode. Emacs is convenient for po editing, but not -mandatory.) - (Make all necessary changes in XX.pox, and save.) -mv XX.pox XX.po -rm XX.pox~ - (To remove Emacs autosave.) - make XX.gmo - (Update the ChangeLog file.) - - cd .. - - (Maybe update lib/CREDITS) - - cvs diff -u XX_po_update.patch - (Or whatever good method to have a patch in unified diff format) - -3) Submitting the patch - - Check your patch and mail it to lyx-devel@lists.lyx.org - -Thanks! - -The LyX Team. - +If you want to make translation for your language, please read +Help-Customization for more information, and the information +in
Re: Fwd: readme updates
On Mon, Jul 09, 2007 at 01:01:21PM +0200, Jean-Marc Lasgouttes wrote: Pavel == Pavel Sanda [EMAIL PROTECTED] writes: Pavel Sanda schrieb: For the patch to readme.localization, could you please send this as separate patch to the devel list for approval. i wonder what is this list for then :) I'm only unsure if I'm allowed to commit anything else than docs and po files because of the release freeze we are in. Your changes are reasonable I just want to have the OK from someone else. regards Uwe Pavel please see the attached patch pavel Looks good to me except maybe: - On Linux: LANG=xx_CC lyx + On Linux: export LANG=xx_CC lyx I do not thing the 'export' is needed. Does it change something for you? (when typing all in the same line) I would use env in place of export, such that it works whatever the shell used. -- Enrico
Re: Fwd: readme updates
> "Pavel" == Pavel Sanda <[EMAIL PROTECTED]> writes: >> Pavel Sanda schrieb: >> >> >>For the patch to readme.localization, could you please send this >> as >>separate patch to the devel list for approval. >> > >> >i wonder what is this list for then :) >> >> I'm only unsure if I'm allowed to commit anything else than docs >> and po files because of the release freeze we are in. Your changes >> are reasonable I just want to have the OK from someone else. >> >> regards Uwe Pavel> please see the attached patch pavel Looks good to me except maybe: - On Linux: LANG=xx_CC lyx + On Linux: export LANG=xx_CC lyx I do not thing the 'export' is needed. Does it change something for you? (when typing all in the same line) JMarc
Re: Fwd: readme updates
> Looks good to me except maybe: > > - On Linux: LANG=xx_CC lyx > + On Linux: export LANG=xx_CC lyx > > I do not thing the 'export' is needed. Does it change something for > you? (when typing all in the same line) $ unset LANG $ lyx ->english menus $ LANG=cs_CZ $ lyx ->english menus $ export LANG=cs_CZ $ lyx ->czech menus pavel
Re: Fwd: readme updates
Pavel Sanda wrote: > $ unset LANG > $ lyx > ->english menus > $ LANG=cs_CZ > $ lyx > ->english menus > $ export LANG=cs_CZ > $ lyx > ->czech menus $ LANG=cs_CZ lyx ->czech menus Jürgen
Re: Fwd: readme updates
> > (when typing all in the same line) bah, i should be more attentive. sorry. fixed patch attached. pavel Index: README.localization === --- README.localization (revision 19005) +++ README.localization (working copy) @@ -14,9 +14,9 @@ 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. For a list -of country codes look at: +of languages 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#Language-Codes 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 @@ -40,7 +40,7 @@ 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 +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. @@ -83,17 +83,38 @@ 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 +1. "make xx.gmo" in the 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...) +For advanced users - if you want to remerge your files against current source +files run make update-po. -7) REFERENCES +7) HOW TO CONTRIBUTE MY WORK? + +You can manually use diff utility to make patch; usually the most comfortable +way is to run something like (after you edit xx.po): + + svn diff xx.po > xx.po.patch + +This file should be sent to [EMAIL PROTECTED] + +Also you can check http://www.lyx.org/trac/browser/lyx-devel/trunk to track +changes or watch updates. + + +8) REFERENCES + For some basic idea on how the translation works, you can look at http://en.wikipedia.org/wiki/Gettext -For detailed reference, have a look at +For detailed reference (including full list of country and language codes), +have a look at http://www.gnu.org/software/gettext/manual/gettext.html + + +Consider subscribing to the documentation list at [EMAIL PROTECTED] (rather +silent one) or developer's mailing list lyx-devel@lists.lyx.org (high volume).Index: po/README === --- po/README (revision 19005) +++ po/README (working copy) @@ -1,56 +1,3 @@ -This file is intended to provide information about the different translation -files. If you want to make one for your language, please read -"Help->Customization" for more information, and the information below. - -How can I update an existing po file? -- - -It requires a bit of work to get started, but once you are set up, -the procedure should be relatively easy: - -1) Getting ready - -Get and install gettext (available from ftp://alpha.gnu.org). Read the -documentation for gettext. Then get the latest LyX distribution including -patches, and unpack it in your home directory. It is yet better if you checkout -the CVS version of LyX. -Read the README in the LyX distribution. -Check the mailing list archives to learn what is going on at the moment. -Consider subscribing to the developer's mailing list, [EMAIL PROTECTED] - -2) Preparing a patch - -Now do (where XX stands for the code of your language): - -cp -R lyx-*.*.* lyx.new - (Which makes a copy of the source distribution for -you to change, but you should work in a CVS workarea) - cd lyx.new/po/ - - make XX.pox - (It merges the po file into the temporary file XX.pox) -emacs XX.pox - (Using po-mode. Emacs is convenient for po editing, but not -mandatory.) - (Make all necessary changes in XX.pox, and save.) -mv XX.pox XX.po -rm XX.pox~ - (To remove Emacs autosave.) - make XX.gmo - (Update the ChangeLog file.) - - cd .. - - (Maybe update lib/CREDITS) - - cvs diff -u > XX_po_update.patch - (Or whatever good method to have a patch in unified diff format) - -3) Submitting the patch - - Check your patch and mail it to lyx-devel@lists.lyx.org - -Thanks! - -The LyX Team. - +If you want to make translation for your language, please read +"Help->Customization" for more information, and the information
Re: Fwd: readme updates
On Mon, Jul 09, 2007 at 01:01:21PM +0200, Jean-Marc Lasgouttes wrote: > > "Pavel" == Pavel Sanda <[EMAIL PROTECTED]> writes: > > >> Pavel Sanda schrieb: > >> > >> >>For the patch to readme.localization, could you please send this > >> as >>separate patch to the devel list for approval. > >> > > >> >i wonder what is this list for then :) > >> > >> I'm only unsure if I'm allowed to commit anything else than docs > >> and po files because of the release freeze we are in. Your changes > >> are reasonable I just want to have the OK from someone else. > >> > >> regards Uwe > > Pavel> please see the attached patch pavel > > Looks good to me except maybe: > > - On Linux: LANG=xx_CC lyx > + On Linux: export LANG=xx_CC lyx > > I do not thing the 'export' is needed. Does it change something for > you? (when typing all in the same line) I would use "env" in place of "export", such that it works whatever the shell used. -- Enrico
