Menu
▾
▴
#176 Unicode characters such as Chinese in the To Do List window won't display correctly if the .pas source file is in ANSI encoding
Unicode characters such as Chinese in the To Do List window won't be displayed correctly if the .pas source file is in ANSI encoding (which is the default encoding), but it's ok if change the encoding to utf8.
I'd need some example files for this and also some screen shots how they are supposed to look (But my Windows will probably not display it correctly anyway.)
Hello Thomas,
Thanks for your attension to this issue. I have a new situation - all my problemetic units have been converted to utf8 some time ago, and just now I tried creating a unit file, added a todo item with some Chinese characters in it, and the To Do List view displayed it correctly. I'm using SVN REV 3090.
Maybe the issue only happen if the unit file was created with an older version of Delphi (maybe D7) on a old version of Windows system in Chinese, not sure...
l'll update you on the issue once I discovered more new details.
Hello Thomas,
I don't know if my problem is the same. I can see, that in installed GExpert 1.3.18 in Delphi 7 and in Delphi XE5 I don't have Polish characters in "Editor Bookmarks".
In Delphi 7 the same problem I have also in "Message Dialog" (in XE5 it's OK).
No problem with "ToDo List" in both IDEs.
You can see in attached screenshot - one is taken from Delpi 7, second from XE5.
Btw - as you can see I have dark interface in my Windows. In Delphi XE5 I have also all IDE made dark using Delphi IDE Colorizer. It could be fine to have possibility to change background and font color for Editor Bookamrks or have it in colors of editor.
Partly fixed for Delphi 6 and 7 in revision #5272: These versions did not support UTF-8 source so they now do not try to convert UTF-8 to ANSI which might have mangled the characters.
Later Delphi versions automatically change source code to UTF-8 if they contain non-ASCII characters so this should be a non-issue. But even if they don't, there is nothing I can do about it, because on the file level without a BOM there is no reliable way to distinguish between UTF-8 and ANSI.