Re: [TOOLS-DEVELOPMENT] CSS for RFCs SOW

That's essentially what we have here. I don't think, however, that
calling it a "Look and Feel for RFCs RFP" will get the right bidders in
the room.

-Heather

On 7/5/16 2:14 PM, HANSEN, TONY L wrote:
>
> This discussion makes me think that what we need is NOT a “CSS for
> RFCs” SOW, but instead a “Look&Feel for RFCs” SOW that covers both
> “CSS for HTML” and “PDF”.
>
>  
>
>                 Tony
>
>  
>
> *From: *TOOLS-DEVELOPMENT <tools-development-bounces@ietf.org> on
> behalf of Robert Sparks <rjsparks@nostrum.com>
> *Date: *Tuesday, July 5, 2016 at 4:07 PM
> *To: *"tools-development@ietf.org" <tools-development@ietf.org>
> *Subject: *Re: [TOOLS-DEVELOPMENT] CSS for RFCs SOW
>
>  
>
> 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.
>
>
>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development