lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-2167) Implement StandardTokenizer with the UAX#29 Standard
Date Thu, 27 May 2010 07:19:37 GMT


Uwe Schindler commented on LUCENE-2167:

Hi Steven,

looks cool, I have some suggestions:
- Must it be a maven plugin? From what I see, the same code could be done as a simple Java
Class with main() like Roberts ICU converter. The external dependency to httpclient can be
replaces by simply and the URL itsself (you can even set the no-cache
directives). Its much easier from ant to invoke a java method as a build step. So why not
refactor a little bit to use a main() method that acceps the target directory.
- You use the HTML root zone database from iana. The format of this file is hard to parse
and may change suddenly. BIND administrators know, that there is also the root zone file available
for BIND in ste standardized named-format @ [] (ASCII
only, as DNS is ASCII only). You just have to use all rows that are not comments and contain
"NS" as second token. The Nameservers behind are not used, just use the DNS name before. This
should be much easier to do. A python script may also work well.
- You can write the Last-Modified-Header of the HTTP-date (HttpURLConnection.getLastModified())
also into the generated file.
- The database only contains the punycode enabled DNS names. But users use the non-encoded
variants, so you should decode punycode, too [we need ICU for that :( ] and create patterns
for that, too.
- About changes in analyzer syntax because of that: This should not be a problem, as the IANA
only *adds* new zones to the file and very seldom removes some (like old yugoslavian zones).
As eMails and Webadresses should *not* appear in tokenized text *before* they are in the zone
file, its no problem that they suddenly later are marked as "URL/eMail" (as they cannot appear
before). So in my opinion we can update the zone database even in minor Lucene releases without
breaking analyzers.

Fine idea!

> Implement StandardTokenizer with the UAX#29 Standard
> ----------------------------------------------------
>                 Key: LUCENE-2167
>                 URL:
>             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-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
>   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:
For additional commands, e-mail:

View raw message