Slash Boxes

All the Perl that's Practical to Extract and Report

More | Login | Reply
Loading... please wait.
  • One major problem with YAML files [], is support for Unicode, more specifically: different YAML parsers have a different default for assuming a file is in UTF-8, or not.

    Why would we need Unicode? Most of all, to spell people's names correctly.

    My proposal to resolve the issue is to have a default encoding for plain text files, my preference being ISO-Latin-1 (which is, I presume, the default for source code on CPAN, too...?), and that for using Unicode (including UTF-8), it requires a BOM marker [].

    (p.s. I cannot

    • Already there in the "Other brainstorming" section:

      * Make Unicode support explicit (whether allowed or prohibited)

      If someone expands that into a proper proposal, it will be considered.

      To be clear, the proposal process is not a "wishlist" process. The working group is not volunteering to implement every suggestion anyone has.

      Proposals that someone cares enough to write up formally indicate issues that are important enough for someone to invest time in. If it's not important enough for someone to spend ti

      • Isn't YAML 1.1 specified to be utf-8 anyway?

        • The current CPAN META Spec is implemented in YAML 1.0 and few of the existing Perl YAML parsers are 1.1 ready. That's part of the issue.

          -- dagolden

          • Anyway, I will write a proposal to define the META spec in terms of (Perl) data structures, and not anymore in terms of YAML. Though examples could still be in YAML (it's more readable than Perl or JSON or anything else); and there should be an appendix with recommended serialization formats (which would be YAML 1.0/1.1/Tiny/whatever, but probably also a Perl data dump).