[jira] Created: (DIRSERVER-805) Supporting Unicode chars above 0xFFFF

Supporting Unicode chars above 0xFFFF
-------------------------------------

                 Key: DIRSERVER-805
                 URL: http://issues.apache.org/jira/browse/DIRSERVER-805
             Project: Directory ApacheDS
          Issue Type: Improvement
            Reporter: Emmanuel Lecharny
            Priority: Minor


The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.

For instance, the DN parsing is based on single chars, and surrogates are not handled at all.

Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-805:
----------------------------------------

    Fix Version/s: pre-2.0

Not sure that it worth the effort right now... Chars above 0xFFFF are generaly attributed to dead langages like ougaritic, old persean, etc ...

> Supporting Unicode chars above 0xFFFF
> -------------------------------------
>
>                 Key: DIRSERVER-805
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-805
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: pre-2.0
>
>
> The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.
> For instance, the DN parsing is based on single chars, and surrogates are not handled at all.
> Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny reopened DIRSERVER-805:
-----------------------------------------

      Assignee: Emmanuel Lecharny

> Supporting Unicode chars above 0xFFFF
> -------------------------------------
>
>                 Key: DIRSERVER-805
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-805
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Assignee: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.
> For instance, the DN parsing is based on single chars, and surrogates are not handled at all.
> Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-805.
-----------------------------------------

    Resolution: Won't Fix

> Supporting Unicode chars above 0xFFFF
> -------------------------------------
>
>                 Key: DIRSERVER-805
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-805
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Assignee: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.
> For instance, the DN parsing is based on single chars, and surrogates are not handled at all.
> Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-805.
---------------------------------------

> Supporting Unicode chars above 0xFFFF
> -------------------------------------
>
>                 Key: DIRSERVER-805
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-805
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Assignee: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.
> For instance, the DN parsing is based on single chars, and surrogates are not handled at all.
> Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRSERVER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-805.
---------------------------------------

    Resolution: Fixed

Let's close this right now. Will reopen it if someone needs it.

> Supporting Unicode chars above 0xFFFF
> -------------------------------------
>
>                 Key: DIRSERVER-805
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-805
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> The current implementation and handling of LdapStrings does not support characttres which are above unicode 0xFFFF. Even if Strings are translated to UTF-8 before being transfered to the server, we still convert them back to String inside the server. Some of those UTF-8 bytes may be encoded into 2 chars (if the UTF-8 bytes sequence contains 4 to 6 bytes), but all the manipulations of those Stri,g does not take into account such characters.
> For instance, the DN parsing is based on single chars, and surrogates are not handled at all.
> Even if not really important, because extended chars are not very common, this is something that should be fixed in 2.0

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.