[
https://issues.apache.org/jira/browse/DIRSTUDIO-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456750#comment-15456750
]
Stefan Seelmann commented on DIRSTUDIO-1114:
--------------------------------------------
Fixed: http://svn.apache.org/viewvc?rev=1758860&view=rev
You are right, the default system encoding was used to convert the binary data
to string. I choosed to always use UTF-8 instead of checking the workspace
setting because the edited data is not loaded from local filesystem but from
remote LDAP server, and in general LDAP uses UTF-8.
> Bad encoding used in text editor for binary data
> ------------------------------------------------
>
> Key: DIRSTUDIO-1114
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1114
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 2.0.0-M10 (2.0.0.v20151221-M10)
> Environment: Windows 7 x64
> Reporter: Nagy Attila
> Priority: Minor
> Fix For: 2.0.0-M12
>
>
> On windows when an octet string ("Binary Data" as displayed by Directory
> Studio) is being edited as text (double click on attribute then click "Edit
> as Text..." in the opened hex editor) wrong encoding/code page is used and
> there is no way to set the encoding to the one that should be used.
> The Text Editor that is opened uses most likely CP1250 no matter what the
> string is encoded in. So an UTF-8 string is mostly uneditable.
> I assume the editor uses the default system encoding.
> I think this because on Linux the text is displayed/edited correctly, and
> nowadays Linux's use UTF-8 as default (albeit that would create the same
> artifacts if the strings were stored with some other encoding like eg.
> Windows-1252).
> The correct behavior for the Text Editor windows would be to honor the global
> Eclipse workspace setting regarding the encoding of text files.
> As about the concrete circumstances to reproduce the error:
> I was editing a vacationInfo attribute (OID: 1.3.6.1.4.1.11048.1.1.1.3 type:
> binary)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
