>> Now that IETF has officially moved to XML as the sole format
>
> I'm not sure what you mean, can you provide a pointer? AFAICT, the
> latest published RFC is still only available as txt and pdf.
I meant that XML is the sole *input* format, per RFC 7990, but you're
right about the XML not currently being easily accessed. I've signed
up for the IETF 104 CodeSprint to fix this, as well as to introduce
folding support into the publishing process.
>> No, there are cases where this fails. We went thru this before.
>
> Only if you have data with > 69 spaces in a row that needs to be
> preserved.
More generally, anytime the fold occurs where space characters
follow.
But why are you arguing for this? - the double-backslash approach
works great for when indents are desired.
My interest in this thread was/is only to cover the common case
when there are no indents, and the continuation line always begins
on column 1, in which case the 2nd backslash is unneeded and
somewhat counterintuitive.
Kent // contributor
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
