On Sat, Jul 18, 2009 at 12:44, pedram salehpoor<pedram.salehp...@gmail.com> wrote: > Hi > I wanted to know how the changes for PO files are progressing and if there > is anything that I can do to ease the change?
There was a recent discussion about this recently.. It seemed that people had great fears of needing to read over every single snippet (thousands, probably hundreds of thousands) and verify their correctness. I don't know what the exact situation is, but I think we should probably cast a vote on this.. do people want to keep using Docbook XML for translations (and continue with all the problems that has; broken builds being the most annoying part) or o people want to switch to po (with the biggest disadvantage of being non-contextual)? If we vote for po, I would recommend to try scripting the conversion to mark "up2date translations" as OK - i.e. error on "OK" rather then "fuzzy" to ease the pain of needing to sanitycheck way to much text. Do be honest, I don't really understand how the build process will work with .po files. Will the "core files" (english) be automatically generated? Will those files be in SVN? Does PhD need changes? ... As far as I have gathered there is some work going on by a 3rd party called "transferex" (or something similar) that offer web based system for translation work.. Currently phpdoc is larger then their system is capable of - but there exists a good chunk of desktop applications that are used by others to translate these files... I am not a translator, and have never really looked into gettext and po in any serious way, so I really lack the experience on the topic. I, and without a doubt Philip too (who has been looking into this the most), would greatly appreciate feedback from all translators here (especially people like Masahiro and Nilgün!)... -Hannes
