Standardization Activities on Additional Font Properties for Multilingual Document Interchange

by Yushi Komachi (Panasonic/MGCS, Japan)

    komachi@y-adagio.com

as a Member of Committee on Multilingual IT, CICC (Center of the International Cooperation for Computerization)

Table of Contents

1. Introduction

CICC (Center of the International Cooperation for Computerization) in Japan established working groups (WGs)

for drafting international standards required for interchanging multilingual documents, in particular, East-Asian multilingual documents. The multilingual documents means complicated documents which include multiple languages within a line, a paragraph, a clause or a page.

The Font WG started its works by the research of user requirements for extension to the existing font standard

from the East-Asian multilingual documents' point of view.

The 1st international discussion1) on this font topic was carried out in MLIT-3 (3rd International Symposium on Standardization of Multilingual Information Technology), in Hanoi, Vietnam, Oct. 6-7, 1998. We recognized the strong user requirements for interchanging multilingual documents particularly in web environments.

Under the recognition of the user requirements, Japanese expert proposed for ISO/IEC JTC1/SC34 to start a discussion of amendment 3 to ISO/IEC 9541-1.

2. Activities in ISO/IEC JTC1/SC34

2.1 Nov. 98 Meeting, Chicago

2.1.1 from SC34 N0017: Status report on legacy project

"4. New Amendment to 9541-1"

The Japanese font experts (in CICC: Center of the International Cooperation for Computerization and SC34/Japan) recognized that the existing ISO/IEC 9541 and its amendments cannot enough satisfy the user requirements, in particular, for the application of East Asian multilingual document interchange, where several languages are included within a document, page or a paragraph.

They hold a conference, MLIT (International Symposium on Standardization of Multilingual Information Technology) in Hanoi, Vietnam, and discussed this topic. Most Asian countries, e.g., China, Laos, Malaysia, Mongolia, Myanmar, Nepal, Philippines, Srilanka, Thailand, etc. dispatched their experts of document processing to the conference and confirmed the user requirements for multilingual document interchange and requirements for an extension to the ISO/IEC 9541.

2.1.2 from SC34 N0023: Resolutions of the ISO/IEC JTC1/SC34 Meeting, Chicago

"Resolution 4: SC 34 Project Subdivision"

SC 34 approves the following subdivision of Project 34.27.01:

Project Number Title Project Editor
34.27.01.03 ISO/IEC 9541-1:1991, Amendment 3 - Information Technology - Font Information Interchange - Part 1: Architecture - Amendment 3: Multilingual extensions to font resource architecture Y. Komachi

Rationale: Documents interchanged in the internet environment are often required to be a multilingual mixture, i.e., described using multiple languages within a paragraph, a page or a document. Those multilingual documents should be rendered and represented according to appropriate multilingual formatting requirements. The existing standard ISO/IEC 9541 and its current Amendment can support multilingual font treatments. However, the properties defined in the standards are still insufficient to fully support multilingual mixtures for multilingual formatting.

SC 34 instructs its Secretariat to forward this project subdivision to JTC 1 for endorsement.

2.2 April. 99 Meeting, Granada

2.2.1 from SC34 N0059: Report of SC34/WG2

"3. AM3 to ISO/IEC 9541-1: Multilingual extensions to font resource architecture" [Project JTC1.34.27.01.03]

According to the resolution 4 (SC34 N0023) of the Chicago meeting, project editor created a working draft of AM3 to ISO/IEC 9541. SC34/WG2 will review and revise it in the Granada meeting to create a PDAM text for PDAM procedure.

"4. AM1 to ISO/IEC 9541-2: Support for font technology advances" [Project JTC1.34.27.02.01]

Project editor created a working draft of AM1 to ISO/IEC 9541-2, which includes the interchange format for new font properties defined in AM2 and AM3 to ISO/IEC 9541-1. SC34/WG2 will review and revise it in the Granada meeting to create a PDAM text for PDAM procedure.

2.2.2 from SC34 N0062: Resolutions of the ISO/IEC JTC1/SC34 Meeting, Granada

"Resolution 4: SC 34 Texts for Ballot"

JTC 1/SC 34 approves the following texts for PDAM/FPDAM/CD/FCD registration and ballot:

ISO/IEC 9541-1/PDAM 3
(SC34 N0071)		 Information Technology - Font Information Interchange - Part 1: Architecture - Amendment 3: Multilingual Extensions to font resource architecture
ISO/IEC 9541-2/PDAM 1
(SC34 N0072)		 Information Technology - Font Information Interchange - Part 2: Interchange Format - Amendment 1: Support for Font Technology Advances

2.3 Voting for the PDAMs

The SC34 Secretariat circulated the PDAM texts for requesting votes by Aug. 18, 1999 as shown below:

Date: Tue, 18 May 1999 13:43:24 -0400
From: Marisa Topping
To: JTC 1/SC 34 Distribution List

The following documents are now available from the JTC 1/SC 34 Web Site at http://www.jtc1.org 

 
SubCommittee Name.:  SC34
Document Number...:  71
Backward pointer..:
Document Type.....:  Text for PDAM ballot or comment
Date Assigned.....:  1999-05-18
Document Title....:  ISO/IEC 9541-1:1991/PDAM 3, Information Technology
                     - Font Information Interchange - Part 1:
                     Architecture - Amendment 3:  Multilingual
                     extensions to font resource architecture
Due Date..........:  1999-08-18
Pages.............:   11
Disk Serial No....:
Source............:  Y. Komachi, Project Editor
Project Number....:  1.34.27.01.03
Status............:  In accordance with Resolution 4 of the 19-23 April
                     1999 JTC 1/SC 34 Meeting, this text is circulated
                     for a three-month PDAM ballot.  Please submit all
                     votes to the SC 34 Secretariat by 18 August 1999.
Action Identifier.:  LB
Medium............:  E


SubCommittee Name.:  SC34
Document Number...:  72
Backward pointer..:
Document Type.....:  Text for PDAM ballot or comment
Date Assigned.....:  1999-05-18
Document Title....:  ISO/IEC 9541-2:1991/PDAM 1, Information Technology
                     - Font Information Interchange - Part 2:
                     Interchange Format - Amendment 1:  Support for
                     font technology advances
Due Date..........:  1999-08-18
Pages.............:    6
Disk Serial No....:
Source............:  Y. Komachi, Project Editor
Project Number....:  1.34.27.02.01
Status............:  In accordance with Resolution 4 of the 19-23 April
                     1999 JTC 1/SC 34 Meeting, this text is circulated
                     for a three-month PDAM ballot.  Please submit all
                     votes to the SC 34 Secretariat by 18 August 1999.
Action Identifier.:  LB
Medium............:  E

Those PDAMs were approved (see Appendix 3) and DAM texts and procedures will be discussed in the next SC34 meeting to be held in Philadelphia, Nov. 1999.

3. Discussion in an East Asian Experts Group

For more discussions on the topic of additional font properties for multilingual document interchange, East Asian font experts met formally or informally.

3.1 12th CJK-DOCP Meeting, 1999-01-21/22, Taipei

from CJK-DOCP/99-18: Resolutions of the 12th CJK DOCP Meeting

"Resolution 4. Amendment 3 to ISO/IEC 9541-1"

CJK DOCP appreciates CJK-DOCP/99-06 as a working draft of Amendment 3 to ISO/IEC 9541-1 and instructs Mr. Y. Okui to create a revised text reflecting the discussions in this meeting before the submission to ISO/IEC JTC1/SC34/WG2.

3.2 CICC Ad-Hoc, 1999-03-05, Tokyo

On 5th March 1999, the font experts in CICC and attendees of the CICC seminar from several East-Asian countries met and discussed the interlinear formatting and objects in their documents.

Aftrer Mr. Okui's brief explanation about the concept of interlinear object, the attendees showed their typical interlinear objects or something they thought might be seen as interlinear objects.

After the discussion, some attendees sent by mail their sample documents which include intelinear formatting or interlinear objects.

3.3 13th CJK-DOCP Meeting, 1999-07-19/20, Moscow

from CJK-DOCP/99-47: Resolutions/Conclusion of the 13th CJK DOCP Meeting

"Resolution 3. Amendment 3 to ISO/IEC 9541-1"

CJK DOCP appreciates CJK-DOCP/99-35 as a PDAM3 to ISO/IEC 9541-1 and instructs Dr. Y. Komachi to create a DAM3 text reflecting the discussions in this meeting.

"Resolution 4. Amendment 1 to ISO/IEC 9541-2"

CJK DOCP appreciates CJK-DOCP/99-36 as a PDAM1 to ISO/IEC 9541-2 and instructs Dr. Y. Komachi to create a DAM1 text reflecting the discussions in this meeting.

