[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] legacy I18N and tickers (was Re: 0.26 status update
From: |
Benoît Dejean |
Subject: |
Re: [Monotone-devel] legacy I18N and tickers (was Re: 0.26 status update) |
Date: |
Fri, 07 Apr 2006 20:02:22 +0200 |
Le jeudi 06 avril 2006 à 11:28 -0700, Graydon Hoare a écrit :
> Richard Levitte - VMS Whacker wrote:
>
> > lapo> BTW: That's a good idea, up to now I was translating in/out
> > lapo> (ingresso/uscita in italian) as "ing."/"usc." but that is very ugly,
> > lapo> arrows are much nicer =)
> >
> > Well, except it breaks under some circumstances...
>
> Agreed. There are really a couple unfortunate behaviors colluding here:
>
> 1. We consider "multiple tickers with same name" a fatal error, which it
> probably isn't. We can probably cook up a fallback behavior which is not
> too bad.
It was an error to use _(tickername) as key.
See 31b6e06e8c46c0eb976c03b34a641f9ab51925a7.
> 2. The French translation contains characters which can't be encoded as
> 8859-1. I think this should probably be avoided. It will help
> compatibility in general if people doing translations in locales with
> strong legacy character sets restrict their translations to those
> character sets (even if using the Unicode codepoints and UTF-8
> encoding). If your locale has a lot of ISO-8859, ISO-2022, KOI, KS-C,
> JIS-X, EUC, or GB users kicking around, it's probably best to stick to
> Unicode characters drawn from those sets.
Fixed :/
--
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html
signature.asc
Description: Ceci est une partie de message numériquement signée
Re: [Monotone-devel] 0.26 status update, Nathaniel Smith, 2006/04/05
Re: [Monotone-devel] 0.26 status update, Nathaniel Smith, 2006/04/04
Re: [Monotone-devel] 0.26 status update, Nathaniel Smith, 2006/04/04