> This whole formal/informal thing is really starting to bother me.
I agree that using a per-file system with the option of changing the
search list is the right approach. Also, I do not think that we need a
"german_translated_by_hanno" file. It's more than enough if the
translator adds a little "readme" file to the language set directory
that informs who translated the messages and how you can contact him for
corrections/suggestions.
> Internally, we will keep track of language by a two-character string given
> by RFC1766 (or a list of such two-character strings).
As mentioned in another which hasn't been distributed by the list yet,
look at Locale::Language, a CPAN module that already does this. I found
it last weekend while I was looking for i8n-Perl modules.
Greetings,
Hanno
--
Alle Ampeln auf Gelb! Hanno Mueller, Programmer
LAVA GmbH, Hamburg
http://my.lava.de/~hanno/
References:
|
|