4. Future Plans

ISO/IEC JTC1/SC34/WG2 has the following plan (SC34 N0076) for the AM3 to ISO/IEC 9541-1 and AM1 to ISO/IEC 9541-2: 

  Committee and WG                     Target & Actual Dates
  Project #                            NP      PDAM     DAM     AM
  ISO Designation
  Document N #
  Title
  Project Editor

  SC 34 / WG 02                        0.00    99.04   99.11  00.05
  27.01.03.00.00                       0.00    99.04    0.00   0.00
  ISO/IEC 9541-1 : 1991/AM 3
  Information Technology - Font
  Information Interchange - Part
  1:  Architecture - Amendment
  3:  Multilingual extensions to
  font resource architecture
  Dr. Yushi Komachi
  
  SC 34 / WG 02                        0.00    99.04   99.11  00.05
  27.02.01.00.00                       0.00    99.04    0.00   0.00
  ISO/IEC 9541-2 : 1991/AM 1
  Information Technology - Font
  Information Interchange - Part
  2:  Interchange Format -
  Amendment 1:  Support for
  font technology advances
  Dr. Yushi Komachi

5. Conclusion

Proposals and comments on the font technology, in particular, regarding country specific font properties, are welcomed and appreciated. They will soon be included in new texts to be discussed in ISO/IEC JTC1/SC34.

The font standards including the amendments will contribute the interchange of multilingual document. For the next step, we should discuss the formatting specification of those multilingual document in order to make it possible to interchange the documents preserving presentation styles. Such activities has already taken place, for example, in W3C (World Wide Web Consortium)2) and JIS committee3) and 4) but they are insufficient for interchanging the East-Asian multilingual documents.

Acknowledgment

The author would like to express their thanks to the members of Fonts WG, Committee on Multilingual IT, CICC for valuable discussions.

References

1) Y. Komachi, Additional Font Properties Required for Multilingual Document Interchange, MLIT-3, 1998-10.

2) Extensible Stylesheet Language (XSL) Specification, W3C, 1999-04.

3) Y. Komachi, DSSSL Application for a JIS Publishing System, 5th ITSIG/TSG, 1998-06.

4) JIS/TR X 0010, DSSSL Library for Japanese Composition, 1999-10.

Appendix 1: PDAM3 to ISO/IEC 9541-1

ISO/IEC JTC 1/SC34 N0071

ISO/IEC JTC 1/SC34

Information Technology --
Document Description and Processing Languages

TITLE: PDAM3 to ISO/IEC 9541-1: Multilingual extensions to font resource architecture
SOURCE: SC34/WG2
PROJECT: JTC1.34.27.01.03
PROJECT EDITOR: Y. Komachi
STATUS: PDAM text
ACTION: For ballot
DATE: 1999-04-19
DISTRIBUTION: SC34 and Liaisons
REFER TO:
REPLY TO: Dr. James David Mason
(ISO/IEC JTC1/SC34 Chaiman)
Lockheed Martin Energy Systems
Information Management Services
1060 Commerce Park, M.S. 6480
Oak Ridge, TN 37831-6480 U.S.A.
Telephone: +1 423 574-6973
Facsimile: +1 423 574-0004
Network: masonjd@ornl.gov
http://www.ornl.gov/sgml/wg4/
ftp://ftp.ornl.gov/pub/sgml/wg4/

PDAM3 to ISO/IEC 9541-1: Multilingual extensions to font resource architecture

Introduction

ISO/IEC 9541-1 and its amendment specify Ruby and Generalized Ken-dot. Although these specifications helps users and application developers implement their rendering system which can support the processing for these two specific objects, it is insufficient for the support for other objects which is positioned between lines or characters (which are called interlinear/intercharacter objects).

This amendment specifies additional properties for the interlinear/intercharacter object for multilingual use. By using this object, you can describe any object which is positioned between lines or characters. Actual objects are derived from this generic object as shown in Annex C for example.

Clause 3

Add the following definitions:

3.31 interlinear object: Objects between lines or objects inserted between lines.

3.32 intercharacter object: Objects between characters in the writing direction.

3.33 parent object: Object with which the interlinear/intercharacter object is associated. This term is used when referring to relation between interlinear/intercharacter object and the object with which that interlinear/intercharacter object is associated.

3.34 child object: Interlinear/intercharacter object. This term is used when referring to relation between interlinear/intercharacter object and the object with which that interlinear/intercharacter object is associated.

