On Mon, 18 Oct 1999, Torsten Neuer wrote:
> Peter Hanecak wrote:
>> in htsearch configuration initialization 'language' option from config is
>> used to determine in which language htsearch should produce output. then
>> default config values are changed so they contain language specific
>> values.
This is a very nice idea. In fact a more general approach would be to use
the GNU gettext package to take all messages out of the code and into more
translatable forms.
>> while slovak pages uses ISO-8859-2 encoding, i (or who? :) have to
>> implement also something like 'encoding' option (also set when making
>> language customization) so proper encodind/charset HTTP header is returned
>> to client.
This is a good point and something that a language attribute would solve.
> Not quite sure.. but as I understand it, this can already be done
> solely based upon the template feature. All you have to do for it
> is to write one template and one config for each language - common
> parts of the config can be shared using the include directive.
> You can then switch languages by switching configuration files, which
> is possible by using "allow_in_form: config".
No, this can't be done solely based on templates, since error messages are
still in english. :-(
One clarification: you *don't* need allow_in_form: config. Config is
part of the default form. (After all, you need the config file to read the
allow_in_form attribute, right?)
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
