According to Jerome ALET:
> On Wed, 19 Jan 2000, Gilles Detillieux wrote:
> > According to Geoff Hutchison:
> > > >plural_suffix: s # for english/default
> > > >plural_suffix: en # The Netherlands
> > >
> > > No, I think this is a good idea. Obviously a patch to defaults.cc
> > > also needs to be made, and I'd suggest a diff -c3p if you don't have
> > > a -u.
> >
> > Yes, I too like anything that improves internationalisation. With a
> > documentation entry for 3.2's defaults.cc, and a note in hts_template.html,
> > I'd give this a +1 for 3.2.0b1.
>
> In my very humble opinion since I'm not a C++ programmer, just a C one, I
> really don't think it's a good way to do it. In fact we all know that
> htdig needs great improvements in the internalization layer, but for me
> this should be done with a special class (I suppose it's the correct term)
> and with one instance of this particular class for each country (maybe we
Wouldn't that mean changing the C++ code whenever you want to add support
for another country? In my opinion, that would definitely not be an
improvement.
> can fill each with text configuration files at runtime ala locale) and
> which shouldn't have to be modified after being created. What I
> mean is adding more and more configuration fields like plural_suffix to
> the main configuration file should be avoided in favor of a correct
> use of the locale specified in the configuration file.
>
> of course I'm not able to code this so...
Well, if you can give us some pointers as to how we'd get this information
from the locale, I'm sure someone would be willing to code it. Whatever
solution we pick, though, it MUST be run-time configurable. Right now,
all the English text that htsearch uses as user output is changeable in
config attributes or template files. This little template variable is
the only thing that slipped through the cracks. Apart from that, the
only English messages hardcoded in htsearch is a few error message that
should only pop up when there are configuration problems.
In other words, this approach is consistent with what we've done so
far. We already have a large number of config attributes, so one more
doesn't hurt. If you want to have all the language specific attributes
in separate configuration files, you can do that now, and just include
the one you want in the main file. E.g.: "include: francais.conf"
If we can get all this stuff reliably into locales, then that may be
a good approach, but given all the problems users have had with broken
locales on various systems, I'm not convinced this is the way to go.
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.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
