[rfc-i] "wysiwyg" requirement
tbray at textuality.com
Sat Nov 10 16:42:44 PST 2012
Except for, nroff is an outdated tool that has no notion of structural
integrity (or actually of structure at all), fosters the illusion that
66-line 80-column monospaced paginated text is anything but an accidental
artifact of long-obsolete display technology, and and whose use is rapidly
heading into the territory of “actively harmful”.
My problem is that I can’t help thinking of the IETF as (in part) a
publisher of high-value intellectual content, and that content deserves
better respect than is shown by the use of tools that were second-rate 30
On Sat, Nov 10, 2012 at 3:24 AM, Andrew G. Malis <agmalis at gmail.com> wrote:
> NroffEdit gives you two windows next to each other, one with the nroff
> and the other with the rendered output. You can edit in either window and
> the other window is automatically updated in real time to reflect the
> change. Both the .nroff and .txt are also saved to your disk
> That should satisfy your requirement.
> On Sat, Nov 10, 2012 at 6:09 AM, Julian Reschke <julian.reschke at gmx.de>
>> On 2012-11-10 03:29, Andrew G. Malis wrote:
>>> Two comments that were missed in the minutes:
>>> 1. Stefan was thanked for his work on NroffEdit.
>>> 2. If the revisable format changes from nroff, RFC authors will need
>>> WYSIWYG editing tools at least as easy to use as NroffEdit.
>> But then, a WYSIWYG editor is much simpler if all it needs to support is
>> our old format.
>> Furthermore, "what you see is what you get" also can mean "what you see
>> *all* you get". So what's important is that it's easy to edit the
>> structure, not to be able to preview the result in 72-characters-per-line
>> fixed-width font format.
>> Best regards, Julian
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rfc-interest