ehk Posted December 3, 2005 ImgBurn does not properly display unicode file names (Japanese in my case). I am using ImgBurn with Windows 2000 (Japanese edition). Presumably, this is a problem with with the font being used for file name display since the programme appears to process the ISO files correctly. Share this post Link to post Share on other sites
LIGHTNING UK! Posted December 3, 2005 I've made no attempt to make anything support unicode... so it's quite possible it doesn't work! Do you have a small image (i.e. 5mb - or can you please make one?) so that I can see what you mean and try to fix it. Thanks. Share this post Link to post Share on other sites
ehk Posted December 4, 2005 I'm not sure what you mean by an image file - an ISO file or a screen image? I'm guessing, probably wrongly, that you want a screen image. I've provided two: the first is ImgBurn with the garbaged file names; the second is the proper file name from 2xexplorer, a freebie European language file manager that works perfectly with Japanese. I don't think you need a real ISO file with a unicode name to check your code. Any random file with a multibyte/unicode file name and an ISO extension, even if it isn't a real ISO file should allow you to trace the error. Or you can take an existing ISO file that you have, copy a bit of Chinese, Japanese, or Korean text from somewhere. Replace your existing file name with this bit of text and play around with it. Given that Winblows since 2000 on is unicode based, I would assume there is some incentive for professional programmers to learn how to code properly for international usage. The Microsoft MSN developer site has a number of items on proper programming for multi-language usage. Share this post Link to post Share on other sites
LIGHTNING UK! Posted December 4, 2005 I'm not a professional programmer I also don't use Microsoft tools for development. All the components in Borland tools make use of something called an AnsiString... and that (as you can tell from it's name), only supports Ansi characters. I don't believe there are WideString (Unicode) versions available at this time, perhaps in the next version of the development environment they will have addressed this issue. In the mean time, sorry! Share this post Link to post Share on other sites
ehk Posted December 4, 2005 I'm not a professional programmer I also don't use Microsoft tools for development. All the components in Borland tools make use of something called an AnsiString... and that (as you can tell from it's name), only supports Ansi characters. I don't believe there are WideString (Unicode) versions available at this time, perhaps in the next version of the development environment they will have addressed this issue. In the mean time, sorry! Share this post Link to post Share on other sites
Qyngali Posted December 13, 2005 Try changing the locale settings for non unicode programs to english us or uk. Or download and run apploc to set it for specific programs only. The Microsoft AppLocale Utility: http://www.microsoft.com/globaldev/tools/apploc.mspx Share this post Link to post Share on other sites
