Re: encoding and content in YML files

Sorry for the late reply:
This is what I mean for actual characters:
ጒፄ䢘䔲

unicode code points:
\u1312\u1344\u4898\u4532


From: Oren Ben-Kiki 
Sent: Thursday, October 08, 2015 2:36 AM
To: jose isaias cabrera 
Cc: Yaml Core 
Subject: Re: [Yaml-core] encoding and content in YML files

Not sure what you mean by "the actual characters vs. the Unicode code points". The _only_ thing a physical file can contain is some _encoding_ of "the actual characters". If someone sees garbage displaying the file, probably his font doesn't support the used characters, or his system doesn't support the encoding, or something like that.

On Thu, Oct 8, 2015 at 12:14 AM, jose isaias cabrera <[email protected]> wrote:


  thanks for the reply...

  I know what Unicode and the various UTF-XX formats are.  So, you're missing the "point" ;-) he he he.  Thanks for pointing me to the site referenced below.  That helped me.  Unicode code points are not Unicode display characters, such as ε, φ, é, ñ, α, etc.  they are displayed as codes, such as \u039A, \u03BB, \u03B5, \u03AF, etc. So, in other words, what YAML files need are Unicode code points, \uxxxx, instead of the actual characters. So, why can't YML take the actual characters vs. the Unicode code points?  The reason why I know this is because I gave someone a YML UTF-8 encoded with characters set and the person told me that they appeared as garbage.  Anyway, my personal opinion is that YML suffers by not allowing the characters.

  thanks.

    ----- Original Message ----- 
    From: Oren Ben-Kiki 
    To: jose isaias cabrera 
    Cc: Yaml Core 
    Sent: Wednesday, October 07, 2015 12:24 AM
    Subject: Re: [Yaml-core] encoding and content in YML files

    Valid UTF-8 encoding is an encoding of "Unicode code points" :-) 

    "Unicode code points" is a technical term - http://gedcom-parse.sourceforge.net/doc/encoding.html is an OK explanation. Unicode code points (or "Unicode characters", if you want to be less formal) are in the range 0 to 10FFFF. Obviously you can't encode one such beast in one byte. Hence, Unicode supports multiple ways of expressing these code points as a sequence of bytes, UTF-8 being one such way to encode them, as are the two UTF-16 (big and small endian) encodings.

    On Wed, Oct 7, 2015 at 12:48 AM, jose isaias cabrera <[email protected]> wrote:


      Greetings!

      I have searched all over the internet for answers, and even on the YAML documentation, c5.2, it's not clear to me. The statement,

      All characters mentioned in this specification are Unicode code points.

      in here,

      http://www.yaml.org/spec/1.2/spec.html#id2771184

      is confusing.  Maybe is because I don't understand what "Unicode code points" means.  So, does this mean that all .yml files can not have characters such as é or ñ, etc.?  I would expect that a valid UTF encoding on the .yml file should be ok to have these unicode actual characters.  Thanks for your support.

      josé

      ------------------------------------------------------------------------------

      _______________________________________________
      Yaml-core mailing list
      [email protected]
      https://lists.sourceforge.net/lists/listinfo/yaml-core

------------------------------------------------------------------------------

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core