Re: [apps-discuss] font/*

+1. From RFC 2046:

>     The "application" media type is to be used for discrete data which do
>     not fit in any of the other categories, and particularly for data to
>     be processed by some type of application program.  This is
>     information which must be processed by an application before it is
>     viewable or usable by a user.

Font files are processed by applications, and they are processed before 
the text with some font is visible to user.  That's not the case for new 
content type.

Mykyta Yevstifeyev

08.11.2011 16:15, Eric Burger wrote:
> Agreed.
>
> On Nov 8, 2011, at 3:27 AM, Graham Klyne wrote:
>
>> It's not clear to me what purpose would be served that cannot be handled perfectly adequately by application/*
>>
>> My understanding (or impression over the years) was that the top-level MIME type was a kind of high-level dispatch indicator to a device capable of rendering or otherwise presenting the broad kind of content, with application/* serving for types that needed further processing before they might meaningfully be considered for presentation
>>
>> If I receive a font/* file, what might I do with it that is different from any other application/* type of file?
>>
>> #g
>> --
>>
>>
>> On 07/11/2011 22:49, Peter Saint-Andre wrote:
>>> In talking with folks at the W3C meeting last week, I heard yet again of
>>> interest in defining a Content Type for fonts. Would anyone active in
>>> the IETF Applications Area want to work on such a spec? And do folks
>>> here think a new top-level content type is needed for fonts?
>>>
>>> Peter
>>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss