[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libcdio-devel] Iconv usage and string handling
From: |
Peter Creath |
Subject: |
Re: [Libcdio-devel] Iconv usage and string handling |
Date: |
Tue, 25 Apr 2006 12:27:38 -0400 |
Answering my own question, it looks like UTF-8 is strings.h-safe, and
it looks like the default type is a plain old char*. (See wcsrtombs).
That makes me feel better, since it looks like bugs resulting from
sloppy coding will simply be incorrect display; not crashing,
string-mangling, or other hard-to-find glitches.
Is that others' experience with UTF-8 as well?
On 4/25/06, Peter Creath <address@hidden> wrote:
> Is UTF-8 guaranteed not to have any internal null bytes?
- [Libcdio-devel] Iconv usage and string handling, Burkhard Plaum, 2006/04/21
- Re: [Libcdio-devel] Iconv usage and string handling, Diego 'Flameeyes' Pettenò, 2006/04/21
- Re: [Libcdio-devel] Iconv usage and string handling, Peter Creath, 2006/04/21
- Re: [Libcdio-devel] Iconv usage and string handling, plaum, 2006/04/22
- Re: [Libcdio-devel] Iconv usage and string handling, Peter Creath, 2006/04/24
- Message not available
- Re: [Libcdio-devel] Iconv usage and string handling, Peter Creath, 2006/04/25
- Re: [Libcdio-devel] Iconv usage and string handling,
Peter Creath <=
- Re: [Libcdio-devel] Iconv usage and string handling, Burkhard Plaum, 2006/04/25
- Re: [Libcdio-devel] Iconv usage and string handling, Peter Creath, 2006/04/26