Re: New standard...
Brad Baxter <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Apr 18, 2009 at 8:52 PM, Douglas Mayle <[email protected]> wrote: > Because YAML supports other object types on the same line, the colon > is an ambiguous character. This means that when a human is editing a > YAML document, they have to take care to quote any strings containing > a colon, which introduces other issues. For example: > > I want to encode the sentence "Beef: it's what's for dinner" under the > 'doc' key. This would end up as: > > doc: 'Beef: it''s what''s for dinner' > > As regards human editing, there are more than just the colon that a human must watch for. I brought this up some time ago, starting here (if my email client doesn't mangle it): http://sourceforge.net/mailarchive/forum.php?forum_name=yaml-core&style=nested&viewmonth=200603&viewday=27 I confess I haven't studied recent changes to see if any of these observations are affected. What about: doc = Beef: it's what's for dinner Sort of like ini files. I doubt that will fly, but it would sure be nice to have a good answer (besides using quotes). Regards, Brad ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Yaml-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yaml-core