Re: [Yaml-core] encoding and external files

[Clark C. E. <cc...@cl...>]

On Tue, Oct 18, 2005 at 09:51:38PM +0100, Nuno Carvalho wrote:
| How I say in a yaml file which encoding is used?
| like in xml in <?xml version="1.0" encoding="UTF-8"?>

It is assumed to be UTF-8 unless there is a byte order mark
specifying a UTF-16 encoding.  Hope this helps.

http://yaml.org/spec/current.html#id2513364
  
   All characters mentioned in this specification are Unicode code
   points. Each such code point is written as one or more octets
   depending on the character encoding used. Note that in UTF-16,
   characters above #xFFFF are written as four octets, using a surrogate
   pair. A YAML processor must support the UTF-16 and UTF-8 character
   encodings. If a character stream does not begin with a byte order
   mark (#FEFF), the character encoding shall be UTF-8. Otherwise it
   shall be either UTF-8, UTF-16 LE or UTF-16 BE as indicated by the
   byte order mark. On output, it is recommended that a byte order mark
   should only be emitted for UTF-16 character encodings. Note that the
   UTF-32 encoding is explicitly not supported. For more information
   about the byte order mark and the Unicode character encoding schemes
   see the Unicode FAQ.

| Is there a way to yaml parser read external files?
| - name      : story
|   author    : John Doe
|   file      : file.txt
| 
| where file was the content of file.txt.

No, there is (deliberately) no concept of external-entities.  If you
need such a thing, you should roll your own mechanism.  There has been
talk (but no proposal) for a !!include data type, which would instruct a
post-processor that knew about this data type to open the file and
replace itself with the appropriate content.

Hope this helps,

Best,

Clark