[
https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2167:
--------------------------------
Attachment: LUCENE-2167.patch
New patch incorporating Uwe's JFlex TLD macro generation patch (with a few
small adjustments), and also including a jflex grammar for a new class:
NewStandardTokenizer. This grammar adds recognition of URLs, e-mail addresses,
and host names and IP addresses (both v4 and v6) to the UAX29Tokenizer grammar.
This is a work in progress -- testing for http: scheme URLs and e-mail
addresses is included, but there is no testing yet for the file:, https:, or
ftp: schemes.
I have dropped the idea of recognizing mailto: URIs, because these seem more
complicated than they are worth (mailto: URIs can include multiple email
addresses, comments, full email bodies, etc.). E-mail addresses within mailto:
URIs should still be recognized.
WARNING: I had to invoke Ant with a 900MB heap ({{ANT_OPTS=-Xmx900m ant jflex}}
on Windows Vista, 64 bit Sun 1.) in order to allow the JFlex generation process
to complete for NewStandardTokenizer; the process also took a minute or two to
finish.
> Implement StandardTokenizer with the UAX#29 Standard
> ----------------------------------------------------
>
> Key: LUCENE-2167
> URL: https://issues.apache.org/jira/browse/LUCENE-2167
> Project: Lucene - Java
> Issue Type: New Feature
> Components: contrib/analyzers
> Affects Versions: 3.1
> Reporter: Shyamal Prasad
> Assignee: Steven Rowe
> Priority: Minor
> Attachments: LUCENE-2167-jflex-tld-macro-gen.patch,
> LUCENE-2167-jflex-tld-macro-gen.patch, LUCENE-2167-jflex-tld-macro-gen.patch,
> LUCENE-2167-lucene-buildhelper-maven-plugin.patch,
> LUCENE-2167.benchmark.patch, LUCENE-2167.patch, LUCENE-2167.patch,
> LUCENE-2167.patch, LUCENE-2167.patch, LUCENE-2167.patch, LUCENE-2167.patch,
> LUCENE-2167.patch, LUCENE-2167.patch, LUCENE-2167.patch, LUCENE-2167.patch,
> LUCENE-2167.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> It would be really nice for StandardTokenizer to adhere straight to the
> standard as much as we can with jflex. Then its name would actually make
> sense.
> Such a transition would involve renaming the old StandardTokenizer to
> EuropeanTokenizer, as its javadoc claims:
> bq. This should be a good tokenizer for most European-language documents
> The new StandardTokenizer could then say
> bq. This should be a good tokenizer for most languages.
> All the english/euro-centric stuff like the acronym/company/apostrophe stuff
> can stay with that EuropeanTokenizer, and it could be used by the european
> analyzers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
