Re: [l10n-dev] OOo 3.2.1 l10n schedule?
Would you guys kindly remind, what's the milestone for the SDF/POT for this release? On 03/17/2010 07:39 PM, Ivo Hinkelmann wrote: Rafaella is currently on vacation but will be back next week. She might give a statement about this. André Schnabel wrote: the wiki mentions a l10n handover and translation delivery for OOo 3.2.1: http://wiki.services.openoffice.org/wiki/OOoRelease321 ... - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [dev] Spanish NL Community requests for funding help on acquiring a local build box
Hi, On 18.3.2010, at 0:03, Alexandro Colorado wrote: The request is to partially fund the buildbox, so given the response, my guess is that most people are ok with this. Please let's try to approve the budget so we can move on. The platform would be on linux and will improve the spanish locale. I won't approve the machine just for one locale, sorry. I'd like to see similar system as is for the windows machine we approved a month ago or so. -- Pavel Janík - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Nomination for the Community Council
Ivo Hinkelmann wrote: Hi, Sophie wrote: Hi Olivier, Olivier Hallot wrote: Hi Fellows I am nominating myself for the NLC position now open in the Community Council, and I ask for your support. My objectives in this position is to do my best to bring a “voice and experience from the South” into the CC. Rio is in south east! Depends where you are. For me it's in the south west. ;-) Thanks a lot for nominating yourself, you'll have all my support +1 +1 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [dev] Spanish NL Community requests for funding help on acquiring a local build box
The request is to partially fund the buildbox, so given the response, my guess is that most people are ok with this. Please let's try to approve the budget so we can move on. The platform would be on linux and will improve the spanish locale. Regards On 3/17/10, Ivo Hinkelmann wrote: > Hi Santiago, > > we are currently moving to the latest version of Pootle. This new > version will also run on a new machine. As soon as this is up and > running well and we moved all translation to this new machine we would > like update the pootle source strings more frequently. Every milestone > or lets say at least once every month. I am not yet sure how to deal > with the different codelines, e.g. OOO320 vs. DEV300 . > > At the moment we don't have the resources here to build instsets / > langpacks for every language on the development codeline ( DEV300 ). > > Cheers, > Ivo > > Santiago Bosio wrote: >> Martin Hollmichel escribió: > >>> Hi Santiago, >>> >>> I think it's an good plan to verify localization (and terminology) as >>> a early as possible.Are there any technical hurdles to import >>> incremental localization updates from pootle and do frequent builds. >>> Can this also easily be done for more languages than Spanish ? What >>> would be your preferred platform for doing this ? >>> >>> Martin >> Hi Martin: >> >> Perhaps somebody from the l10n project can give better technical >> background about the workflow on translation and why the process doesn't >> admit changes after the localisation CWS has been integrated. >> >> We have been working with Pootle, open language tools, and gsicheck and, >> personally, I consider that string translation changes are of the safest >> changes that can be introduced (provided that they are checked and >> sanitized) without breaking builds or causing problems. And even when we >> considered some translation errors as show-stoppers, their corrections >> weren't accepted in RC stage, and were delayed to next bugfix release. >> >> As I said, we have been doing our own builds, patching the translations >> with the latest snapshot from Pootle, converted to OOo SDF format using >> po2oo, and gsichecking the resulting file. All of it can be done >> automatically, but I see two problems to solve for the "as early as >> possible" scenario: >> >> 1. Pootle updates are done only after UI and string freeze. Then these >> new or modified strings are available for a few weeks to be translated, >> before localisation CWS integration, and after that, usually a two week >> period to introduce changes before first RC. Ideally, new or modified >> strings should be inmediately available on Pootle to alleviate the >> translation burden when too many strings were introduced/modified. Also, >> I think translation updates must be accepted in-between RC's when NL >> project leaders ask to do so, and next RC built with the last snapshot >> from Pootle. >> >> 2. Weekly devel builds should be done with the complete set of language >> packs, and not only a few of them as it is done currently (I think they >> are FR, DE, IT, JA, pt-BR, etc.) as it will give us the opportunity to >> check our advance (provided that we have early the strings to translate >> on Pootle as I said before). >> >> Regardless of that, on our community we have a specific problem with our >> translation: it has a poor overall quality, and this review process I >> described on my previous e-mail must be carried out outside the current >> translations on Pootle, because if we did otherwise, we can get as a >> result a more confusing translation on the next upcoming releases. So, >> we still need a local box to do our own builds to test the revision >> process until it gets to an acceptable degree of quality to merge the >> changes back to Pootle. >> >> Best regards, >> >> Santiago >> >> PD: I'm cross-posting this message to l10n dev list. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.org >> For additional commands, e-mail: dev-h...@openoffice.org >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org > For additional commands, e-mail: dev-h...@l10n.openoffice.org > > -- Alexandro Colorado OpenOffice.org Español "Support this 31st March - Document Freedom Day " http://www.documentfreedom.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Add Latvian language to Sun builds
Hi, Viesturs Zariņš wrote: What steps should I make to have Latvian language incorporated into the official builds? in the next release that will contain localisation I will move your translation from Pootle into the code. The language is already enabled in OOO320. Because 3.2.0 is already released new builds are not possible. For future builds "lt" is now in the build list (due to 3.2.0) and the quality will get better with your newest effort. please file an issue to Ivo (OOo name "ihi") to get the localization integrated into the DEV300 codeline. Will this mean that Pootle content is upgraded to the DEV strings? If so' I'd rather wait a couple of months until Ubuntu 10.4 is released, as getting good 3.2 translations in there is our top priority right now. Pootle will not be updated with DEV300 strings now. Cheers, Ivo - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Add Latvian language to Sun builds
Hi, Rimas Kudelis wrote: Hi Marcus, 2010.03.12 18:47, Marcus Lange rašė: Viesturs Zarins wrote: Currently all the result is in Pootle: http://pootle2.sunvirtuallab.com/lv/index.html What steps should I make to have Latvian language incorporated into the official builds? Because 3.2.0 is already released new builds are not possible. For future builds "lt" is now in the build list (due to 3.2.0) and the quality will get better with your newest effort. "lt" is the code for Lithuanian, not Latvian. For Latvian, you should also include "lv" into the build list (and please don't drop "lt" at the same time ;)). m13 of OOO320 pack.lst contains both, lv and lt ;) Cheers, Ivo Regards, Rimas - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Nomination for the Community Council
Hi, Sophie wrote: Hi Olivier, Olivier Hallot wrote: Hi Fellows I am nominating myself for the NLC position now open in the Community Council, and I ask for your support. My objectives in this position is to do my best to bring a “voice and experience from the South” into the CC. Rio is in south east! Thanks a lot for nominating yourself, you'll have all my support +1 Voted! Cheers, Ivo - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] Re: [dev] Spanish NL Community requests for funding help on acquiring a local build box
Hi Santiago, we are currently moving to the latest version of Pootle. This new version will also run on a new machine. As soon as this is up and running well and we moved all translation to this new machine we would like update the pootle source strings more frequently. Every milestone or lets say at least once every month. I am not yet sure how to deal with the different codelines, e.g. OOO320 vs. DEV300 . At the moment we don't have the resources here to build instsets / langpacks for every language on the development codeline ( DEV300 ). Cheers, Ivo Santiago Bosio wrote: Martin Hollmichel escribió: Hi Santiago, I think it's an good plan to verify localization (and terminology) as a early as possible.Are there any technical hurdles to import incremental localization updates from pootle and do frequent builds. Can this also easily be done for more languages than Spanish ? What would be your preferred platform for doing this ? Martin Hi Martin: Perhaps somebody from the l10n project can give better technical background about the workflow on translation and why the process doesn't admit changes after the localisation CWS has been integrated. We have been working with Pootle, open language tools, and gsicheck and, personally, I consider that string translation changes are of the safest changes that can be introduced (provided that they are checked and sanitized) without breaking builds or causing problems. And even when we considered some translation errors as show-stoppers, their corrections weren't accepted in RC stage, and were delayed to next bugfix release. As I said, we have been doing our own builds, patching the translations with the latest snapshot from Pootle, converted to OOo SDF format using po2oo, and gsichecking the resulting file. All of it can be done automatically, but I see two problems to solve for the "as early as possible" scenario: 1. Pootle updates are done only after UI and string freeze. Then these new or modified strings are available for a few weeks to be translated, before localisation CWS integration, and after that, usually a two week period to introduce changes before first RC. Ideally, new or modified strings should be inmediately available on Pootle to alleviate the translation burden when too many strings were introduced/modified. Also, I think translation updates must be accepted in-between RC's when NL project leaders ask to do so, and next RC built with the last snapshot from Pootle. 2. Weekly devel builds should be done with the complete set of language packs, and not only a few of them as it is done currently (I think they are FR, DE, IT, JA, pt-BR, etc.) as it will give us the opportunity to check our advance (provided that we have early the strings to translate on Pootle as I said before). Regardless of that, on our community we have a specific problem with our translation: it has a poor overall quality, and this review process I described on my previous e-mail must be carried out outside the current translations on Pootle, because if we did otherwise, we can get as a result a more confusing translation on the next upcoming releases. So, we still need a local box to do our own builds to test the revision process until it gets to an acceptable degree of quality to merge the changes back to Pootle. Best regards, Santiago PD: I'm cross-posting this message to l10n dev list. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OOo 3.2.1 l10n schedule?
Hi André, Rafaella is currently on vacation but will be back next week. She might give a statement about this. Cheers, Ivo André Schnabel wrote: Hi, the wiki mentions a l10n handover and translation delivery for OOo 3.2.1: http://wiki.services.openoffice.org/wiki/OOoRelease321 Do we have any idea about string / word counts and what parts (UI / Help) need to be translated? Would bevery helpfull to prepare translation for next week. Thanks and greetings, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] OOo 3.2.1 l10n schedule?
Hi, the wiki mentions a l10n handover and translation delivery for OOo 3.2.1: http://wiki.services.openoffice.org/wiki/OOoRelease321 Do we have any idea about string / word counts and what parts (UI / Help) need to be translated? Would bevery helpfull to prepare translation for next week. Thanks and greetings, André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
