Re: bugsquad guidelines

[Malcolm Tredinnick <malcolm commsecure com au>]

On Thu, Nov 07, 2002 at 04:39:22PM +0000, Telsa Gwynne wrote:
> On Thu, Nov 07, 2002 at 10:15:10AM -0500 or thereabouts, Luis Villa wrote:
> > On Sat, 2002-11-02 at 10:00, Andrew Sobala wrote:
> 
> > New bugs
> > --------
> > -- #FIXME: I18N, L11N: What's the difference?
> 
> > | Kjartan has provided better definitions of these now- are they 
> > | clear enough to you, Andrew? Note that in many cases bugs are both.
> 
> My Favourite Internationalisation/Localisation Muddle-Bug:
> http://bugzilla.gnome.org/show_bug.cgi?id=50595
> 
> If you can sort out which are internationalisation problems and
> which are localisation problems, you are doing well :) 
> 
> Seriously, it's an amazing tangle. The easy bit is that a string
> not marked for translation is definitely an i18n bug. Despite the
> huge list of "what it would be in our locale", I -think- it's all
> an internationalisation bug.

I think it's an internationalisation bug. As a general rule, if the
problem can be fixed by the translators alone (playing around in .po
files), it's L10N. If it requires code changes or extra markup, it's
I18N. Bug #50595 definitely required code changes (and the discussion is
pretty educational -- I'll have to remind menthos to add the solution to
his tips-and-tricks document). What a cool bug. :-)

> Long ago, when we moved everything to bugzilla, there was a
> bug against evolution about "You have translated this word this
> way. That is only correct in Mexican Spanish. The word in Castilian
> Spanish is different." That's a localisation bug. 

Like the way that in Luis-English, localisation has 11 letters between
the 'l' and the 'n'? <runs/> :-)

Malcolm

-- 
The cost of feathers has risen; even down is up!