At 9:31 AM +0100 1/20/00, Jerome ALET wrote:
>done without changing any code, e.g. reading each file in a directory
>which contains all the country specific files and creating a new instance
>for each countryfile read.
Yes, this is GNU getttext. It's not C++, but this is essentially how
it works. I haven't investigated much more though.
> - or create country specific files (or directories) in the same
>way as the locale database is constructed, but let them in the htdig home.
Right. These are the gettext "localization" files.
>you're right. IMHO these messages should remain in English to avoid
>problems when understanding what is wrong when helping other people.
This depends on the quality of translation!
> > Indeed, the most frequent problems involving internationalisation
> > in htdig/htsearch have been 1) confusion about how to configure it, 2)
> > broken locale implementations, 3) lack of an accent fuzzy match algorithm,
> > 4) lack of support for 16-bit characters. Locales don't solve any of
> > these problems, and from my experience have aggravated the first two.
>
>maybe they have aggravated problems instead of solving them, nevertheless
>what we want should be included in the locales database, I mean in an
>ideal world.
It's debatable how much should be in a locale database--programs
often have very specific (and hard to translate) messages. So some
things are harder to generalize than others.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
