According to James O'Malley:
> We just finished with a big project for latin america that included among
> other things internationalized versions of htdig (both english and spanish
> at the same time). I've seen a lot of questions on the mailing list and FAQ
> about how to do the build_select_lists, but few examples. Took a while, but
> here's a drag and drop example of how to get your search form in spanish (or
> any other language without using templates, but passing variables right to
> the htsearch). This is on a slackware box running a slackware-current from
> about a month ago. (side note: Great distro, I highly recommend it!)
Really? It seems even just a few months ago we were still getting
reports of broken locale support on slackware. I guess they finally
bit the bullet and switched to glibc, or fixed the old libc5 code.
> build_select_lists: METHOD_LIST method method_names 2 1 2
> FORMAT_LIST format template_map 3 2 1 template_name
> ""
> SELECTED_SORT sort sort_names 2 1 2
This won't work at all! The entries in build_select_lists should come in
sets of eight. Your first line is incomplete, plus it's missing the
trailing backslash to make it continue on the next line, so the rest is
also ignored. Note that htsearch doesn't give a lot of feedback when
attributes are set incorrectly. It normally just silently ignores them
and goes on if it can.
In any case, the template variables you're attempting to define above
are not needed at all, as htsearch already defines METHOD, FORMAT and
SORT as select lists, without the use of build_select_lists.
There are examples of build_select_lists here:
http://www.htdig.org/attrs.html#build_select_lists
http://www.htdig.org/hts_selectors.html
Both of these will be expanded somewhat in the next release. I think
the notes in the second documentation file above make it clear that the
FORMAT_LIST exammple is just an example, to mimic what htsearch already
does. It also lists the 3 built-in select lists, METHOD, FORMAT and SORT.
> Works like a charm. One thing to note: the configuration manual says:
>
> The following line would do it:
> <input type=hidden name=config value="cc">
>
> Which I took to mean, add it.
Well, that's a bad assumption, but unfortunately it's a common one.
> However, the line already exists and if you add it, it gives you a
> configuration file not found error. So maybe the documentation should be
> amended to say
>
> Modify the following line replacing value with your custom configuration
> file:
> <input type=hidden name=config value="">
That would assume that everyone following these instructions must be
using the sample search.html file that comes with the package. I don't
think that's the case. Still, we do need to clarify this FAQ entry a bit.
> Anyway, we followed the FAQ for creating the spanish ispell dictionaries
> which worked fine. If anyone would like a detailed explaination of this
> process I'll post it.
If you can put together a kit, similar to Didier Lebrun's "kit de
francisation", that would be even better! We do get requests now and
then for setting up Spanish support, so I think the contribution would
be appreciated.
--
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
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
