Skip to main content

Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration
draft-collins-pfr-00

The information below is for an old version of the document that is already published as an RFC.
Document Type This is an older version of an Internet-Draft that was ultimately published as an RFC.
Author John Collins
Last updated 2013-03-02 (Latest revision 2000-11-15)
Stream Legacy stream
Formats plain text htmlized pdfized bibtex
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3073 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-collins-pfr-00
A new Request for Comments is now available in online RFC libraries.

        RFC 3073

        Title:      Portable Font Resource (PFR) -
                    application/font-tdpfr MIME Sub-type Registration
        Author(s):  J. Collins
        Status:     Informational
        Date:       March 2001
        Mailbox:    jcollins@bitstream.com
        Pages:      6
        Characters: 9076
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-collins-pfr-00.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3073.txt

This document describes the registration of the Multipurpose Internet
Mail Extensions (MIME) sub-type application/font-tdpfr.  The encoding
is defined by the PFR Specification.
 
A Portable Font Resource (PFR) contains a set of glyph shapes.  Each
glyph shape is associated with a character code.  The PFR format is
designed to be both compact and platform-independent.  It is intended
to facilitate accurate rendering of fonts in all environments whether
or not they have the required fonts already installed.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.