[DIRSTUDIO-1114] Bad encoding used in text editor for binary data

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0-M10 (2.0.0.v20151221-M10)
• Fix Version/s: 2.0.0-M12
• Component/s: studio-ldapbrowser
• Environment: Windows 7 x64
• Assignee: Stefan Seelmann
• Reporter: Nagy Attila
• Created: 31/Aug/16 13:01
• Updated: 18/Apr/20 11:41
• Resolved: 01/Sep/16 21:59

Description

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)