Re: Phone encodings (revisited)

"Roger Binns" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <009f01c6568f$216950e0$07000100@rogersqyvr14d3>
> It should iterate through the supported charsets untill the 
> conversion is successful.  

That is by far the worst way of doing it!  If you had a random
stream of bytes and wanted to convert to unicode then telling
it to use almost any encoding would work.  Conversely going
from unicode to a particular byte encoding will often give
you errors, even if the encoding is correct.  The *ONLY* way
to do conversions correctly is if you know what the encoding is.

Joel has a good article on Unicode:

  The Absolute Minimum Every Software Developer Absolutely, 
  Positively Must Know About Unicode and Character Sets 
  (No Excuses!)

 http://www.joelonsoftware.com/articles/Unicode.html

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.