On Mon, 18 Oct 1999, Geoff Hutchison 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.
well, i feel not very competent about that right now. with some time maybe
i can manage that. sure it would be cleaner or nicer implementation.
> >> 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.
this one i'll do tomorow? well, this week for sure. :)
> > 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. :-(
yes. and for now are not "localized" in my patch.
templates solve almost everything (if we forget error messages) but when
you perform search (i.e. you see result page) there are $(METHOD),
$(FORMAT) and $(SORT) variables in templates which vere filled with
english words - this looks somehow strange in slovak page (some users then
should get confused and/or angry). these can't be dome using config file
not templates. or can be?
> 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?)
right. specifying config in your search.html is enought to "force" usage
of alternate config.
i want to say, that even "you are dump", "you stupid", ... messages are
welcome while maybe i overlooked somethink else which can handle the
"multilanguage" thing. of course some more explanation is needed in such
messages :) .
hany
===================================================================
Peter Hanecak - production manager
Mega & Loman, Stare grunty 52, 842 44 Bratislava, Slovakia
tel., fax: +421-7-654 211 52
[EMAIL PROTECTED], http://www.megaloman.com
GPG pub.key: http://www.megaloman.com/gpg/hanecak-megaloman.txt
===================================================================
------------------------------------
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.
