Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Lucene: Java-Dev

[jira] [Commented] (LUCENE-3747) Support Unicode 6.1.0

 

 

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded


jira at apache

Feb 2, 2012, 10:14 AM

Post #1 of 4 (34 views)
Permalink
[jira] [Commented] (LUCENE-3747) Support Unicode 6.1.0

[ https://issues.apache.org/jira/browse/LUCENE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199047#comment-13199047 ]

Robert Muir commented on LUCENE-3747:
-------------------------------------

+1 as soon as the icu release comes out we should start working on the update.

additional things for updating icu:
* check for any uax#29 differences (i think we are unaffected)
* update files in icu/src/data/utr30 (i really need to make a script to automate this, but it does document what has to happen)
* try again to remove the java7-workaround-hack in LuceneTestCase for http://bugs.icu-project.org/trac/ticket/8734


> Support Unicode 6.1.0
> ---------------------
>
> Key: LUCENE-3747
> URL: https://issues.apache.org/jira/browse/LUCENE-3747
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 3.5, 4.0
> Reporter: Steven Rowe
> Priority: Minor
>
> Now that Unicode 6.1.0 has been released, Lucene/Solr should support it.
> JFlex trunk now supports Unicode 6.1.0.
> Tasks include:
> * Upgrade ICU4J to v49 (after it's released, on 2012-03-21, according to http://icu-project.org).
> * Use {{icu}} module tools to regenerate the supplementary character additions to JFlex grammars.
> * Version the JFlex grammars: copy the current implementations to {{*Impl3<X>}}; cause the versioning tokenizer wrappers to instantiate this version when the {{Version}} c-tor param is in the range 3.1 to the version in which these changes are released (excluding the range endpoints); then change the specified Unicode version in the non-versioned JFlex grammars from 6.0 to 6.1.
> * Regenerate JFlex scanners, including {{StandardTokenizerImpl}}, {{UAX29URLEmailTokenizerImpl}}, and {{HTMLStripCharFilter}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Feb 2, 2012, 10:18 AM

Post #2 of 4 (30 views)
Permalink
[jira] [Commented] (LUCENE-3747) Support Unicode 6.1.0 [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199051#comment-13199051 ]

Steven Rowe commented on LUCENE-3747:
-------------------------------------

bq. check for any uax#29 differences (i think we are unaffected)

Right, I'm not sure about this - I plan on upgrading the JFlex test cases that implement the uax#29 rules and test against the data Unicode.org provides. I should know more once that's done.

> Support Unicode 6.1.0
> ---------------------
>
> Key: LUCENE-3747
> URL: https://issues.apache.org/jira/browse/LUCENE-3747
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 3.5, 4.0
> Reporter: Steven Rowe
> Priority: Minor
>
> Now that Unicode 6.1.0 has been released, Lucene/Solr should support it.
> JFlex trunk now supports Unicode 6.1.0.
> Tasks include:
> * Upgrade ICU4J to v49 (after it's released, on 2012-03-21, according to http://icu-project.org).
> * Use {{icu}} module tools to regenerate the supplementary character additions to JFlex grammars.
> * Version the JFlex grammars: copy the current implementations to {{*Impl3<X>}}; cause the versioning tokenizer wrappers to instantiate this version when the {{Version}} c-tor param is in the range 3.1 to the version in which these changes are released (excluding the range endpoints); then change the specified Unicode version in the non-versioned JFlex grammars from 6.0 to 6.1.
> * Regenerate JFlex scanners, including {{StandardTokenizerImpl}}, {{UAX29URLEmailTokenizerImpl}}, and {{HTMLStripCharFilter}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Feb 2, 2012, 10:26 AM

Post #3 of 4 (27 views)
Permalink
[jira] [Commented] (LUCENE-3747) Support Unicode 6.1.0 [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199064#comment-13199064 ]

Robert Muir commented on LUCENE-3747:
-------------------------------------

the "changes.txt" is here http://www.unicode.org/versions/Unicode6.1.0/ along with the log here:
http://www.unicode.org/reports/tr29/tr29-19.html#Modifications


> Support Unicode 6.1.0
> ---------------------
>
> Key: LUCENE-3747
> URL: https://issues.apache.org/jira/browse/LUCENE-3747
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 3.5, 4.0
> Reporter: Steven Rowe
> Priority: Minor
>
> Now that Unicode 6.1.0 has been released, Lucene/Solr should support it.
> JFlex trunk now supports Unicode 6.1.0.
> Tasks include:
> * Upgrade ICU4J to v49 (after it's released, on 2012-03-21, according to http://icu-project.org).
> * Use {{icu}} module tools to regenerate the supplementary character additions to JFlex grammars.
> * Version the JFlex grammars: copy the current implementations to {{*Impl3<X>}}; cause the versioning tokenizer wrappers to instantiate this version when the {{Version}} c-tor param is in the range 3.1 to the version in which these changes are released (excluding the range endpoints); then change the specified Unicode version in the non-versioned JFlex grammars from 6.0 to 6.1.
> * Regenerate JFlex scanners, including {{StandardTokenizerImpl}}, {{UAX29URLEmailTokenizerImpl}}, and {{HTMLStripCharFilter}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Feb 3, 2012, 11:49 AM

Post #4 of 4 (25 views)
Permalink
[jira] [Commented] (LUCENE-3747) Support Unicode 6.1.0 [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199985#comment-13199985 ]

Steven Rowe commented on LUCENE-3747:
-------------------------------------

{quote}
bq. check for any uax#29 differences (i think we are unaffected)

Right, I'm not sure about this - I plan on upgrading the JFlex test cases that implement the uax#29 rules and test against the data Unicode.org provides. I should know more once that's done.
{quote}

I've finished adding Unicode 6.1 versions to JFlex's UAX#29 test cases, including the word break rules test case, and the only change I noticed that could conceivably affect Lucene's UAX#29 tokenizers is the new Section 8, which discusses Korean syllables. Since the rules listed in that section are not part of the word break rules, but rather are a tailoring, and since that section says "All standard Korean syllable blocks used in modern Korean are of the form <L V T> or <L V> and have equivalent, single-character precomposed forms.", I don't think we need to support this (right now anyway).

(By contrast, the UAX#14 line break rules changed significantly between Unicode v6.0 and v6.1, and I'm still working to include a Unicode 6.1 version to JFlex's corresponding test case.)

> Support Unicode 6.1.0
> ---------------------
>
> Key: LUCENE-3747
> URL: https://issues.apache.org/jira/browse/LUCENE-3747
> Project: Lucene - Java
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 3.5, 4.0
> Reporter: Steven Rowe
> Priority: Minor
>
> Now that Unicode 6.1.0 has been released, Lucene/Solr should support it.
> JFlex trunk now supports Unicode 6.1.0.
> Tasks include:
> * Upgrade ICU4J to v49 (after it's released, on 2012-03-21, according to http://icu-project.org).
> * Use {{icu}} module tools to regenerate the supplementary character additions to JFlex grammars.
> * Version the JFlex grammars: copy the current implementations to {{*Impl3<X>}}; cause the versioning tokenizer wrappers to instantiate this version when the {{Version}} c-tor param is in the range 3.1 to the version in which these changes are released (excluding the range endpoints); then change the specified Unicode version in the non-versioned JFlex grammars from 6.0 to 6.1.
> * Regenerate JFlex scanners, including {{StandardTokenizerImpl}}, {{UAX29URLEmailTokenizerImpl}}, and {{HTMLStripCharFilter}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.