985
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − == Preliminary ==+ − The Goal is to integrate Pootle with CVS and an automatic converter between XML files and PO at contribs.org :) − Once we have everything worked out how to interact with pootle and the formmagick stuff then I'll get something up on contribs.org that everyone can use. It would be really nice if we could automate the extraction/import of files that need to be translated into pootle but first things first. <small>— [[User:Slords|Slords]] ([[User talk:Slords|talk]] • [[Special:Contributions/Slords|contribs]]).</small> 18:23, 24 January 2008 (MST)+ − Test pootle site: http://www.unixlan.com.ar:8888+ − When you comment on this page, please, add comments in the related section and delete dated text+ − == Formagick ==+ − I have found a good tool (getpo) for convert HTML to PO and revert. The best is you can customize to handle xml tags. It has use TIDY lib. − Before use, you can enable centosplus repo and install "tidy".+ − Download getpo from http://i18n.linux.net.cn/download/gettext-autowork/getpo-031.tar.bz2+ − See these address:+ − http://mail.gnome.org/archives/gnome-i18n/2004-March/msg00070.html+ − http://tidy.sourceforge.net − http://www.w3.org/People/Raggett/tidy/ − http://tidy.sourceforge.net/docs/quickref.html − + + − ===progress=== − Is this working manually yet Normando ? − :Not yet because I need help from a python or perl specific programmer. Anyway I can playing with these converters.+ − :--[[User:PicsOne|Normando Hall]] 08:21, 25 January 2008 (MST) − − == revision control using CVS/SVN == − − Today I had a quick look at the pootle pages and found a wiki as well, which has some valuable information like for instance revision control using CVS/SVN: http://translate.sourceforge.net/wiki/pootle/version_control - [[User:Cactus|Cactus]] 03:26, 25 January 2008 (MST) − − ===progress=== − we'll look at this later, perhaps starting with contribs − − − == Usage == − − ===untranslated words=== − click "Show Editing Functions" and finally at "Quick Translate" for each file or whole language. − − Also you can see the suggestions clicking at "Review Suggestions". − − ===checks=== − click "show checks" to see a list of syntax errors − − acronyms 6 strings (2%) failed − brackets 17 strings (6%) failed − doublequoting 4 strings (1%) failed − doublespacing 1 string (0%) failed − endpunc 11 strings (3%) failed − endwhitespace 4 strings (1%) failed − numbers 2 strings (0%) failed − puncspacing 2 strings (0%) failed − sentencecount 2 strings (0%) failed − simplecaps 16 strings (5%) failed − startcaps 6 strings (2%) failed − unchanged 7 strings (2%) failed − untranslated 53 strings (19%) failed − − click on one of the links offered and fix them − − See http://translate.sourceforge.net/wiki/guide/pofilter_examples and http://translate.sourceforge.net/wiki/guide/translation/commonerrors − − == Remarks == − Now we have entered the data, it makes it clearer where there are missing translations, good work ! − − ===cleanup=== − − ===bugs=== − − * http://bugs.contribs.org/show_bug.cgi?id=3833 − there isn't a standard english base for translators to work off, french and german have the most complete set − − there is now, the english version is the latest − − see merging new files, & check this patch to see differences − − * http://bugs.contribs.org/show_bug.cgi?id=3834 − .po file names are inconsistent, SV & FR add .tmpl.po − − : .tmpl.po is correct, please delete the incorrect files, see bug<br> − : and if you can rename ALL the languages for those two files − − ===questions=== − − *Another item is charset utf8 or iso-8859-1 − − :charset=iso-8859-1 is mostly being used in the files I've looked at why would we change it ? SN − − ===merging new strings=== − I have merged new strings into all 10 languages − − A good way is to create a file with the change, called the same as the file you are merging into − eg this update from sv userOverQuota.po − #: root/etc/e-smith/templates/usr/lib/e-smith-quota/userOverQuota.tmpl:22 − msgid " no limit set" − msgstr "" − − A not so good way is to clobber it with a complete file, I did this with server-console.po − − The stings merge fine, it just overwrites the header info. − − I created the new server-console.po by taking the most complete translation which was the fr version and − stripping the fr translations − − A few inconsistencies remain, individual translators will have to resolve them, eg − :IT has extra strings − :SV is missing a few − − Merging this way may leave orphaned strings, eg − − -#: root/sbin/e-smith/console:2791 − +#: root/sbin/e-smith/console:2832 − msgid "" − -"Please select whether you wish to reboot or shutdown. The process will start " − -"as soon as you make your selection." − +"Please select whether you wish to reboot, reconfigure or shutdown. The " − +"process will start as soon as you make your selection." − msgstr "" − − − We should work out how 'update from template' works. Where are the templates kept ? they will be the EN versions − − :Please, see this bug http://bugs.contribs.org/show_bug.cgi?id=3833
no edit summary
Managing SME translations with pootle have been moved to [[Translations]]
== Please use common packages and default package names (where possible) ==
A lot of the RPM's are in the DAG repository, no use of packaging them yourself or sharing them by copying them from the providing website and sharing them under a different name.
:What packages exactly? All packages are build from the sources code with the command "python setup.py bdist_rpm" (under python 2.4), and the packge itself create the RPM. The only packages I have changed the name is smeserver-pylucene, because it has a lot of problem to build at the same time of build rpm. Instead, I have only package the installed files. But in the next release of "Translate Toolkin", support for PyLucene 2.X and I have this package correctly builded.
Please point users to download python-kid (replacing you kid RPM), python-lxml (replacing your lxml RPM), python-sqllite (replacing pysqlite RPM), python_Levenshtein and python-elementtree (which you called elementtree) which is also available in the DAG repository and AFAIK is already installed on SME Server by default.
:These packages don't run under python2.4.
On top of that not everything is required to install Pootle, only requirements AFAIK could find on the Pootle site are listed [http://translate.sourceforge.net/wiki/pootle/installation#pre-requisite_software here] and because of the jToolkit requiring pythonabi-2.4 you have problems installing against pythonabi-2.3 which is installed on SME Server 7.3, perhaps you can find an older jToolkit, or recompile jToolkit from source and see if it will also work with pythonabi-2.3, this would drop the hack you have to do to make it work on SME Server 7.x.
:Yes, requirements say python 2.3 is supported, but preferable 2.4. This page is out of date. If you search through pootle mailing lists you will found a lot of problems with python 2.3. Of couser I was preferable python 2.3, and make my own packages and test with python 2.3 but without sucess. I have a lot of headache with python 2.3 to try (only try) to run pootle. So, python 2.4 is mandatory. Also has a superb efficiently above 2.3 with some new functions that pootle use.
:See http://translate.svn.sourceforge.net/viewvc/translate/src/trunk/Pootle/README?r1=6098&r2=6144
I want to play with it to finally convert formmagick panels to PO correctly.
:I am not finish this howto yet. Sorry for not warn about that. Now I put a template box with a warn.
:Only when I have finished this howto, I will included in smecontribs.
- [[User:Cactus|Cactus]] 14:09, 19 February 2008 (MST)