Phillip Holmes wrote: >Think of UTF-8,16, etc as the telephone line and the charset as the >conversation over it. >For DBCS(double byte character sets), you'll need UTF-16 (double byte >telephone line) to properly handle the charset.
Huh? If that were true, how would you ever use UTF-8 to encode Unicode data? (Which is what it's generally used for; and Unicode actually has more than two bytes worth of characters now.) Sixten ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260930 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4