Re: [TOOLS-DEVELOPMENT] DRAFT: RFI for fonts

I would not say  "It is unlikely that license-free or low-cost fonts exist to cover all these requirements.   "

It would be great is someone could tell us how to meet these needs.

Russ

On Dec 1, 2014, at 7:07 AM, Heather Flanagan (RFC Series Editor) wrote:

> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello all,
> 
> I'm drafting an RFI to collect information on fonts.  Below is my first cut.  Questions for this group: what's missing?  Should I include any information on things I already know about (in particular, Google's Noto font library)?
> 
> I don't know if this will turn into an RFP or something else; that's why I'm doing an RFI.
> 
> - -----
> 
> Embedded Fonts for the PDF Publication Format for RFCs
> 
> Request for Information
> 
>  
> 
> Description:
> 
> In 2013, the RFC Series Editor announced to the IETF community the intent to change the format for RFCs from a single, plain-text, ASCII-only format to a format based on a canonical XML file with multiple publication formats.  One of those publication formats will be PDF/A-3 (see <draft-hansen-rfc-use-of-pdf).
> 
>  
> 
> One of the requirements for the PDF/A-3 format is that the font information for any and all fonts used for that document be embedded within the file.  The purpose here is to make the file as self-contained and stable as possible.    Requirements for the fonts themselves include:
> 
>  
> 
> ·      Serif and sans-serif fonts should be available (to meet the requirement in <draft-hansen-rfc-use-of-pdf> for main text and headings).
> 
> ·      A fixed-width font must be available for code, BNF, and any other text that requires such a font as an aid in insuring alignment.     
> 
> ·      Wide support for Unicode (which may require multiple fonts) is necessary to support the change that allows non-ASCII characters in RFCs, such as person names in native languages.
> 
> ·      Liberal or low-cost license terms.
> 
>  
> 
>  
> 
> It is unlikely that license-free or low-cost fonts exist to cover all these requirements.   This RFI is seeking information on what is available, where gaps exist such that a font might need to be acquired with a for-fee license, and where a font might need to be designed.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iQEcBAEBAgAGBQJUfFoEAAoJEER/xjINbZoGFBkIAKecMpEEWUdPPnmwkn6VIjVD
> 7y5Xk1LZZ0QZGh6YLTA+gG+5O6/zQXK7KkuxM4te3mhepzSoA+vUpQSSG+p7yk0u
> OYINqNWMpdVp3D8HLB+oBGCHZAlMRrkUyKT4RWW97JItaKHT96k6npOqBG5kBZUe
> FvlaD9RnLkDVD44fF6jHEX1hbrWdq4CBj7f4e2eij6tngC45Q/0MvGgXFtfU8e5k
> Sv7orqqlcLzW+jr6dKQwH1gnwKsATpA76VXfVdsgy4/D6TS69GBD2ez8NI335Jac
> m2D8rv/XLrxEMyQGeVcfiuAFLqHcP4w3Tgmn6zVna6CPa3o1OG1O0YnglRZW9Lk=
> =pf1v
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development