N1848

ISO/IEC JTC1/SC18/WG8

Document Processing and Relating Communication—

Document Description and Processing Languages

TITLE:	Disposition of comments accompanying results of voting on ISO/IEC CD 9541-4, Information technology -- Font Information Interchange -- Part 4: Application-specific extensions
SOURCE:	Barbara Beeton
PROJECT:
PROJECT EDITOR:
STATUS:	WG8 approved disposition
ACTION:	For processing with revised text of standard
DATE:	24 May 1996
DISTRIBUTION:	WG8 and Liaisons
REFER TO:	ISO/IEC JTC1/SC18 N5244, 1995-12-14, Summary of voting on Document SC 18 N5160, ISO/IEC CD 9541-4, Information technology -- Font Information Interchange -- Part 4: Application-specific extensions
REPLY TO:	Dr. James D. Mason (ISO/IEC JTC1/SC18/WG8 Convenor) Oak Ridge National Laboratory Information Management Services Bldg. 2506, M.S. 6302, P.O. Box 2008 Oak Ridge, TN 37831-6302 U.S.A. Telephone: +1 423 574-6973 Facsimile: +1 423 574-6983 Network: masonjd@ornl.gov http://www.ornl.gov/sgml/wg8/wg8home.htm ftp://ftp.ornl.gov/pub/sgml/wg8/

Disposition of comments accompanying results of voting on ISO/IEC CD 9541-4, Information technology -- Font Information Interchange -- Part 4: Application-specific extensions

Comments were submitted by two national bodies, Japan and the U.K. In addition, although the U.S. vote was not included, responses are given here to comments provided to the editor by the U.S. national body.

Comments from Japan

Scope, line 2 The description "font interchange" should be "font information interchange.
Not accepted. The first paragraph of the Scope clause is identical with the corresponding text in ISO/IEC 9541-2 and ISO/IEC 9541-3.
1. Scope, line 7 The description "font and glyph properties" should be "font properties"
Not accepted. The phrase "glyph properties" is clarified.
2. Normative references Add a reference which defines TeX standard referred to in the Annex A of this standard.
Accepted. Added in Annex A. This is not normative.
4. Properties, line 2 The description "within paragraphs" should be "within lines"
Accepted.
Properties, line 4 The word "letter" should be "glyph", since "letter" is not yet defined in any international standards.
Accepted. Changed to "alphabetic glyph".
4.1 Additional font resource properties The descriptions "font resource properties" should be "font resource description properties".
Accepted.
4.1.1 Application-specific descriptive property-list The description "descriptive property-list" should be "description property-list".
Accepted.
p. 3 NOTE 1 The "script property" should be explained more precisely.
Accepted
4.3 Additional glyph properties The description "glyph properties" should be "glyph metrics properties".
Not accepted. Most of the properties defined under this clause are not metric, but descriptive, e.g. MATHCLASS, BIGOPLIM, BIGOPTYPE, etc.
p. 14 The title "A compatability with installed based" should be "Annex A (Informative) Compatability with installed base".
Accepted.
4.1.6 and 4.3.6 They should be defined.
Accepted. Appropriate text will be present in the DIS.
Figure 1 The examples are inappropriate from mathematical point of view.
Accepted.

Comments from the U.K.

UK comments on ISO/IEC CD 9541-4 (Font Information Interchange -- Application-specific extensions)

Figure 1 Move the `Relative positions' text to the top of the figure.
Accepted in principle. However, the composition of this particular type of expression is quite different in text and in display, although the meaning is identical; the `Relative positions' illustrated are applicable only to the second (display) case; a `Relative positions' example applicable to the first (text) case will be provided.
Figure 2 For consistency with other figures, insert `Relative positions' text.
Accepted.
Clause 4.2.6 Do not allow figure 4 to break up the text of the formal definition.
Accepted.
Clause 5.1
1. Three data types are imported from ISO/IEC 9541-2, but are not used.
  Structured-Name is necessary to establish the use of structured names; cf. ISO/IEC 9541-2, A.1. The other two will be removed.
2. It is necessary to define in this clause the data types that are used, in the same form as in 6.1 and A.1 of ISO/IEC 9541-2.
  The data types defined in ISO/IEC 9541-4 are additive with respect to those defined in ISO/IEC 9541-2, Clause 6. Omission of data types not used in 9541-4 from lists such as Property-Value or Value would have the unfortunate result of omitting sequential ASN.1 codes, either changing the code values or leaving gaps in the sequence. In order to clarify the situation, the introductory text to this clause has been changed to point out the fact that the properties defined in 9541-4 are additive and an explicit reference to 9541-2 Clause 6 has been included.

Comments from the U.S.

Complete foreword, introduction and references.
Accepted.
In all figures, rules indicating vertical positioning have disappeared in copying; generate copy for DIS ballot using rules of sufficient thickness so that they do not disappear.
Accepted.
Supply text for clause 4.1.6, Culture.
Accepted.
Supply figures for properties that are not yet illustrated.
Accepted.
Supply text for clause 4.3.6, Attachment points.
Accepted.
In ASN.1 encoding, review IMPORTS for correctness and update if necessary. Also, review for need of EXPORT.
Accepted.
ASN.1 and SGML encodings are not consistent with clause 4.1.1, 4.2.1 and 4.3.1; check 9541-2 and, if necessary, change the encoding.
Accepted.
Change text of clause 5.2, SGML, to remove DOCTYPE and replace with English description explaining where to insert elements in SGML encoding clause of 9541-2.
Accepted.
In SGML encoding, ruleclr and sbspclr require element declarations; spelling of subwisup and subwsup needs to be brought into agreement.
Accepted.