[
Lists Home |
Date Index |
Thread Index
]
> The supposed problem with control characters in general is that the
> presence of those bytes in files causes problems. I am suggesting
> that UTF-16 already gives us those problems.
They do, and I agree that UTF-16 has the same issues.
> But the specificproblem with nul is in XML APIs. Any C API that uses
> nul-terminated strings will not be able to handle nuls in those
> strings. If the strings are UTF-16 strings, they are terminated by a
> UTF-16 nul character, not by a single zero byte. UTF-16 characters
> with zero bytes are not a problem.
XML parser/processor API's suffer the problem just as you say. Other non-XML
aware programs/libraries will suffer similarly... that it what I was getting
at.
|
