Re: Rethinking "Supported language"



Le mercredi 20 février 2008 à 13:27 +0100, Johannes Schmid a écrit :
> Hi!
> 
> What about a different approach:
> 
> In the release notes, there should be placeholder for translators to say
> "my language is supported". So everybody translating the release notes
> will have the chance to put his language and name at the appropriate
> place, regardless of any 80% rule.

Frankly, I hadn't been convinced by any of the proposals until now. The
80%/50% rules are not perfect, but unless we have some serious method to
be more accurate, like Danilo proposed in his D-L HACKING file, I don't
see any reason to change it now.

Claude

> Am Mittwoch, den 20.02.2008, 13:20 +0100 schrieb Reinout van Schouwen:
> > Op woensdag 20-02-2008 om 12:37 uur [tijdzone +0100], schreef Wouter
> > Bolsterlee:
> > 
> > >   Don't count strings in the Developer Tools suite to decide whether a
> > >   language should show up in the release notes as being 'supported' (i.e.
> > >   80% string coverage). That's all.
> > 
> > +1
> > 
> > > Thoughts?
> > 
> > Yes, one more thing. For some modules, being "fully localized"
> > encompasses more than just UI or documentation. IIRC, dasher requires
> > statistics on character frequency in any given language. Productivity
> > apps will need spelling and hyphenation dictionaries, and grammar rules.
> > I haven't tried Orca yet, but I imagine it needs information on how to
> > pronounce words.
> > 
> > My point: I believe that applications with special l10n requirements
> > shouldn't be called "supported" even if just the UI is translated 100%.
> > 
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]