[rfc-i] Fwd: New Version Notification for draft-flanagan-rfc-css-00.txt

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Tue Jun 30 09:29:07 PDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello all,

I've posted a new draft related to the format work that starts to define
the requirements for the RFC Editor's CSS for the HTML output. This is
an early draft, and details will be fleshed out in future drafts. The
goal here is to make sure all classes are listed, and to make a first
pass at which classes will result in a visual distinction in the document.

Comments welcome.
Heather


- -------- Forwarded Message --------
Subject:     New Version Notification for draft-flanagan-rfc-css-00.txt
Date:     Tue, 30 Jun 2015 09:23:11 -0700
From:     internet-drafts at ietf.org
To:     Heather Flanagan <rse at rfc-editor.org>, Heather Flanagan
<rse at rfc-editor.org>



A new version of I-D, draft-flanagan-rfc-css-00.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

Name:        draft-flanagan-rfc-css
Revision:    00
Title:        CSS Requirements for RFCs
Document date:    2015-06-30
Group:        Individual Submission
Pages:        13
URL:           
https://www.ietf.org/internet-drafts/draft-flanagan-rfc-css-00.txt
Status:         https://datatracker.ietf.org/doc/draft-flanagan-rfc-css/
Htmlized:       https://tools.ietf.org/html/draft-flanagan-rfc-css-00


Abstract:
   While individuals may choose their own Cascading Style Sheet for
   presenting HTML-formatted RFCs, the default offered by the RFC Editor
   must meet certain requirements.  This draft describes those
   requirements and is based on the classes defined in draft-hildebrand-
   html-rfc.

   Discussion of this draft takes place on the rfc-interest mailing list
   (rfc-interest at rfc-editor.org), which has its home page at
   https://www.rfc-editor.org/mailman/listinfo/rfc-interest.

                                                                                
 


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCAAGBQJVksPTAAoJEER/xjINbZoGJ04IAINKDGL88ZK6qiYcyVBQ3v4U
k24+KzMe7ymY1DPdjeGR1eg2v0WmE/4IiOQOftRy2XHLACIiMYW0YzTF5MmPiFh2
qnJe9n0MrVHhg3xMyTu98UNoH3LqHMgHRYZVw3f/E0No/zrBXyUtjEBT62thUhxA
tKgP0MTF0gON9i7E7cs2YwxfCtNs8JJe6iJibczackhbO3+qoeGDYr+Qz8NzTtBM
OUiB2Qcn1QU2Bd1pk58zgVbegNZzfCxqaK+m0u1blBsUpfENEZo/wXJP0EhK7+DV
l+ieIMhA+eCR0lm9q3xd08XzjC070HbkL2ZbyPNuVyGcXB5gUZmB8fpMkO0/8CM=
=GUlK
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150630/b9aaa2a2/attachment.html>


More information about the rfc-interest mailing list