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
you like to express it? As another (optional) argument to
lp:get-cts-query()?
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(). But if it's useful functionality, let's
figure out how to add it.
-- Mike
Shannon wrote:
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
http://rotunda.upress.virginia.edu
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
