[apps-discuss] 答复: font/*

TianLinyi <tianlinyi@huawei.com> Sun, 13 November 2011 12:03 UTC

Return-Path: <tianlinyi@huawei.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 DC66C21F8B98 for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 04:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.749
X-Spam-Level: **
X-Spam-Status: No, score=2.749 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 djmlmLKKWR7j for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 04:03:21 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D44D721F8B90 for <apps-discuss@ietf.org>; Sun, 13 Nov 2011 04:03:20 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUL008TULHJNN@szxga05-in.huawei.com> for apps-discuss@ietf.org; Sun, 13 Nov 2011 20:03:19 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUL0020WLHIAT@szxga05-in.huawei.com> for apps-discuss@ietf.org; Sun, 13 Nov 2011 20:03:19 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEY53494; Sun, 13 Nov 2011 20:02:39 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 13 Nov 2011 20:02:38 +0800
Received: from SZXEML513-MBX.china.huawei.com ([169.254.8.59]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Sun, 13 Nov 2011 20:02:29 +0800
Date: Sun, 13 Nov 2011 12:02:27 +0000
From: TianLinyi <tianlinyi@huawei.com>
In-reply-to: <4EBF15DD.4050801@att.com>
X-Originating-IP: [172.24.2.41]
To: Tony Hansen <tony@att.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Message-id: <3615F3CCD55F054395A882F51C6E5FDA181FF7DB@szxeml513-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [apps-discuss] font/*
Thread-index: AQHMoS4cofDqxFROr0KXII3D5pJmlpWpddWAgAE/iUw=
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <4EB86078.8070904@stpeter.im> <BDC0F178EEB88CC4B3D24020@PST.JCK.COM> <4EB8D0F4.9020907@it.aoyama.ac.jp> <555BA718-A5FA-4111-9A8B-1DE99921CCE2@standardstrack.com> <60D34A5D-985C-4C97-A4FA-3CBF5CD31FCF@mnot.net> <4EB9D49C.5010100@it.aoyama.ac.jp> <4EBB2FEA.5060602@dcrocker.net> <4EBB50F4.7020501@it.aoyama.ac.jp> <4EBB54E0.9090005@dcrocker.net> <00bb01cc9f87$ff24b9a0$4001a8c0@gateway.2wire.net> <4EBBABC1.1010101@it.aoyama.ac.jp> <003201cca12e$1f35f860$4001a8c0@gateway.2wire.net> <4EBF15DD.4050801@att.com>
Subject: [apps-discuss] =?gb2312?b?tPC4tDogIGZvbnQvKg==?=
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: Sun, 13 Nov 2011 12:03:22 -0000

why not define something like this:
application/fontformat-arial

define a top level type may not be needed

_______________________________________
发件人: apps-discuss-bounces@ietf.org [apps-discuss-bounces@ietf.org] 代表 Tony Hansen [tony@att.com]
发送时间: 2011年11月13日 8:57
到: apps-discuss@ietf.org
主题: Re: [apps-discuss] font/*

On 11/12/2011 6:27 AM, t.petch wrote:
> ----- Original Message -----
> From: "Martin J. Dürst"<duerst@it.aoyama.ac.jp>
> To: "t.petch"<ietfc@btconnect.com>
> Cc:<dcrocker@bbiw.net>;<apps-discuss@ietf.org>
> Sent: Thursday, November 10, 2011 11:47 AM
>
>
>> On 2011/11/10 18:06, t.petch wrote:
>>> Dave
>>>
>>> My bibles say
>>>
>>> Type(face) Family; Courier, Futura, Century Schoolbook,  ..
>>> Typeface; one of the above with a defined
>>>    - Style: Roman, Italic
>>>    - Weight: Light, Semibold, Bold, ...
>>>    - Width: Ultracondensed, Condensed, Expanded, ...
>>> Type Font; one of the above with a defined Size
>>>    - eg 12-point
>> As I said before in a mail to Dave, the last point worked well for lead
>> type or bitmap fonts, but technology has moved beyond.
> Martin
>
> The concepts have not changed and remain useful, IMO, in any discussion
> on presentation.  What has changed is the implementation detail so when
> I download a new package to my PC, then it will apply to all Fonts, within
> a Typeface, as opposed to having a separate module for each Font.
> (Incidentally, my bibles all relate to laser printing ie to modern technology
> and have nothing to do with lead:-).
>
> But more significantly, as other posts have clarified for me, this thread
> is nothing to do with fonts but with type definition languages, so perhaps
> it should be 'type/*'.

I've seen several hints of wanting to do web Accept-style queries along
the line of

     Accept: font/arial, font/comicsans

What is it that is really desired?

While this sounds like it might be a nice capability, it really doesn't
agree with what media types are all about. The Arial font can be
described in many different font file formats.

Media types are more for describing things like:
     MMMM/datafork-truetype
     MMMM/intellifont
     MMMM/postscriptfont
     MMMM/truedocfont
     MMMM/truetype
     MMMM/webopenfont

(where MMMM is some prefix yet to be determined), within which you can
have a description of many different fonts, including Arial and ComicSans.

=======

*IF* we were to define a top-level media type, I do *not* think it
should be named "font", but instead should name it "fontformat" or
something like that. I think naming it "font" just leads people to have
false expectations.

=======

I notice that if "application" were used for font format file names,
some of the font format names would need to include the word "font" as
part of the name. For example, "application/postscript" can not be used
for the font format defined in the postscript standard. Instead, it
would have to be "application/postscriptfont". This *could* be taken an
argument for using "fontformat" as a top level type, as in
"fontformat/postscript". However, I don't find it a convincing argument
by itself.

     Tony Hansen

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss