Unicode VS ANSI encoded files on Windows Mobile Devices

Unicode VS ANSI encoded files on Windows Mobile Devices

• Eric66

  1952:

  - You know, this two digit field for a year will be broken in 2000...

  - It’s almost 50 years from now, there’s no way this application will be around that long.

  - Of course, you right. Let’s save two bytes, it’s important.

   

  UTF-8 is Unicode encoding, so yes, you can and should stick with it. Also see this: http://www.joelonsoftware.com/articles/Unicode.html

  
  
  

• Shobha69358

  Hi Ilya,

  Thanks for your advise on this. Interesting article, looks like I need to take more cosideration for the global populous :)

  Oh yeah 1952 - I earned a lot of money in 1999 <bg>

  
  

• DavidThi808

  Hi Ilya,

  Thanks for your prompt reply.

  I know keeping an application globalization ready is a good practice. I doubt much that the application in question will go global though <g>

  I'm in no need for international characters and plain old ASCII codes are acceptable to me. Does this mean I can stick with a UTF-8 encoded text file I'm not that worried I suppose, if I have to I will go Unicode. If its less hassle I'll make the encoding Unicode ;)

  Thanks

  
  

• Bertrand Caillet

  You should always use Unicode, that would make your application globalization ready. As to size, UTF-8 encoding matches ASCII for all ASCII characters, so unless you're using international characters size will be the same. The big difference is what you actually can use international characters if needed with UTF-8.
  
  
• Unicode VS ANSI encoded files on Windows Mobile Devices