[gmpi] Re: string encoding in teh API (UTFs)
- From: Jeff McClintock <jeffmcc@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Thu, 15 Dec 2005 07:30:12 +1300
> You're still ignoring all the other issues.
Well I decided to use wide-chars (UCS-2) based on this article...
"The Absolute Minimum Every Software Developer Absolutely, Positively
Must Know About Unicode and Character Sets (No Excuses!)"
http://www.joelonsoftware.com/articles/Unicode.html
It discusses most of the points you raise.
I guess you may not agree that UCS-2 (16 bit wide-char) is the way to
go. But I hope it at least explains my reasoning (better than I can).
Best Regards,
jeff
----------------------------------------------------------------------
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
- Follow-Ups:
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin
- 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: Jeff McClintock
- [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)
---------------------------------------------------------------------- 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.
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin
- [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: Jeff McClintock
- [gmpi] Re: string encoding in teh API (UTFs)
- From: thockin