Sounds interesting, but is there a way to extract out the FOP code?
Alternatively, this could be in the contrib area, where the dependency
would be allowed, although, I still think we aim to keep our Analyzers
pretty lightweight. Of course, if the are ASL, we probably could just
put the classes in the contrib area with a NOTICE file saying they
were appropriated from FOP (although, I don't know if even that is
required)
Best thing to do, I think, would be to submit a patch (see the Wiki on
How To Contribute) and we can have a discussion based on what is there.
-Grant
On Feb 5, 2008, at 4:08 PM, Thomas Peuss wrote:
Hello!
I have nearly finished a tokenfilter to decompose compound words you
find in many germanic languages (like German, Swedish, ...) into
single
tokens.
An example: Donaudampfschiff would be decomposed to Donau, dampf,
schiff
so that you can find the word even when you only enter "Schiff".
I use the hyphenation code from the Apache XML project FOP
(http://xmlgraphics.apache.org/fop/) to do the first step of
decomposition. Currently I use the FOP jars directly. I only use a
handful of classes from the FOP project.
My question now:
Would it be OK to copy this classes over to the Lucene project
(renaming the packages of course) or should I stick with the
dependency
to the FOP jars? The FOP code uses the ASF V2 license as well.
What do you think?
CU
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
