Jump to content

unicode file names


ehk
 Share

Recommended Posts

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.

Link to comment
Share on other sites

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.

 

post-1629-1133689753_thumb.jpg

 

post-1629-1133690043_thumb.jpg

Link to comment
Share on other sites

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!

Link to comment
Share on other sites

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!

Link to comment
Share on other sites

  • 2 weeks later...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.