On Ma, 2007-01-15 at 16:09 +1030, Clytie Siddall wrote: > Hi everyone :)
Hi Clytie > > 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 .sdf > > 6. 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 Most of my work on this is finalised, I believe. It is not deployed, and will probably need another 2 hours of work and testing, but drop me a line when we need to start on this again. I hope I can fit it in. > > 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. I (very) quickly had a look at one file in helpcontent2, and I must say, it is an abomination! The markup is more than the translatable text. Furthermore it seems as if many of them have a simple pattern like <tag with detail>translatable text</tag> which in my opinion should not be coming to the translator at all (unless there are attributes that should be translated). All of this means that you cannot (easily) use your UI translations as a TM to align your terminology (which is supposed to be trivial) and the problems with syntax as you mention. It also seems as if they would be able to merge some consecutive strings if they were able to strip the markup. It seems that angular brackets and quotes are permanently escaped which just means more hassle for the translator. If I'm not mistaken, this isn't even consistent with the rest of OpenOffice.org, is it? In other places the angular brackets and quotes are used bare, so there seems to be different rules for helpcontent2. I guess I should now be offering to allocate time to write a separate storage class and converters for helpcontent2 which will help a little bit, but in my opinion a more disruptive change from their side might help more. I can fully understand why your team got frightened away. In fact, I'm not quite sure why you are not (well, I have an idea ;-) You should feel free to translate offline and to update the translations on the server. You can simply upload a ZIP file of the updated files. Just take care to use the same directory structure so that Pootle can merge them with the existing files. Currently Pootle will always try to merge the files on upload, which might not always be what you want, but I should have some news on developments in this area real soon. ------------------------------------------------------------------------- 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
