Hi everyone :)We've all had a lot to do, way too much to do, actually, so things have tended to fall off our general ToDo list.
Our original plans in supporting translation of OpenOffice.org via Pootle included (please correct me if I get this wrong):
1. importing .sdf files 2. updating from current milestone (merge with current files)3. transparently updating project names, no need to set up project access or set options again (e.g. OpenOffice.org 2.1 -> OpenOffice.org 2.2)
4. effective checks of output files(Note: the checks have improved a lot since my report on OpenOffice.org 2.1 checks. Most remaining false positives were errors in the original strings, which I have also reported now.)
5. conversion back to .sdf6. output file connected to a live FTP or HTTP link which can be used by the build processes: every time you output a new .sdf file, accessing this link will download it until the next output file overwrites it
The aim was to automate these processes, test them, then release them to be used, particularly by the arsaperta main current OpenOffice.org translation server, and by individual OpenOffice.org servers run by different language projects.
I am still keen to work on this, although I can only test and advise. OpenOffice.org currently is a very large and complex project with multiple high barriers to participation. Getting Pootle set up to reduce those significantly would make a big difference. Where other large projects already have a functional i18n infrastructure, OpenOffice.org does not (I do not mean this negatively, simply that the extra help supplied by other projects is not available in OpenOffice.org yet). It needs your help, and since it is so important a product in the promotion of free software, I hope you can give it some priority.
Translation deadline for OpenOffice.org 2.2 is 18th January, and after that, due to some impassioned and persistent protests, the release interval will be six months instead of three months. So after 18th January we should have a clear run at testing. Just tell me what you want tested. ;)
One note on editing OpenOffice.org files on Pootle: I did submit a feature request about hiding HTML code. The volunteers who had started working on our OpenOffice.org Help section have been defeated by the difficulty of wading through the HTML code and working out what to translate.
Even if you're accustomed to HTML, the process is very wearing. I did it for an hour or so yesterday and it was too much for me. Code hiding, syntax colouring and/or code folding would be a huge help. Please don't view this as a cosmetic change: it is functional and badly-needed.
I will be downloading those files and translating them in my text editor from now on, because it has syntax colouring and code folding. But I'd rather do the work on Pootle, and my team needs to be able to use Pootle, to distribute the task. Otherwise I end up doing the whole thing, again. I'm the only one silly enough to keep doing a difficult and unrewarding task.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
