Hello everyone :)As yet another translation deadline for OpenOffice.org looms over us (18th January), despite the fact that many languages haven't completed QA for version 2.1 yet, we have to update strings for 2.2.
Fortunately, impassioned protests have achieved the goal of changing the OpenOffice.org release interval to six months after version 2.2.
Meanwhile, we have strings to prepare. I have sent an email to Javier, asking for the updated Vietnamese file [1] to be uploaded over our current OpenOffice.org interface strings, and for the new OpenOffice.org milestone to be merged into those current strings. I hope that can be done RSN [2].
Before uploading the updated file, I wanted to check it. I ran: ___Pearl:~/Vietnamese/Individual projects/OpenOffice/sdf files clytie$ pofilter -t accelerators -t escapes -t variables -t xmltags -- openoffice GSI_vi.sdf errors.txt
processing 1 files... [###########################################] 100%Pearl:~/Vietnamese/Individual projects/OpenOffice/sdf files clytie$ pofilter -t accelerators -t escapes -t variables -t xmltags -- openoffice GSI_vi.sdf
processing 1 files... [###########################################] 100%Pearl:~/Vietnamese/Individual projects/OpenOffice/sdf files clytie$ perl expand-vi-characters.pl GSI_vi.sdf >GSI_vi_decomp.sdf Pearl:~/Vietnamese/Individual projects/OpenOffice/sdf files clytie$ pofilter -t spellcheck --language=vi GSI_vi_decomp.sdf errors.txt
processing 1 files... [###########################################] 100% Pearl:~/Vietnamese/Individual projects/OpenOffice/sdf files clytie$ ___The first command included "errors.txt" as an output file. But no output file was created, nor errors displayed.
The second command did not supply an output file, but still no errors were displayed. I had to assume there simply weren't any errors (an attractive thought ;) ).
The third command ran a script to convert the strings in the Windows installer screens to decomposed Unicode. Please see these issues [3] which provide a workaround for the persistent lack of Unicode support in NSIS.
The fourth and fifth commands tried to spellcheck that converted file, with and without an output file. Again, there was no output file, there were no errors displayed.
Am I doing something wrong here? How do I get pofilter output on OpenOffice.org files?
Thankyou for your help with this. :)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 [1] http://www.riverland.net.au/~clytie/OpenOffice/GSI_vi.sdf.bz2 [2] Real Soon Now [3] http://www.openoffice.org/issues/show_bug.cgi?id=72905 http://www.openoffice.org/issues/show_bug.cgi?id=73103 http://www.openoffice.org/issues/show_bug.cgi?id=73192
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
