I am setting up a bilingual website with content
negotiation. ht://Dig does not work well with that.
It does not state to the server in what language it
would like to be answered (no Accept-Language: header).
Currently, the default language for a webpage is all
that gets indexed. And the language that the searching
browser has set is not taken into account at all. What
Ideally, one htdig run would be able to query for >1
languages by requesting each of them separately. More
modestly, it would be useful to be able to run ht://Dig
twice, with different language settings, and perhaps
even with different databases. Hacking htsearch to
pick the preferred language is easy (see the attached
I made a quick stab at it but failed, on account of
misunderstanding how the configuration file data
(specifically, the "locale" setting) is read into
htdig. Perhaps I'll give it another shot later.
Thanks for ht://Dig!
Rick van Rein,
Log in to post a comment.