[ 
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

This patch contains 3 modifications: 
# The {{IPv6Address}} macro in {{StandardTokenizerImpl.jflex}} now makes 
everything in front of the double colon optional, so that e.g. "::" alone is a 
valid address.
# The {{EMAILbracketedHost}} macro in {{StandardTokenizerImpl.jflex}} now 
contains IPv6 and IPv4 addresses, along with a comment about how DFA 
minimization keeps the size of the resulting DFA in check.
# Renamed the {{EMAILaddressStrict}} macro to {{EMAIL}} in 
{{StandardTokenizerImpl.jflex}}.
# The {{root.zone}} file format has changed (hunh? why? I don't know anything 
about DNS...), so I modified {{GenerateJflexTLDMacros.java}} to parse the 
current format in addition to the previous format.

This version looks roughly the same in terms of performance - below are the 
numbers for the 25 round, 20k doc benchmark:

||Operation||recsPerRun||rec/s||elapsedSec||
|ClassicTokenizer|2467769|661,245.69|3.73|
|ICUTokenizer|2481688|544,827.25|4.55|
|RBBITokenizer|2481688|571,817.50|4.34|
|StandardTokenizer|2481687|650,848.94|3.81|
|UAX29Tokenizer|2481688|655,317.69|3.79|

For some reason, the size of the .class file for 
{{StandardTokenizerImpl.jflex}} is smaller: 51,798 bytes.


> 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: Robert Muir
>            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.benchmark.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, LUCENE-2167.patch, LUCENE-2167.patch, LUCENE-2167.patch, 
> LUCENE-2167.patch, standard.zip, StandardTokenizerImpl.jflex
>
>   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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to