Clause 8

Add the following properties:

8.10 Interlinear/intercharacter Object Properties (ILCOBJ)

ILCOBJ is a property-list consisting of property-lists that specify type, font size, typeface, rotation, position in writing direction, formatting information in writing direction, and position in line progression direction of a interlinear/intercharacter object.

Note that these are primitive properties to locate interlinear/intercharacter object. There may be some GUI or convention for specification which can produce these properties.

ILC-property ::= ILC-name, ILC-value-property-list
ILC-name ::= STRUCTURED-NAME
ILC-value-property-list ::= (ILC-type-property|ILC-font-size-property|
ILC-typeface-property|ILC-rotation-property|
ILC-writing-direction-offset-property| ILC-formatting-type-property|
ILC-line-progression-direction-offset-property)+

ILC-type-property ::= ILC-type-name, ILC-type-value
   -- type of Interlinear/intercharacter objects
ILC-type-name ::= STRUCTURED-NAME
ILC-type-value ::= STRUCTURED-NAME

ILC-font-size-property ::= ILC-font-size-name, ILC-font-size-value-type,
ILC-font-size-value
   -- Property for font size
ILC-font-size-name ::= STRUCTURED-NAME
ILC-font-size-value-type ::= "ABS" | "RELATIVE"
ILC-font-size-value ::= REL-RATIONAL 

ILC-typeface-property ::= ILC-typeface-name, ILC-typeface-value
   -- Property for typeface
ILC-typeface-name ::= STRUCTURED-NAME
ILC-typeface-value ::= STRUCTURED-NAME

ILC-rotation-property ::= ILC-rotation-name, ILC-rotation-value
   -- Property for rotation
ILC-rotation-name ::= REL-RATIONAL
ILC-rotation-value ::= 0|90|180|270

ILC-writing-direction-offset-property ::= ILC-writing-direction-offset-name, 
ILC-writing-direction-offset-value, ILC-writing-direction-offset-value
   -- Property for position in writing direction 
ILC-writing-direction-offset-name ::= STRUCTURED-NAME
ILC-writing-direction-offset-value-type ::= "ABS" | "RELATIVE"
ILC-writing-direction-offset-value ::= REL-RATIONAL

ILC-formatting-type-property ::= 
                     ILC-formatting-type-name, ILC-formatting-type-value
   -- Property for formatting information in writing direction
ILC-formatting-type-name ::= STRUCTURED-NAME
ILC-formatting-type-value ::= "HEAD"|"CENTER"|"TAIL"|"JUSTIFICATION"

ILC-line-progression-direction-offset-property ::= 
ILC-line-progression-direction-offset-name,
ILC-line-progression-direction-offset-value,
ILC-line-progression-direction-offset-value-type
   -- Property for position in line progression direction 
ILC-line-progression-direction-offset-name ::= STRUCTURED-NAME
ILC-line-progression-direction-offset-value-type ::= "ABS" | "RELATIVE"
ILC-line-progression-direction-offset-value ::= REL-RATIONAL

NOTE 1 You have to specify the following items for recognition of interlinear/intercharacter object other than properties described here.

This document doesn't provide any particular way to specify these items above. For example, you may use customized SGML/XML tags to do that.

NOTE 2 You can associate multiple interlinear/intercharacter objects with the same character(s).

NOTE 3 ILC-type-property (type) specifies the type of a interlinear/intercharacter object.

NOTE 4 ILC-font-size-property (font size) specifies an absolute or relative value to font size of character(s) of the parent object with which the interlinear/intercharacter object is associated.

NOTE 5 ILC-typeface-property (typeface name) specifies typeface name.

NOTE 6 ILC-rotation-property (rotation) specifies an angle measured counterclockwise from the parent object's writing direction to the child object's writing direction. Probably interlinear objects have 0 degree for this property and intercharacter objects have 270 degree (when the main text is horizontally flowed) or 90 degree (when the main text is vertically flowed).

NOTE 7 ILC-writing-direction-offset-property (offset in writing direction) specifies an absolute or relative value to font size of character(s) with which the interlinear object is associated.

This value is the offset between the positioning point of child object and parent object. The writing direction is the one of the parent object, not the one of child object. That means this value is measured from the viewpoint of parent object's coordinate system.

NOTE 8 ILC-formatting-type-property (formatting type information in writing direction) specifies the formatting information regarding the alignment in writing direction. When this property is specified, the property for position in writing direction will be ignored even if there is one.

