On Sat, Mar 22, 2008 at 12:14 AM, Micah Cowan <[EMAIL PROTECTED]> wrote:
> YAML uses UTF-8; I'm beginning to think YAML may not be what we want,
> though, given that the definition for a given entry may be interposed
> with defining content for other entries; I don't want to kludge that by
> suffixing the names or something. I'll have to look more into YAML to
> see how doable that is.
YAML handles hierarchical data, for example
Session:
- date: 10102008
- files:
-
url: http://...
- headers:
- status: 200
> If we did end up using YAML, then obviously we wouldn't accept arbitrary
> byte valus: it'd be UTF-8 only.
Isn't UTF-8 writes the same byte value with ASCII encoding for ASCII
characters? So we can pretend when reading the session file that it is
in UTF-8 while using ASCII when writing to it.
