Re: [apps-discuss] font/*

Eric Burger <eburger@standardstrack.com> Tue, 08 November 2011 14:20 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353D221F8CC9 for <apps-discuss@ietfa.amsl.com>; Tue, 8 Nov 2011 06:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.352
X-Spam-Level:
X-Spam-Status: No, score=-102.352 tagged_above=-999 required=5 tests=[AWL=-0.353, BAYES_00=-2.599, J_CHICKENPOX_83=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WTMvxvEsuR7X for <apps-discuss@ietfa.amsl.com>; Tue, 8 Nov 2011 06:20:12 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3F821F8CCB for <apps-discuss@ietf.org>; Tue, 8 Nov 2011 06:20:12 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=0LrUs+n4saj0gym/sVud+fFlRYQLCawqqQEaxOe0MBE4Ffu6V12LHWCIRFt8AOBPPjG6m5HjEAScvanG+Eb4BpbC86AWhVh1fbbeOF5+PbfY9c30u1OqYSd0mfxkGAGl;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:50468 helo=[192.168.15.184]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1RNmX4-0002Vd-UX for apps-discuss@ietf.org; Tue, 08 Nov 2011 06:20:11 -0800
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-27-1004908240; protocol="application/pkcs7-signature"; micalg=sha1
Date: Tue, 8 Nov 2011 09:20:08 -0500
In-Reply-To: <4EB8D0F4.9020907@it.aoyama.ac.jp>
To: "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>
References: <4EB86078.8070904@stpeter.im> <BDC0F178EEB88CC4B3D24020@PST.JCK.COM> <4EB8D0F4.9020907@it.aoyama.ac.jp>
Message-Id: <555BA718-A5FA-4111-9A8B-1DE99921CCE2@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [apps-discuss] font/*
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2011 14:20:13 -0000

Is the idea we would see something like

	font/Times

or one of 

	font/PostScript/Times
	font/TrueType/Times
	font/OpenType/Times
	font/METATYPE/Times

or one of

	font/Times/PostScript
	font/Times/TrueType
	font/Times/OpenType
	font/Times/METATYPE

One cannot just say it's font/* and assume it is an opaque container, as one could see battles over the latter examples.

On Nov 8, 2011, at 1:49 AM, Martin J. Dürst wrote:

> Hello John,
> 
> On 2011/11/08 8:32, John C Klensin wrote:
>> 
>> 
>> --On Monday, November 07, 2011 15:49 -0700 Peter Saint-Andre
>> <stpeter@stpeter.im>  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?
>> 
>> Well, I think that a top-level would be in order -- these are
>> really different from the existing types.  Things may have
>> changed, but my recollection from when I had some exposure to
>> them in the early 90s is that there are a bunch of font
>> definition languages out there.  Unless all but one has
>> atrophied or one could pick one to go with the top-level type,
>> there is going to be a messy problem in which one either needs
>> to have
>>   font/DefinitionLanguage fonttype=Foo
>> or another round of
>>   font/Foo+DefinitionLanguage
>> I'd hope we could avoid the latter, especially since some of
>> those languages and definitional methods don't scale over a very
>> broad range, s.t. one might actually need a tuple of Definition
>> Language, Typeface, Style, and applicable range of sizes.
>> 
>> Happy to try to help with this, but there better be some real
>> typographic experts involved.  We do not want to create a
>> top-level type only to find ourselves locked into one particular
>> kind of solution (even if it is open source rather than
>> vendor-specific).  I might still be able to carry on a useful
>> conversation with such an expert, but it has been a very long
>> time since I've had to do that, things have changed, and I've
>> forgotten a lot of what I once knew.
> 
> There is no need to overengineer this stuff. Like all other types, it's simply a top level type, and a subtype. A very rough approximation of what could end up in the subtype can be found here: http://en.wikipedia.org/wiki/Category:Font_formats.
> 
> If some kind of 'Definition Language' is used inside a font format, then that's just something under the hood. My understanding is that some popular formats such as OpenType essentially are mergers resulting from the "Definition Language" wars in the early 1990. Also, typeface, style, and applicable range of sizes shouldn't be necessary as part of the mime type because it's part of the content.
> 
> Some such parameters were proposed in http://tools.ietf.org/html/draft-singer-font-mime-00, and may still be necessary, but not as much as 7 years ago, when you apparently shot down the proposal (see http://www.ietf.org/mail-archive/web/ietf/current/msg33267.html). So if the font experts say they really need a parameter, we'll keep it, but we don't have to make thing more complicated than necessary in advance.
> 
> The only RFC that defined a new top-level type is RFC 2077 (http://tools.ietf.org/html/rfc2077). It's rather short, and I expect the font/ RFC to be even shorter unless it also includes some registrations for actual subtypes (I'd probably do it in two separate documents, one for the top-level type and another for some low hanging subtypes, but I'll leave the decision to whoever does the actual work.)
> 
> 
> Regards,   Martin.
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss