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

Emmanuel Lecharny commented on DIRSTUDIO-802:
---------------------------------------------

Damn! I know see what you mean (thanks for the attachments).

Ok, we will have a look at this tool. Not sure that it's a good one though : we 
should let the user select his charset instead of forcing ISO8859-1 (except if 
it uses the platform locale).
                
> confusion between ISO-8859-1 and UTF-8 in the encode/decode LDAP gui tool
> -------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-802
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-802
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>         Environment: Windows XP pro
>            Reporter: julien2512
>            Priority: Minor
>              Labels: decode, encode, iso-8859-1, utf8
>         Attachments: encode-decode LDAP demo 1.PNG, encode-decode LDAP demo 
> 2.PNG
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The encode/decode tool (from the LDAP menu) gives "aGVydsOp" for BASE-64 
> encoding from the ISO-8859-1 string "hervé".
> while the website http://www.base64decode.org/   gives the same results from 
> the same string but in UTF-8.
> Also UTF-8 BASE 64 encoding of Apache Directory Studio match with ISO-8859-1 
> BASE64 encoding of the previous website.
> The result from my own java code match with that website.
> I think there is a confusion between ISO-8859-1 and UTF-8 in the 
> encode/decode LDAP gui tool of Apache Directory Studio.
> It will be easy to fix.

--
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


Reply via email to