Re: EBML data type constraints
Jerome Martinez <[email protected]>
| Newsgroups | gmane.comp.multimedia.matroska.devel |
|---|---|
| Message-ID | <[email protected]> |
Le 02/07/2015 16:21, wm4 a écrit : > On the other hand, allowing zero-padded strings will cause weirdness > with other languages which do byte strings, and where a zero byte > won't automatically terminate a string. IMHO this stupid detail should > just be disallowed (or deprecated). In that case, I propose: String - Printable ASCII (0x20 to 0x7E) Muxers MUST NOT append any NULL byte Demuxers SHOULD accept NULL padding when present and consider such bytes as non existent. UTF-8 - Printable Unicode string (Unicode character value >=0x20) conforming to RFC 2279 Muxers MUST NOT append any NULL byte Demuxers SHOULD accept NULL padding when present and consider such bytes as non existent. _______________________________________________ Matroska-devel mailing list [email protected] http://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel