[rfc-i] draft-rfc-image-files-03

Julian Reschke julian.reschke at gmx.de
Tue Apr 10 01:43:31 PDT 2012


On 2012-04-09 20:11, Iljitsch van Beijnum wrote:
> On 9 Apr 2012, at 19:54 , Paul E. Jones wrote:
>
>> Not specific to this HTML example, but one thing we night want to consider
>> is whether we want to change the normative words from all uppercase to
>> italics (or bold) lowercase.  This document shows uppercase, because that is
>> the current agreed style driven by the use of ASCII.  HTML opens up an
>> opportunity to change that, if we want.
>
> That's the wrong question.
>
> The right question is: do we want to explicitly tag RFC 2119-relevant words so that they can be rendered appropriately using whatever output format/device that is used?
> ...

<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext.element.bcp14>

> That would be a good way to make the output a bit nicer and maybe reclaim the words "may" and "should" for normal use when not tagged, but doing this does impose a higher level of metadata round trip survival, as these words occur a lot throughout the text, unlike most other types of metadata.
>
> On Julian's HTML: I have no strong feelings either way, except that using text that runs the entire width of the browser window is rather suboptimal for pleasant/efficient reading. 10 - 12 words a line is best.
> ...

That's something people regularly disagree on. (see epic discussion 
thread on the related W3C mailing list)

In the end we probably need something that works for both audiences.

Best regards, Julian


More information about the rfc-interest mailing list