From: Steve H. <sh...@zi...> - 2002-07-02 17:59:03
|
> | 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. > > If we wanted to be consistent, then we wouldn't even have "folded" > style at all; as the literal block does just fine. The whole point > of folded style is to allow for information to be encoded in a way > that is readable in your standard 76 column limited terminal. My > content that I want to display nice in folded land, has very long > paragaphs separated by a single line. This is my use case and the > whole reason why I pushed for folded to begin with. Okay, since it's your use case, I won't argue any more. Let's document it better. I like the technique of showing the same data in both representations. Showing things in YAML goes a lot further than describing them in English. The spec might also talk about the use case a little more. Clearly, YAML's folding format will be optimized for the one-newline-between-paragraphs internal format. That's reasonable. > > I've already conceded that carriage returns surrounding indented > blocks should be signficant; which is IMHO, a great idea. However, > trying to change the established inter-paragraph rules is a > dead-on-arrival proposition. ;) Clark > Examples of that would be good too. Thanks, Steve |