Re: [Yaml-core] RE: in favor of DWIM use case over smushed paragraphs use case

[Steve H. <sh...@zi...>]

Retracting some of this, sorry...

----- Original Message -----
From: "Steve Howell" <sh...@zi...>
> > On Tue, Jul 02, 2002 at 12:25:45PM -0400, Steve Howell wrote:
> > | What's the convention for separting paragraphs in underlying data?
> > | Do folks typically separate paragraphs with one line feed or two?
> >
> > In previous systems I've worked on, we used a single carriage
> > return to separate each paragraph.  We could have used two
> > carriage returns... but I don't see the need.
>
> On a typewriter, you would hit two carriage returns between paragraphs to
> create the text you see here.  On paper, you would see two line feeds.  On
> your terminal, you would see two line feeds.

Keep above.

>
> In your underlying representation, though, there would only be one
paragraph
> separating the paragraphs.  But, then, in YAML, I'd have to supply three
> carriage returns.  THREE carriage returns!  (Until I got my YAML-optimized
> editor, I guess.)
>

Retract above.  Got off-by-oned.

> Why don't we just be consistent?  Let's assume most apps use two carriage
> returns as the paragraph separator.  Then, let's have YAML render the two
> carriage returns as two carriage returns.  A human typing YAML would then
> also use two carriage returns to see the YAML.  Then, when the YAML was
read
> by another human, they would know that the two carriage returns actually
mean
> two carriage returns.  I don't think this will be two difficult for most
> people two understand.
>

Keep above.

> Thanks,
>
> Steve
>