Tweet
BC3 seems to prefer European encodings over others when auto detecting.
I'm on a Japanese version of Windows XP and have a Shift-JIS encoded file. Using the "ANSI" encoding will correctly display the file (since the system's default code page is Shift-JIS). Using "DOS/OEM" or "Japanese (Shift-JIS)" will also work.
BC3 however chooses "Turkish (Windows)" for one file and "Western European (Windows)" for another. (Both of which are correct in terms of there being no encoding errors.)
I read in another thread that BC3 is using IE's encoding detection component(?) and there isn't much that can be changed.
Could BC3 also offer the locale specific auto-detection that IE provides such as "Japanese (Auto-detect)" to deal with the dilemma in detecting encodings with similar character sets?
I'm on a Japanese version of Windows XP and have a Shift-JIS encoded file. Using the "ANSI" encoding will correctly display the file (since the system's default code page is Shift-JIS). Using "DOS/OEM" or "Japanese (Shift-JIS)" will also work.
BC3 however chooses "Turkish (Windows)" for one file and "Western European (Windows)" for another. (Both of which are correct in terms of there being no encoding errors.)
I read in another thread that BC3 is using IE's encoding detection component(?) and there isn't much that can be changed.
Could BC3 also offer the locale specific auto-detection that IE provides such as "Japanese (Auto-detect)" to deal with the dilemma in detecting encodings with similar character sets?
Comment