Martin Thomson <[email protected]> wrote: >> just let people do their own thing, with perhaps some text >> somewhere about the impacts of those choices?
> While I personally agree with Carsten, I can recognize that as a
> personal preference thing. (I recently moved from wrapped text to
> clause-per-line and find that it works better with revision control
> systems.)
Yes, exactly.
I find that as soon as people see the different on git{hub,lab,diff} that
they instantly realize it's better.
So many people are still commiting with trailing spaces.
Many repos still without any kind of Makefile.
> I think that Ekr's point here is the only reasonable outcome of this
> discussion. The group of people working on a document can set some
> norms. I do think that it is useful to have the markdown source
> formatting retained as much as possible in XML (and HTML, because why
> not), because that makes it easier to detect changes, but that's
> inconsequential.
I agree it's a design team decision.
I am however, reminded of quote from Thomas the Tank Engine's Duck engine.
(An engine imported to the Island of Sodor from the Great Western Railway)
https://ttte.fandom.com/wiki/Duck
"There is the Great Western Way, and the Wrong Way"
The question remains, when the RPC edits text, whether XML or kramdown,
ought they do a do-nothing pass where they change to NSNL.
Assume that there is a tool to do this.
If not, ought they at least attempt NSNL for any changes that *they* make.
{I'd really like that part}
Many people doing XML editing will:
1. NSNL
2. indent paragraphs to match document structure
3. maintain comments above each <section> noting what section number it turns
into.
(Because comments on ML are usually about section 4.3.2)
All of the above then goes against people who then open the document XMLmind,
and then save it, and then wonder why every single line is a diff.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
