[rfc-i] Jave ascii art editor [was Re: Fwd: New Version Notification for draft-flanagan-plaintext-00.txt]

Elwyn Davies elwynd at folly.org.uk
Tue Jun 24 15:51:24 PDT 2014

On Tue, 2014-06-24 at 19:35 +0200, Thomas Clausen wrote:
> On Jun 24, 2014, at 18:33, Elwyn Davies <elwynd at folly.org.uk> wrote:

> Back to the question at hand, which I’ll just go ahead and paste back in (still quoting you, Elwyn): 
> > If I have understood correctly and we have to continue doing ASCII art
> > or add in many more words for such cases, I am not sure this is a gain.
> > 
> > Maybe the protocol field diagram is amenable to a specification language
> > that will generate the ASCII art or some SVG alternative according to
> > output rendering.
> > 
> > Message flow diagrams and architecture/structure block diagrams are more
> > difficult.
> > 
> > I am sure there must be tools out there that will do most of this
> > already.
> For the format defined in RFC5444 (a regexp derivative - and here’s a
> memory test, Elwyn, who was the GEN-ART reviewer for that document?)
> and used in a few protocols now, there’re actually several “picture
> generators” out there that take a regexp and produce ascii-art (and
> other stuff), so that bit is actually fairly doable.
> I’m afraid that I do not know of anything taking a textual/tabular
> description of a state machine or a block diagram, and draws legible
> ASCII-art - OmniGraffle already has a hard time drawing block diagrams
> in non-ASCII…so for that, I’ve resorted to JaVE or by-hand.

ECharts (http://echarts.org/) has a go at drawing state machine diagrams
from a textual description (I was more interested in its ability to
exercise the resulting state machine).  In practice the drawing wasn't
very good and it certainly wasn't ASCII art.

> I am thrilled, though, that xml2rfc inserts page numbers
> automatically, though ;)
> Thomas
> > /Elwyn
> > 
> >> 
> > 

More information about the rfc-interest mailing list