From: Nathan S. <nis...@ts...> - 2004-06-05 16:52:36
|
On Jun 4, 2004, at 11:00, Clark C. Evans wrote: > On Fri, Jun 04, 2004 at 07:17:33AM +0100, Peter Murphy wrote: > | I was wondering about that. In earlier YAML specs, it mandated > UTF-32, > | UTF-16 and UTF-8. In the January one, UTF-32 disappeared. What > | happened to it? > > Someone suggested we support UTF-7, ISO 8859-X (for Europe), UCS-4 [1]. > We need to draw the line somewhere, and no one has provided a real-life > need for UTF-32 (yet). Since UTF-16 and UTF-8 are the most common, > I'm > very happy to limit our encoding requirements to these two formats. > We chose to be 'restrictive' for now, we can always losen the > restriction when more YAML parsers actually support UTF-8 and 16. > Also, as another data point, XML parsers are only required to parse UTF-8 and -16. |