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, README.localization: Updates and clarifications from Pavel

Browse Source 
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@19022 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
Uwe Stöhr 2007-07-10 01:01:05 +00:00
parent 635004c6a6
commit f0b3234596
2 changed files with 30 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
README.localization
View File

@ -14,9 +14,9 @@ native language.
The file you need to edit it an xx.po file where xx stands for your language's 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 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 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 and name it after your language. German would be for example de.po and Polish
@ -40,7 +40,7 @@ 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 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 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 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 then you will see in it the untranslated strings and a place to write your
translation for them. translation for them.
@ -83,17 +83,38 @@ e.g., Czech, the code is "cs_CZ".
The most comfortable way to see your updated translation while editing, is The most comfortable way to see your updated translation while editing, is
running (in linux): 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 2. "make install" in root lyx tree to copy xx.gmo into the appropriate location
(or do it by hand...) (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 po-updates@lyx.org.
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 For some basic idea on how the translation works, you can look at
http://en.wikipedia.org/wiki/Gettext 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 http://www.gnu.org/software/gettext/manual/gettext.html
Consider subscribing to the documentation list at lyx-docs@lists.lyx.org (rather
silent one) or developer's mailing list lyx-devel@lists.lyx.org (high volume).

58
po/README
View File

@ -1,56 +1,4 @@
This file is intended to provide information about the different translation If you want to make translation for your language, please read
files. If you want to make one for your language, please read "Help->Customization" for more information, and the information
"Help->Customization" for more information, and the information below. in README.localization file.
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, lyx-devel@lists.lyx.org.
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.