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

Robert Muir edited comment on LUCENE-2019 at 10/30/09 10:30 PM:
----------------------------------------------------------------

Yonik, no. this is how i see it.

process-internal means just that, internal to processing. 
So if I want to use U+FDDF in some lucene process, say as a syllable delimiter 
or something like that, i should not have to worry about it being stored in a 
*portable index* as an abstract character (inside some term text)

again this is my interpretation, so if you guys disagree, please mark the issue 
as not fix, but i enjoy the discussion.

<edit addition>

here is an example use case, perhaps i want to make a Query that needs to do 
some fuzzy matching or something crazy for a difficult language.
i should be able to internally use any of these process-internal codepoints as 
delimiters in my processing (process-internal)
without worrying that they will be in the Term text from TermEnum. 

      was (Author: rcmuir):
    Yonik, no. this is how i see it.

process-internal means just that, internal to processing. 
So if I want to use U+FDDF in some lucene process, say as a syllable delimiter 
or something like that, i should not have to worry about it being stored in a 
*portable index* as an abstract character (inside some term text)

again this is my interpretation, so if you guys disagree, please mark the issue 
as not fix, but i enjoy the discussion.

  
> map unicode process-internal codepoints to replacement character
> ----------------------------------------------------------------
>
>                 Key: LUCENE-2019
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2019
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Robert Muir
>            Priority: Minor
>         Attachments: LUCENE-2019.patch
>
>
> A spinoff from LUCENE-2016.
> There are several process-internal codepoints in unicode, we should not store 
> these in the index.
> Instead they should be mapped to replacement character (U+FFFD), so they can 
> be used process-internally.
> An example of this is how Lucene Java currently uses U+FFFF 
> process-internally, it can't be in the index or will cause problems. 

-- 
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to