Community
Participate
Working Groups
In fact, the only way to read a file with an encoding other than the workbench default is to read it in wrong and then re-read it. This is odd. The code is a bit odd, too. StorageDocumentProvider createDocument() calls getEncoding() which wants to get the incoding from StorageInfo which hasn't been created yet. So it returns null which is later replaced by the default. This is obviously the point at which auto-detection or other encoding determination should be done, but of course at that point there is no place to save the encoding so it will get into the info.
*** This bug has been marked as a duplicate of 5399 ***