h5bp/server-configs

Font MIME type with the RFC 8081

LeoColomb opened this issue · 5 comments

LeoColomb commented

Hi @h5bp/server-configs folks!

Recent changes introduced by the RFC 8081 and registered at IANA about font media types should be applied to server configs, shouldn't it?

Current New
application/x-font-ttf font/ttf
application/font-otf or font/opentype font/otf
application/font-woff font/woff
application/font-woff2 font/woff2
application/font-cff or application/x-font-ttf (.ttc) font/collection
LeoColomb commented

Ping @alrra just in case ! 😇

ChrisMcKee commented

Woff/Woff2 are already in there as are TTF/OTF... sfnt is the basis of woff / otf / ot; are cff/sfnt currently in use anywhere (webfont wise)?

https://www.iana.org/assignments/media-types/application/font-sfnt
https://blog.typekit.com/2010/12/02/the-benefits-of-opentypecff-over-truetype/

LeoColomb commented

Woff/Woff2 are already in there as are TTF/OTF... sfnt is the basis of woff / otf / ot;

What do you mean?

ChrisMcKee commented

woff/2/ttf/otf mime types are already in the configs.
Are CFF/SFNT in use on the web at the moment?

LeoColomb commented

woff/2/ttf/otf mime types are already in the configs.

Yep, but my issue points out that there is an update regarding the media types of these file types.
This update is introduced by the RFC 8081 published on February 2017.

Are CFF/SFNT in use on the web at the moment?

font/sfnt is a general case for both font/otf and font/ttf, see https://www.iana.org/assignments/media-types/font/sfnt:

Note that "font/sfnt" is an abstract type from which the (widely
used in practice) "font/ttf" and "font/otf" types are conceptually
derived. Use of "font/sfnt" is likely to be rare in practice, and
might be confined to:

  • Uncommon combinations such as "font/sfnt; layout=sil" that do not have a shorter type

  • Cases where a new parameter value is registered

  • Test cases, experimentation, etc.