On Wed, Jun 29, 2011 at 8:11 AM, Marcus (OOo) <[email protected]> wrote:
> Right. Maybe we should split this into 2 parts: > > 1. The very first build(s) to handle fixes for build breaker: > IMHO here it should be enough to have en-US only > > 2. If this is done the next builds can be also used for looking into the > localizations. > > We had the following set of languages for our developer milestones (DEV300 > and OOO340): > - English (US) as master language > - German due to historical reasons and we had the most testers here > - French for the same reason IMHO and long strings > - Japanese due the CJK characters and to test RTL writing > - Russian due to Cyrillic charachters > - Arabic due to the characters and to test bidi writing > > So, we could stick with this (or maybe exchange the one or other language > if is no volunteer to test at the moments, maybe French --> > Brazilian-Portuguese ?). > Spanish would be good. I did submit a petition a few months back for this. Portuguese is a split language between portugal and brasil. Althought most of the romance language shared the same locales issues like long strings. > > --- > > 3. Tests for release builds are out of scope at the moment, but more > language tests the better. > > BTW: > We have also smoke tests. If I'm not wrong these should be included in the > source code. > > Marcus > > > > Am 06/29/2011 02:35 PM, schrieb Rob Weir: > >> It might be useful to make a distinction between two things: >> >> 1) What is needed to have a successful first build? >> ( >> https://cwiki.apache.org/confluence/display/OOOUSERS/Build-Translate-Plan >> ) >> >> 2) What is needed to have a successful first release? >> ( >> https://cwiki.apache.org/confluence/display/OOOUSERS/Release-Translate-Plan >> ) >> >> For a first build, I think our main task will be to ensure that we >> didn't break anything by moving over from Oracle's servers to Apache >> servers. We want to define a simple set of tests that could be done >> after the initial move. But we would also want to run these tests on >> a regular basis,even daily. At work we call these "smoke tests". I >> don't know what the equivalent name is for OOo. >> >> So what is the easiest test that we can do to verify that localization >> is not broken in OOo? >> >> >> For a public release, this will be much more complicated. >> >> >> -Rob >> >> >> >> >> On Wed, Jun 29, 2011 at 8:23 AM, Marcus (OOo)<[email protected]> >> wrote: >> >>> IMHO you can do such little changes without to ask. >>> >>> We should extended the languages to Russian (due to Cyrillic letters) and >>> Portuguese resp. Brazilian-Portuguese (due to long compared to other >>> languages). >>> >>> Marcus >>> >>> >>> >>> Am 06/29/2011 01:46 PM, schrieb Kazunari Hirano: >>> >>>> >>>> As we see Plan Matrix, >>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Project+Planning >>>> Build-Translate-Plan will be one of our first jobs :) >>>> >>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Build-Translate-Plan >>>> Can you read my comments on the page above? >>>> >>>> Can I delete the previous list and start the new list? >>>> >>> -- *Alexandro Colorado* *OpenOffice.org* Español http://es.openoffice.org