NOTE 9 ILC-line-progression-direction-offset-property (offset in line progression direction) specifies an absolute or relative value to font size of character(s) with which the interlinear object is associated.

This value is the offset between the baseline of character(s) with which interlinear object is associated and the baseline of interlinear object. The line progression direction is the one of the parent object, not the one of child object. That means this value is measured from the viewpoint of parent object's coordinate system.

Figure1. Concept of offsets - Writing direction of the parent object is left-to-right, rotation is 0 degree

Figure2. Concept of offsets - Writing direction of the parent object is left-to-right, rotation is 270 degree

Figure3. Concept of offsets - Writing direction of the parent object is top-to-bottom, rotation is 0 degree

Annexes

Add the following annexes:

Annex C. Examples of the use of generic interlinear object model (Informative)

Properties for interlinear/intercharacter objects are selected to represent particular objects. The following are the examples to show you which properties are selected and used to particular objects. In some cases, specific values are assigned to a property. In other cases, values are restricted to some values.

C.1 Ruby

ILC-type-value: "Ruby"

The name "Ruby" is just an example in this document. You can use any name.

ILC-font-size-value-type: "ABS" or "RELATIVE"
ILC-font-size-value: any size
ILC-typeface-value: any typeface name
ILC-rotation-value: 0
ILC-writing-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-writing-direction-offset-value: any size
ILC-formatting-type-value: "HEAD" or "CENTER" or "JUSTIFICATION"
ILC-line-progression-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-line-progression-direction-offset-value: any size

C.2 Generalized Ken-dot

ILC-type-value: "Generalized-Ken-dot"

The name "Ken-dot" is just an example in this document. You can use any name.

ILC-font-size-value: any size
ILC-typeface-value: any typeface name
ILC-rotation-value: 0
ILC-formatting-type-value: "HEAD" or "CENTER"
ILC-line-progression-direction-offset-value: any size

C.3 Return Mark

ILC-type-value: "Return-Mark"

The name "Return-Mark" is just an example in this document. You can use any name.

ILC-font-size-value: any size
ILC-typeface-value: any typeface name
ILC-rotation-value: 0
ILC-writing-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-writing-direction-offset-value: any size
ILC-line-progression-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-line-progression-direction-offset-value: any size

C.4 Added Characters

ILC-type-value: "Added-Characters"

The name "Added-Characters" is just an example in this document. You can use any name.

ILC-font-size-value: any size

ILC-typeface-value: any typeface name
ILC-rotation-value: 0
ILC-writing-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-writing-direction-offset-value: any size
ILC-line-progression-direction-offset-value-type: "ABS" or "RELATIVE"
ILC-line-progression-direction-offset-value: any size

Annex D. Samples of Formatting Pattern of interlinear/intercharacter objects (Informative)

D.1 Ruby

The followings are samples of formatting pattern of interlinear/intercharacter objects.

Figure 4. Formatting information in writing direction is "HEAD"

FIgure 5. Formatting information in writing direction is "CENTER"

Figure 6. Formatting information in writing direction is "JUSTIFICATION"

FIgure 7. Position in writing direction is specified

D.2 Generalized Ken-dot

Formatting type in writing direction is "HEAD"

{short description of image} {short description of image}

Figure 8. Formatting information in writing direction is "CENTER"

D.3 Return Mark & Added Characters

{short description of image}

{short description of image} {short description of image}

Figure 9. Pattern of return mark

{short description of image}

{short description of image}

Figure 10. Pattern of added characters

Appendix 2: PDAM1 to ISO/IEC 9541-2

ISO/IEC JTC 1/SC34 N0072

ISO/IEC JTC 1/SC34

Information Technology --
Document Description and Processing Languages

TITLE: PDAM1 to ISO/IEC 9541-2: Support for font technology advances
SOURCE: SC34/WG2
PROJECT: JTC1.34.27.02.01
PROJECT EDITOR: Y. Komachi
STATUS: PDAM text
ACTION: For information
DATE: 20 April 1999
DISTRIBUTION: SC34 and Liaisons
REFER TO: SC34 N0059
REPLY TO: Dr. James David Mason
(ISO/IEC JTC1/SC34 Chaiman)
Lockheed Martin Energy Systems
Information Management Services
1060 Commerce Park, M.S. 6480
Oak Ridge, TN 37831-6480 U.S.A.
Telephone: +1 423 574-6973
Facsimile: +1 423 574-0004
Network: masonjd@ornl.gov
http://www.ornl.gov/sgml/wg4/
ftp://ftp.ornl.gov/pub/sgml/wg4/

