Stoune schrieb: > This is my algorithm of making translation. > Warning: I'm not the developer of Sphinx so this text express my own > opinion. Any comments appritiated . > Warning: This is correct fo Windows OS. On xUnix this steps require > some modification, for example path separator '/' instead of '\'. > gettext utils ordinary installs with developers packages. > 1. easy_install babel - install pybabel package from PyPI. > 1a(optional). You can install cygwin (cygwin.com) gettext > distribution to detect mistakes. > 2. Clone latest mercurial repository of Sphinx. > 2a. Install sphinx. For example: easy_install -U . on parent directory > to sphinx sources. (Warning: this directory should contain only one > python module(Sphinx) in another case you'll get error). > 3. Go to the sphinx directory. > 4. python sphinx\setup.py extract_messages - This step extract > messages from sources. > 5(this step needed only if you make translation first time). > python setup.py init_catalog -l <loc> -i sphinx\locale\sphinx.pot - > o sphinx\locale\<loc>\sphinx.po - there substitute <loc> - to your > languge code. > 5a. If you make update of old translation then run python setup.py > update_catalog --previous > 6. Translate on sphinx\locale\<loc>\sphinx.po strings by entering your > translation into corresponding msgstr "" section. You can fill po > template header with translator name first time, or Last-Translator if > you updade existed translation. > 7. Remove #, fuzzy from po footer before compiling messages. > 8. You can copy your translated and original file into same directory > and run on cygwin command: > msgcmp --use-fuzzy sphinx.po sphinx.pot > Observe output of this program and try to fix errors. > 9. python setup.py compile_catalog this will produce compiled catalog > file and js. > 10. Add your translation into installed sphinx modele. %site-packages%/ > sphinx-0.6dev_20090114-py2.6.egg > 11. Testing. Modify on sphinx\doc\sphinx.py language option with > language = '<loc>' ther <loc> - your languge. > Run sphinx-build -b html sphinx\doc\ sphinx\htmldoc . Observe that > build was successfull. Goto sphinx\htmldoc open index.html navigate to > different pages, make shure that translation was correct, all > functionality work as expected, translation do not contain typos and > gramattical mistakes. > 12. Archive translated directory and upload it into reachable place. > Contact with Sphinx maintaner and inform it that you make the > translation. (You can make enchancement request on Sphinx tracker, > maybe maintaners select preferable way).
Thanks for the guide, I think it covers all important steps. Georg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
