Well, I can understand that now is not the time to bring it up, as they're too close to release, but I hope to bring it up for the next version.  If for no other reason than I've been stung by mistakes while hand editing a string...

Douglas Mayle

On Apr 21, 2009, at 9:43 AM, Brad Baxter wrote:

On Sat, Apr 18, 2009 at 8:52 PM, Douglas Mayle <dmayle@dmayle.com> 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):


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).