PDAM1 to ISO/IEC 9541-2: Support for font technology advances

1. SGML DTD for 9541-1 AM2

Add the following SGML DTD at the end of clause 6.2 

<!-- DTD for 8.9.1 Vertical Units and Horizontal Units -->

<!ELEMENT  verticalunit-property   (verticalunit-name, 
  verticalunit-value)  >
<!ELEMENT  verticalunit-name      (glbname)  -- STRUCTURED NAME -- >
<!ELEMENT  verticalunit-value      (card)      -- CARDINAL -- >
<!ELEMENT  horizontalunit-property (horizontalunit-name, 
  horizontalunit-value)  >
<!ELEMENT  horizontalunit-name   (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  horizontalunit-value   (card)    -- CARDINAL -- >

<!-- DTD for 8.9.2 Fill Ratio -->

<!ELEMENT  fillratio-property   (fillratio-name, 
  fillratio-value-property-list)  >
<!ELEMENT  fillratio-name      (glbname) -- STRUCTURED NAME --  >
<!ELEMENT  fillratio-value-property-list   (blackness+) >
<!ELEMENT  blackness (reference-glyph, fillratio-value)  >
<!ELEMENT  reference-glyph   (msg) -- MESSAGE -- >
<!ELEMENT  fillratio-value     (ratl) -- RATIONAL -- >

<!-- DTD for 8.9.3 Design Areas -->

<!ELEMENT  designareas-property   (designareas-name, 
  designareas-value-property-list)  >
<!ELEMENT  designareas-name      (glbname) -- STRUCTURED NAME --  >
<!ELEMENT  designareas-value-property-list   
 (designarea-property|plist)+ >
<!ELEMENT  designarea-property   (designarea-name, 
  designarea-value-property-list)  >
<!ELEMENT  designarea-name      (glbname) -- STRUCTURED NAME --  >
<!ELEMENT designarea-value-property-list   (letter-face+) >
<!ELEMENT letter-face    (dsnarea-glyphset-name, dsnarea-height, 
  dsnarea-width) >
<!ELEMENT  dsnarea-glyphset-name   (msg) -- MESSAGE -- >
<!ELEMENT  dsnarea-height     (ralr) -- REL RATIONAL -- >
<!ELEMENT  dsnarea-width      (ralr) -- REL RATIONAL -- >

<!-- DTD for 8.9.4 Average ESC -->

<!ELEMENT  averageesc-property   (averageesc-name, 
  averageesc-value-property-list)  >
<!ELEMENT  averageesc-name      (glbname) -- STRUCTURED NAME --  >
<!ELEMENT  averageesc-value-property-list   (averagelen-property|plist)+
  >

<!ELEMENT  averagelen-property   (averagelen-name, 
  averagelen-value-property-list)  >
<!ELEMENT  averagelen-name      (glbname) -- STRUCTURED NAME --  >
<!ELEMENT averagelen-value-property-list   (average-length+) >
<!ELEMENT average-length   (averlen-glyphset-name, avrlen-height, 
  avrlen-width) >
<!ELEMENT  averlen-glyphset-name   (msg) -- MESSAGE -- >
<!ELEMENT  averlen-height     (ralr) -- REL RATIONAL -- >
<!ELEMENT  averlen-width      (ralr) -- REL RATIONAL -- >

<!-- DTD for 8.9.5 Generalized Kendot -->

<!ELEMENT  genkendot-property   (genkendot-name, 
  genkendot-value-property-list)  >
<!ELEMENT  genkendot-value-property-list  
 (genkendot-offsetx-property|genkendot-offsety-property|genkendot-thick-
  property|genkendot-shape-property)+ >
<!ELEMENT  genkendot-offsetx-property  (genkendot-offsetx-name, 
  genkendot-offsetx-value) >
<!ELEMENT  genkendot-offsetx-name      (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  genkendot-offsetx-value     (ralr)    -- REL RATIONAL -- >
<!ELEMENT  genkendot-offsety-property  (genkendot-offsety-name, 
  genkendot-offsety-value) >
<!ELEMENT  genkendot-offsety-name      (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  genkendot-offsety-value     (ralr)    -- REL RATIONAL -- >
<!ELEMENT  genkendot-thick-property  (genkendot-thick-name, =
  genkendot-thick-value) >
<!ELEMENT  genkendot-thick-name        (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  genkendot-thick-value       (ralr)    -- REL RATIONAL -- >
<!ELEMENT  genkendot-shape-property  (genkendot-shape-name, =
  genkendot-shape-value) >
<!ELEMENT  genkendot-shape-name        (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  genkendot-shape-value       (glbname) -- STRUCTURED NAME -- >

2. SGML DTD for 9541-1 AM3

Add the following SGML DTD at the end of clause 6.2 

<!-- DTD for 8.10 Interlinear/intercharacter Object Properties -->

<!ELEMENT  verticalunit-property   (verticalunit-name, 
  verticalunit-value)  >
<!ELEMENT  verticalunit-name      (glbname)  -- STRUCTURED NAME -- >
<!ELEMENT  verticalunit-value      (card)      -- CARDINAL -- >
<!ELEMENT  horizontalunit-property (horizontalunit-name, 
  horizontalunit-value)  >
<!ELEMENT  horizontalunit-name   (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  horizontalunit-value   (card)    -- CARDINAL -- >

<!ELEMENT  ILC-property (ILC-name, ILC-value-property-list) >
<!ELEMENT  ILC-name     (glbname)  -- STRUCTURED NAME -- >
<!ELEMENT  ILC-value-property-list 
 (ILC-type-property|ILC-font-size-property|
  ILC-typeface-property|ILC-rotation-property|
  ILC-writing-direction-offset-property|
  ILC-formatting-type-property|
  ILC-line-progression-direction-offset-property)+ >

<!ELEMENT  ILC-type-property  (ILC-type-name, ILC-type-value) >
<!ELEMENT  ILC-type-name      (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  ILC-type-value     (glbname) -- STRUCTURED NAME -- >
<!ELEMENT  ILC-font-size-property (ILC-font-size-name, 
  ILC-font-size-value-type,
  ILC-font-size-value) >
<!ELEMENT ILC-font-size-name   (glbname) -- STRUCTURED NAME -- >
<!ELEMENT ILC-font-size-value-type  - o EMPTY >
<!ATTLIST ILC-font-size-value-type (ABS|RELATIVE) "ABS" >
<!ELEMENT ILC-font-size-value (relr) -- REL RATIONAL -- >

<!ELEMENT ILC-typeface-property  (ILC-typeface-name, ILC-typeface-value)
  >
<!ELEMENT ILC-typeface-name   (glbname) -- STRUCTURED NAME -- >
<!ELEMENT ILC-typeface-value  (glbname) - STRUCTURED NAME -- >

<!ELEMENT ILC-rotation-property (ILC-rotation-name, ILC-rotation-value) 
  >
<!ELEMENT ILC-rotation-name (relr) -- REL RATIONAL -- >
<!ELEMENT ILC-rotation-value  - o EMPTY >
<!ATTLIST ILC-rotation-value (0|90|180|270) "0"  >

<!ELEMENT ILC-writing-direction-offset-property
 (ILC-writing-direction-offset-name,
  ILC-writing-direction-offset-value,
  ILC-writing-direction-offset-value) >
<!ELEMENT ILC-writing-direction-offset-name (glbname) -- STRUCTURED NAME
  -- >
<!ELEMENT ILC-writing-direction-offset-value-type - o EMPTY >
<!ATTLIST ILC-writing-direction-offset-value-type (ABS|RELATIVE) "ABS" >
<!ELEMENT ILC-writing-direction-offset-value (relr) -- REL RATIONAL -- >

<!ELEMENT ILC-formatting-type-property
 (ILC-formatting-type-name, 
  ILC-formatting-type-value) >
<!ELEMENT ILC-formatting-type-name (glbname) -- STRUCTURED NAME -- >
<!ELEMENT ILC-formatting-type-value - o EMPTY >
<!ATTLIST ILC-formatting-type-value  (HEAD|CENTER|TAIL|JUSTIFICATION) =
  "HEAD" >

<!ELEMENT ILC-line-progression-direction-offset-property
 (ILC-line-progression-direction-offset-name,
  ILC-line-progression-direction-offset-value,
  ILC-line-progression-direction-offset-value-type) >
<!ELEMENT ILC-line-progression-direction-offset-name (glbname)
                                             -- STRUCTURED NAME -- >
<!ELEMENT ILC-line-progression-direction-offset-value-type - o EMPTY >
<!ATTLIST ILC-line-progression-direction-offset-value-type 
 (ABS|RELATIVE) "ABS" >
<!ELEMENT ILC-line-progression-direction-offset-value (relr) -- REL =
  RATIONAL -- >

Appendix 3: Voting Summaries of the PDAMs

A3.1 Voting Summary of PDAM3 to ISO/IEC 9541-1

ISO/IEC JTC 1/SC 34
Document Description and Processing Languages


ISO/IEC JTC 1/SC34 N 94

DATE:  1999-08-19

REPLACES

DOC TYPE:
Summary of Voting/Table of Replies

TITLE:
Summary of Voting on SC 34 N 71, ISO/IEC 9541-1:1991/PDAM 3,
Information Technology - Font Information
Interchange - Part 1:  Architecture - Amendment 3:  Multilingual
extensions to font resource architecture

SOURCE:
Secretariat, ISO/IEC JTC 1/SC 34

PROJECT:  1.34.27.01.03

STATUS:
To JTC 1/SC 34 for information and to WG 2 for preparation of a
disposition of comments report and recommendation on further
progression of the work.

ACTION ID:  FYI

DUE DATE:

DISTRIBUTION:  P and L Members
               SC Chairman
               WG Conveners and Secretariats

MEDIUM:  E

DISKETTE NO.:

ISO/IEC JTC 1/SC 34 N 94

Summary of Voting on SC 34 N 71, ISO/IEC 9541-1:1991/PDAM 3, Information Technology - Font Information Interchange - Part 1: Architecture - Amendment 3: Multilingual extensions to font resource architecture  

SC 34 National Body P-Members (13)

Australia, Brazil, Canada, China, Denmark, France, Ireland, Italy, Japan, Netherlands, Norway, United Kingdom, United States

P-Members in Favour (8 of 13)

Australia, China, Denmark, Ireland, Italy, Japan (w/comments), Netherlands, Norway

P-Members Voting Against (0 of 13)

P-Members Abstaining (2 of 13)

France, US

P-Members who did not vote (3 of 13)

Brazil, Canada, UK


COMMENTS

Japan

The National Body of Japan approves the PDAM3 to ISO/IEC 9541-1 (SC34 N0071) with the following comments.

(1) D.1, Figure 5, 6 and 7
Illustrated examples should be separated with each other.
(2) D.2 Figure 8
Illustrated examples should be separated with each other.


A3.2 Voting Summary of PDAM1 to ISO/IEC 9541-2

ISO/IEC JTC 1/SC 34
Document Description and Processing Languages


ISO/IEC JTC 1/SC34 N 95

DATE:  1999-08-19

REPLACES

DOC TYPE:
Summary of Voting/Table of Replies

TITLE:
Summary of Voting on SC 34 N 72, ISO/IEC 9541-2:1991/PDAM 1,
Information Technology - Font Information Interchange - Part 2:
Interchange Format - Amendment 1:  Support for font technology
advances

SOURCE:
Secretariat, ISO/IEC JTC 1/SC 34

PROJECT:  1.34.27.02.01

STATUS:

ACTION ID:  FYI

DUE DATE:

DISTRIBUTION:  P and L Members
               SC Chairman
               WG Conveners and Secretariats

MEDIUM:  E

DISKETTE NO.:

ISO/IEC JTC 1/SC 34 N 95

Summary of Voting on SC 34 N 72, ISO/IEC 9541-2:1991/PDAM 1, Information Technology - Font Information Interchange - Part 2: Interchange Format - Amendment 1: Support for font technology advances 

SC 34 National Body P-Members (13)

Australia, Brazil, Canada, China, Denmark, France, Ireland, Italy, Japan, Netherlands, Norway, United Kingdom, United States

P-Members in Favour (8 of 13)

Australia, China, Denmark, Ireland, Italy, Japan (w/comments), Netherlands, Norway

P-Members Voting Against (0 of 13)

P-Members Abstaining (2 of 13)

France, US

P-Members who did not vote (3 of 13)

Brazil, Canada, UK


COMMENTS

Japan

The National Body of Japan approves the PDAM3 to ISO/IEC 9541-1 (SC34 N0071) with the following comments.

(1) 1.
The meaningless "=" at line ends should be removed.
(2) 2.
The meaningless "=" at line ends should be removed.