On Sat, Aug 15, 2015 at 7:15 AM, Kerim Aydin <[email protected]> wrote: > Hey omd, > > Can you elaborate on what you mean by this? The Ruleset is > whitespace- inconsequential; formatting is wholly at Rulekeepor > discretion - the only thing that would "break" in non-fixed > width is the Town Fountain. Do you mean get rid of ALL indenting/ > nesting structure (i.e. bullets and lists)? > > The main concern with non-fixed-width is Report formatting, > it's the only way to do tables while keeping to the html-free > email medium.
What I was thinking of is just a script that would automatically detect paragraphs and indentation schemes in the ruleset and unwrap into semantic equivalents in HTML; it would require some special casing but shouldn't be that hard. Of course, an alternative would be maintaining an unwrapped version as the source format and doing the reverse transformation for list publication (or just being all modern and using HTML mail after repealing the rule against it, heh), but that's up to the Rulekeepor. (Pros: less use of heuristics required, easier to enforce style uniformity, word diff works better, and if it leads to non-indented rule text becoming the standard for proposals, newbies don't have to figure out how to indent things in order to have their proposals look spiffy. Cons: I actually find fixed-width text aesthetically appealing [but less friendly looking] and its relative uncommonness these days *for most people* could be said to add character; ASCII art could still be done with <pre> or whatnot but would look more out of place; the need to run the converter makes tech more of a prerequisite for future new Rulekeepors; and unwrapped text is harder to just read directly in git or whatever without special tools - but you were going to use a database anyway...)
