[I18n-sig] Sourceforge Project now operational
Thu, 2 Nov 2000 11:43:24 -0500 (EST)
Andy Robinson writes:
> Meanwhile, what are we aiming for in the long run? Is it ONE
> add-on package with most of the world's codecs? Or several? If
> one, do we just call it python-codecs, and if several, what's a
> good naming convention?
M.-A. Lemburg writes:
> I think that a package AsianCodecs might be a good starter
> for all encodings of that area.
IMHO it is better to break these down by language: downloading all of
the Asian codecs could be a bit draconian. By that scheme a single
package would contain:
and more that I can't think of right now.
Better, IMHO, to have separate codecs broken down by language: this is
what we have done in Rosette. We may even want to break some (like the
Chinese encodings) into smaller sections: Simplified, Traditional, and
Perhaps a name based on the ISO language codes would be useful?
Tom Emerson Basis Technology Corp.
Zenkaku Language Hacker http://www.basistech.com
"Beware the lollipop of mediocrity: lick it once and you suck forever"