[gmpi] Re: string encoding in teh API (UTFs)

  • From: Sebastien Metrot <meeloo@xxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Wed, 14 Dec 2005 18:53:03 +0100

thockin@xxxxxxxxxx wrote:

It seems to me that UTF-16 has all the problems of UTF-8 and more, with
none of the advantages. The *only* thing it has going for it is Windows
and Mac. That shouldn't be ignored, but neither should the accompanying

UTF-16 is not a standard Windows feature. Win32 uses UCS-2. UTF-8 is the easiest way to go if you are not doing a word processor. strlen DOES work in the sense that it counts bytes, not glyphs so most program can work out of the box with UTF-8. You only need special handling if you are actually trying to interpret the text data (separate words, isolate glyphs, hyphenate, etc...). Most people don't have those needs and the ones that have the needs will learn how to do it properly which is not nearly as complicated as you make it sound :-).


Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: