[TF-dev] validation results ([Fwd: Re: [TF-dev] FCS date - Monday 06/15])

I checked our current files in repository.
Please check the results below for your language.

   http://translatedfiles.netbeans.org/6.7/validation.html

If these keywords for MessageFormat and ChoiceFormat
are localized and mismatced {} exists, it may cause
expected exception at NetBeans.

Here are same examples:

gl_ES: "number" is localized
   ide11/gsf-testrunner/gsf-testrunner/org/netbeans/modules/gsf/testrunner/api/Bundle_gl_ES.properties
   # Error: ''number'' should not be localized in <{0} - causou un ERRO ({1,número,0.0##} s)> (En=<{0} - caused an ERROR ({1,number,0.0##} s)>).

es: "[" is used instead of "{"
   ide11/diff/diff/org/netbeans/modules/diff/Bundle_es.properties
   # Error: Localized key <EXC_PatchApplicationFailed=Error al aplicar el parche a "[1}": {0}> doesn't contain '{1}' (En='Application of the patch to ''{1}'' failed: {0}').

I'll check again and try to fix all of them at integration next week.
But please check as much as possible on CTI.

Please note that some English strings in CTI have been updated,
so in some cases, English and localized strings are not matched.
You can ignore them.

Regards,
Masaki

-------- Original Message --------
Subject: Re: [TF-dev] FCS date - Monday 06/15
Date: Fri, 12 Jun 2009 08:22:46 +0900
From: Masaki Katakai <[email protected]>
To: [email protected]
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Hi Jean-François,

> displays with missing data or even make NB crash (unbalanced brackets,
> see http://www.netbeans.org/issues/show_bug.cgi?id=166624 for instance).

Thank you for the info. Yes, true. We need to trasnalte these
strings very carefully if it contains {0},{1},{2},... It will be
used in MessageFormat.

For another case that will cause exception, I sent email about
over-translation of "choice" case for ChoiceFormat. We need to
care this case too.

http://translatedfiles.netbeans.org/servlets/ReadMsg?list=dev&msgNo=5376

These keywords should not be localized. Once it's localized, NetBeans
will cause exception.

  FormatType: one of
          number date time choice
  FormatStyle:
          short
          medium
          long
          full
          integer
          currency
          percent

Please refer http://java.sun.com/javase/6/docs/api/java/text/MessageFormat.html

> I don't think only the FR team has such problems... or do we ?  ;-)

Yes, it may happen in any languages.

We used to check these strings by script. I'll prepare it asap to check them.

Regards,
Masaki

Jean-François El Fouly wrote:
> I would dare add: fix as many translation bugs as you can and IMHO this 
> has an even higher priority.
> For me/for us (TF-fr) we've experimented that typos such as unbalanced 
> brackets or failing to double quotes where required may cause stupid 
> displays with missing data or even make NB crash (unbalanced brackets, 
> see http://www.netbeans.org/issues/show_bug.cgi?id=166624 for instance).
> Or spurious "[fuzzy]" comments put here and there by OmegaT that don't 
> look good in NB...
> I don't think only the FR team has such problems... or do we ?  ;-)
> 
> BTW does "Monday" mean Monday morning or Monday night, Central Europe time ?
> 
> 
> Le 11 juin 09 à 10:34, Petra Stastna (Nicky) a écrit :
> 
>> Dear Community,
>>
>> We will be picking up translations for the final FCS integration on 
>> *Monday 06/15*, so please translate as much as possible for this date.
>>
>> All translations done by 06/15 will go into the final FCS build.
>> After this date, we will complete projects so they will "disappear" 
>> from CTI. A couple of days later, we will restart projects for those 
>> languages and files you will want to continue translating. But please 
>> translate as much as possible by  06/15.
>>
>>
>> Thank you!
>> Petra
>>
> 



-- 
Masaki Katakai
Sun Microsystems K.K.
http://blogs.sun.com/katakai