so just work
> with Strings.
Also, if you would to modify the tokens generated by the
[Standard]Analyzer, you could write your own TokenFilter - e.g. like the
SynonymFilter in the LIA book.
>
> Otis
>
> - Original Message ----
> From: Ryan O'Hara <[EMAIL PROTECTED]&
ging the String seems like the simplest approach. If you want
to wrap that in StringReader, you can, but you can also just work
with Strings.
Otis
- Original Message
From: Ryan O'Hara <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, October 16, 2006 4:28:3
with
Strings.
Otis
- Original Message
From: Ryan O'Hara <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Monday, October 16, 2006 4:28:35 PM
Subject: Help with Custom Analyzer
I have a few questions regarding writing a custom analyzer.
My situation is that I w
ed to Lucene, that's all up to you. Changing
the String seems like the simplest approach. If you want to wrap that in
StringReader, you can, but you can also just work with Strings.
Otis
- Original Message
From: Ryan O'Hara <[EMAIL PROTECTED]>
To: java-user@lucene
I have a few questions regarding writing a custom analyzer.
My situation is that I would like to use the StandardAnalyzer but
with some data-specific rules. I was wondering if there was a way of
telling the StandardAnalyzer to treat a string of text, that would
normally be tokenized into m
