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 <[EMAIL PROTECTED]> wrote: > Is UTF-8 guaranteed not to have any internal null bytes? _______________________________________________ Libcdio-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/libcdio-devel
