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

["Heather Flanagan (RFC Series Editor)" <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/1/14 7:12 PM, Russ Housley wrote:
> I would not say  "It is unlikely that license-free or low-cost fonts
> exist to cover all these requirements.   "

OK.  Removed.

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

If you're curious, Martin Dürst has a quick write up on the problem(s) -
http://www.rfc-editor.org/pipermail/rfc-interest/2014-October/008044.html

> 
> Russ
>
>
> On Dec 1, 2014, at 7:07 AM, Heather Flanagan (RFC Series Editor)
> wrote:
>
>>
> 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.
>
>>
>> _______________________________________________ TOOLS-DEVELOPMENT
>> mailing list [e-mail]
>> <mailto:[e-mail]>
>> https://www.ietf.org/mailman/listinfo/tools-development
>

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

iQEcBAEBAgAGBQJUfbv9AAoJEER/xjINbZoGXusIAL0a2a7e4KxKFKXysRLVSiAl
Mo62r4sf2EQF2FfKspZUTt8dRaaa5ZMVYVQVK2QR0wdN3l4Zq6jJaQQKN+oE0kND
IIOKWDJxUXHxxV+D0GRj0ZJh1O/xFUZIWyXgkbb7rqIrNCKGuGcGTIgSg9Z+03Zg
n13tLaL/HmVtOIkQzA49cYixPKmnJFgtbwATO/ieO28rQ8E5hlvffciauqmbGTkD
a3Uf3pmiG+5H8V1KsMq5Yt5M74uhXQqG+3drEDMagEvJnKA5GgOJPdoTs52lUVw9
RFFyRDwPGUdGskWRq1m7CVW9wnmkYbiJo1kXCxSj8nS1TSODhQ0rB09hzsZTV6g=
=v0On
-----END PGP SIGNATURE-----