[Justfont] Editorial issues
Chris Lilley <chris@w3.org> Sun, 07 February 2016 15:35 UTC
Return-Path: <chris@w3.org>
X-Original-To: justfont@ietfa.amsl.com
Delivered-To: justfont@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49AB41B3C16 for <justfont@ietfa.amsl.com>; Sun, 7 Feb 2016 07:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0r49jPDW5hzi for <justfont@ietfa.amsl.com>; Sun, 7 Feb 2016 07:35:12 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [IPv6:2001:470:8b2d:804:52:12:128:0]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 448BE1B3C13 for <justfont@ietf.org>; Sun, 7 Feb 2016 07:35:11 -0800 (PST)
Received: from cim06-h01-31-32-14-119.dsl.sta.abo.bbox.fr ([31.32.14.119] helo=M6700) by raoul.w3.org with esmtpsa (TLS1.1:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <chris@w3.org>) id 1aSRMj-0001eK-4R for justfont@ietf.org; Sun, 07 Feb 2016 15:35:09 +0000
Date: Sun, 07 Feb 2016 16:35:04 +0100
From: Chris Lilley <chris@w3.org>
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <1841720038.20160207163504@w3.org>
To: justfont@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/justfont/PFliYk4tA4zXhvcvQtfmBlI13QE>
Subject: [Justfont] Editorial issues
X-BeenThere: justfont@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Font Top Level Media Type \(just font\) WG" <justfont.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/justfont>, <mailto:justfont-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/justfont/>
List-Post: <mailto:justfont@ietf.org>
List-Help: <mailto:justfont-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/justfont>, <mailto:justfont-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 15:35:14 -0000
Hello, The list of closed issues is at https://github.com/svgeesus/ietf-justfont/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed Any of these can be re-opened if there is further discussion, of course. Four were editorial: - Add CSS3 fonts reference #4 https://github.com/svgeesus/ietf-justfont/issues/4 The 'format' part of the @font-face src descriptor was used without a reference to the defining specification. I added the reference. - WOFF "published specification" #5 https://github.com/svgeesus/ietf-justfont/issues/5 The text said that, for WOFF 1.0 "This media type registration is extracted from the WOFF specification at W3C." Except it wasn't. The WOFF 1.0 spec had the old, application/font-woff registration. I changed this to say "This media type registration updates the the WOFF specification at W3C." (Once this ID becomes an RFC, the W3C WebFonts WG will errata WOFF 1.0 to point to it). - Drop "Primary Content Type" for "Top level Type" #8 https://github.com/svgeesus/ietf-justfont/issues/8 The phrase "Primary Content Type", copied from the model/* registration, is obsolete and should be changed for the correct term, "Top Level Type". I changed all occurrences. - IETF nits #9 https://github.com/svgeesus/ietf-justfont/issues/9 This issue was to remind me to fix nits at https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-ietf-justfont-toplevel-00.txt The issues were: ** The document seems to lack an IANA Considerations section. (See Section 2.2 of http://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. The issue was closed by adding explicit Normative and Informative references, correctly using the xref element, and adding a reference to RFC 2119. Two issues were not editorial but seemed clear-cut. Apologies if I closed them prematurely: - Magic number for SVG #3 https://github.com/svgeesus/ietf-justfont/issues/3 The specification talks about magic numbers for TrueType and CFFe outlines, so I opened an issue asking about a magic number for SVG outlines. Rod Sheeter commented on the GitHub issue with a quote from the OpenType spec which verified that the existing magic numbers were correct. In addition, SVG outlines alsways occur together with either TrueType or CFF outlines, not by themselves. Thus, there is no magic number for SVG as such. - OpenType shaping parameter #1 https://github.com/svgeesus/ietf-justfont/issues/1 This was an issue raised on draft-lilley but not resolved before this IETF WG was created. it was raised by Grzegorz Rolek on Twitter. he pointed out that the abbreviation "OTF" (OpenType Format) was being used both as a format specifier and also as a layout language specifier. The correct term for the latter is "OTL" (OpenType Layout). I corrected the draft to use OTF where the format was meant, and OTL where the layout was meant. -- Best regards, Chris Lilley Technical Director, W3C Interaction Domain
- [Justfont] Editorial issues Chris Lilley