Re: [TOOLS-DEVELOPMENT] CSS for RFCs SOW

Looks good to me.

> On Jul 17, 2016, at 3:31 PM, Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org> wrote:
> 
> On 7/5/16 10:07 PM, Robert Sparks wrote:
>> 
>> 
>> 
>> On 7/5/16 2:56 PM, Heather Flanagan (RFC Series Editor) wrote:
>> 
>> <trim/>
>> 
>>> 
>>> > 
>>> >>> - it's unclear how designing the CSS has any impact on PDF,
>>> >>> unless we plan to produce the PDF from HTML (which I would
>>> >>> strongly support), in which case mentioning it here doesn't make
>>> >>> a lot of sense
>>> >> 
>>> >> The most recent update to the CSS for RFCs SOW is much more clear
>>> >> on this point.  I think the previous version was fuzzy.
>>> > 
>>> > I just looked and it still talks about PDF all over the place; it's
>>> > totally unclear from the SoW how CSS affects PDF.
>>> 
>>> 
>>> The HTML and PDF need to look very similar, and if the implementer(s) decide to create the PDF from the HTML using all the features described in the PDF draft, then there may well be implications for the CSS. I feel rather strongly that we need to leave the mentions of PDF in this doc. Whoever designs the CSS needs to understand how closely these things will be tied together. 
>> It's probably worth capturing the distinction I think Julian is really looking for.
>> 
>> The CSS designer needs to be aware that we want to create PDF that looks very similar to the way HTML renders.
>> That will constrain the choices the designer makes to those that won't make creating that PDF _hard_.
>> The CSS designer should also be aware that we could choose to render PDF from the HTML, and not make choices that would make that hard.
>> 
>> That captures the connection between the HTML and PDF for the purposes of this document completely I think.
> 
> Does this change in the Overview capture this, do you think?
> 
> This project will result in a CSS file that will reflect visually pleasing, accessible, and responsive design. The HTML follows a semantic design as described in <https://datatracker.ietf.org/doc/draft-iab-html-rfc/>; all display details must come from an embedded CSS. The PDF must also follow a semantic design, including proper PDF tags, as described in <https://datatracker.ietf.org/doc/draft-iab-rfc-use-of-pdf/>. The CSS will be embedded in the HTML; the CSS designer should avoid any feature that is not easily implemented in PDF. The CSS designer should be aware that we may choose to render PDF from the HTML, and so should avoid making any choices in the implementation of the CSS that would make that creating a visually similar PDF difficult.
> 
> 
> (last sentence added)
> -Heather 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

-- 
Joe Hildebrand