According to James O'Malley:
> Except that it DOES work!!! and work perfectly. You're right, though I
> missed the backslashes... I added them, but it didn't seem to make a
> difference.
Well, if it works for you, then either tHe build_select_lists line in your
config file is different than what you posted, or you're using METHOD,
FORMAT and SORT in your templates, rather than METHOD_LIST, FORMAT_LIST
and SELECTED_SORT. I wrote the code that handles build_select_lists,
so unless you somehow modified the code, I know for a fact that the
example usage you posted will not produce any template variables.
build_select_lists needs octuples to work.
> However, I couldn't get ANY of the examples on the htdig site to work. I
I'd be interested in knowing exactly which examples you tried that didn't
work, and how they were entered in your config file and template files.
I personally tested the examples in hts_selectors.html and attrs.html,
and they worked.
> ended up grepping the hell out of the source code to see how those menus
> were built internally for the cgi so for me it passes the Turing test for
> wrongness *G*, that is, if it works well enough that it cannot be
> distinguished from elegant code, then it must be elegant. *shrug*.
Well, if you grepped through the source code, then you must have come across
the main loop in htsearch/Display.cc (setVariables) which goes through the
entries in build_select_lists:
for (int b = 0; b <= builds.Count()-8; b += 8)
Note how it takes them eight at a time, and if there are less than eight
entries in the attribute it won't even enter the loop.
> Anyway, as far as slackware goes, we've always just made symlinks to get
> stuff to work right. A lot of the time things expect es instead of es_ES or
> es_PR, so we end up just creating symlinks. This is particularly true with
> PHP.
>
> Sure, I'll put together what we've done into an espa�olizaci�n kit and put
> it someplace where people can get at it.
Excellent! Thanks.
> > 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
