[gmpi] Re: string encoding in teh API (UTFs)
- From: Sebastien Metrot <meeloo@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 14 Dec 2005 20:28:14 +0100
thockin@xxxxxxxxxx wrote:
UTF-16 is not a standard Windows feature. Win32 uses UCS-2.
Great, so Windows doesn't even support Unicode fully.
At least they don't change their mind about what subset of Unicode they
support and what encoding converters their provide with every OS
revision as do some fruity companies...
I'm trying to make a fair opinion, but it really seems to me that UTF-8 is
the standards-supported option for making data cross compiler boundaries.
....
I totaly agree with Tim. UTF-8 all the way...
Sebastien
----------------------------------------------------------------------
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
- References:
- [gmpi] Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] string encoding in teh API (UTFs)
- From: thockin
- [gmpi] Re: string encoding in teh API (UTFs)
- From: Jeff McClintock
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin
- [gmpi] Re: string encoding in teh API (UTFs)
- From: Sebastien Metrot
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin
Other related posts:
- » [gmpi] string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
- » [gmpi] Re: string encoding in teh API (UTFs)
UTF-16 is not a standard Windows feature. Win32 uses UCS-2.
Great, so Windows doesn't even support Unicode fully.
I'm trying to make a fair opinion, but it really seems to me that UTF-8 is the standards-supported option for making data cross compiler boundaries.
Sebastien
- [gmpi] Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: thockin
- [gmpi] Re: Querying a plugin's structure (params, IOs, etc)
- From: Jeff McClintock
- [gmpi] string encoding in teh API (UTFs)
- From: thockin
- [gmpi] Re: string encoding in teh API (UTFs)
- From: Jeff McClintock
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin
- [gmpi] Re: string encoding in teh API (UTFs)
- From: Sebastien Metrot
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin