[translate-pootle] OpenOffice.org processes for Pootle

[Clytie Siddall]

To: translate-pootle
Cc: Aiet Kolkhi, OpenOffice.org Pootle admin

Hi everyone :)





A. UPDATING



1. Notice that the next milestone is out.

2. Get the en-US.sdf file (original strings).

3. Convert it to a POT tree (oo2po).

4. Convert the current translation (GSI_xx.sdf) to a PO tree (oo2po).

5. Update the PO dir with the POT dir (pomigrate2).

6. Find if there are new/fuzzy strings, get the stats (pocount).

7.  Upload/publish the stats and new files for the team to access.







B. SUBMISSION



1. Convert the PO dir. to SDF format (po2oo).

2. Upload the translation to a public address.







(a) convert to SDF

(b) upload

(c) submit issue



C. GLOBAL CHANGES



How could we do this via Pootle?



D. CONCLUSION



Now, if we could only get OpenOffice.org to use XLIFF...




http://groups-beta.google.com/group/vi-VN

Now I'm back in the OpenOffice.org release maelstrom, I'd like to be able to use Pootle more during that process. I have stayed with the main Pootle server, to work on OpenOffice.org-specific processes. Currently, I have to work offline during this time, as there are a lot of quick changes required. However, I think we could manage them via Pootle, if we had an auto-update mechanism, or a fairly straight- forward update mechanism which the team-leader could manage. OpenOffice.org "milestones" (more like tombstones in my sanity ;) ) are right now springing up every few days. I don't know if they are always that frequent, but currently I have to spend quite a lot of time just updating our translation. This means: Ideally, the dedicated OpenOffice.org Pootle server would be synced with the code repo, so teams could enable auto-update to the latest milestone, with an archived directory of the previous version as backup. That would take care of the whole process, because the translation would stay current on the Pootle server, Pootle makes the files and stats available, and we can download whatever we need. Can we do that? At least, can we do it with the OpenOffice.org Pootle server, Aiet? If not, what help do you need to make this happen? Once the translation is ready to submit, there are three different steps: 3. Submit an issue to the OpenOffice.org issue tracker, submitting a translation and including the link to its public location. I think it would be a huge help if we could do these three steps via Pootle. Step 3 would only need to be done once per release, but steps 1 and 2 could be repeated whenever we update our translation, as they makes an updated file available, for example, for Pavel Janik's OpenOffice.org builds, which are regularly released. This would make it much easier to integrate fixes. The translation files could be hosted on the OpenOffice.org Pootle server, or each team could set an upload address on Pootle. So we need these features: (a) and (b) could be buttons on the admin interface, while (c) could be a form, with an optional template, possibly even a link to the OpenOffice.org Issue Tracker, with some of the fields already filled in. The main advantage I've found in working with the SDF file (a remarkably ugly and inflexible format) is that it unifies the tree of PO files, thus making it easy to find-and-replace globally, and to go through the file, comparing vocabulary and syntax. Now we have a global Find, could we also have a global Replace? And possibly a more complex Find feature, which would display all results on one page (or more if necessary), as editable strings, to make it easier to compare translations? Although my examples are specific to OpenOffice.org, I think similar features would be of use to other projects. I'm going to submit an rather large and determined issue about the state of OpenOffice.org translation strings, so a request to change to XLIFF might as well be part of that. I might even live to see it. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)

PGP.sig
Description: This is a digitally signed message part

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle