lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (LUCENE-2019) map unicode process-internal codepoints to replacement character
Date Fri, 30 Oct 2009 22:53:59 GMT

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

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

bq. And if I'm indexing to a RAM directory? The point is, the private-use char is never seen
external to the process (which includes both Lucene and it's index).

whoah, lets not confuse private-use characters with non-characters. there is a huge difference!!!!

<edit addition>

I see private-use characters as available to the end user, i.e. someone like DM Smith trying
to index Myanmar encoded in private-use chars (he mentioned this before).
These are available for his use.

control characters are available for your use to concatenate or do strange things.

process-internal (non-characters) should not be stored and are available for processing, without
concern that they will be treated as an abstract character.

      was (Author: rcmuir):
    bq. And if I'm indexing to a RAM directory? The point is, the private-use char is never
seen external to the process (which includes both Lucene and it's index).

whoah, lets not confuse private-use characters with non-characters. there is a huge difference!!!!
  
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message