On 6 jul 2009, at 8:53, Yaakov Stein wrote:
OK, here is what happens on my netbook using your method.
What I see :
0 1 2 3 4 5 6 7 8 9 0
1 2 3 4 5 6 7 8 9 0 1 2
3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-
+-+-+-+-+-+-+-+-+-+-+-+-+
Hm, it's not supposed to break lines between <pre> and </pre> even if
they don't fit on the screen...
Obviously ASCII art is created with screen / paper size assumptions
built in. I never claimed I was able to get around that. My claim was
that it was possible to create an HTML-ized form of the RFC format
that would both be valid HTML and could be turned back into the well-
known plain ASCII format by simply removing the HTML tags.
Due to the difficulties in making good graphics and the issue of
having a single RFC span multiple files in the case of HTML format
with graphics I think we should stick with ASCII art in the general
case even if we move to HTML as the archival format. But packet layout
diagrams can be made with HTML tables, which would make them a little
more flexible than ASCII art but on a really tiny screen those still
wouldn't display very well.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf