Hi,
Does anyone know whether lib-parser has support for language-aware
tokenization, for lp:get-cts-query specifically?
Thanks,
__
Shannon Scott Shiflett, programmer/analyst with ROTUNDA,
The University of Virginia Press, Charlottesville, VA USA
Today, lib-parser calls cts:tokenize() without the language argument, so
it always uses the database default language. So the tokenization is
language-aware, but there's no per-query control over which language it
uses.
If per-query control over language awareness would be useful, how would
y
Thank you, Mike--that's so very agreeable--yes, per-query control
language awareness would be most useful! Given a form that accepts a
query string input and a language selector that includes an "all"
option, the desired behavior is language-specific tokenization, in
this case, for English
Shannon,
Hmm... I think we may be talking at cross-purposes. As I mentioned
yesterday, I'm a little concerned about maintaining a distinction
between cts:query term-level language, vs the language passed to
cts:tokenize() in lp:get-cts-query-element().
When I mentioned the idea of adding ano
Good morning,
Mike, thanks for the free consulting :)
I agree, in the case of English and French, I don't think I need to be
concerned with the tokenizing.
I may end up submitting an RFE on this (something similar to the
thesaurus expansion API sounds like a good approach to me) since
fu
