RE: [cgmo-webcgm] ISSUE: packaging of the font interchange/mapping

["Weidenbrueck, Dieter" <dweidenbrueck@ptc.com>]

Lofton,

one more comment to this:

Do we want the font mapping to be file specific or viewer specific?

For the past 12 years we have been using a viewer specific font mapping
file, and that seemed perfectly enough for everybody. It sounds like
overkill to me to do a separate font mapping for each CGM.

That said, an XCF section that overrides the default font mapping as
specified in one way or the other for the viewer for one specific file
would be fine with me. 

Dieter

-----Original Message-----
From: Lofton Henderson [mailto:lofton@rockynet.com] 
Sent: Montag, 7. Januar 2008 19:24
To: CGM Open WebCGM TC
Subject: [cgmo-webcgm] ISSUE: packaging of the font interchange/mapping

This is a peripheral issue on the font mapping "file".

ISSUE:  How is the font mapping information packaged?

DISCUSSION:  It has been resolved [1] that it should be in XML format.
[1] discusses it as a "file".  Is it in a separate standalone file?  Or
will it be a new defined subsection of the current XCF format, e.g., a
"<prelude>" 
element or some such?   If it is a separate standalone file, then we 
potentially have (at least) two separate XML-based companion files
associated with each CGM instance.

OPTIONS:
1.) separate stand-alone file;
2.) subsection within the XCF file;
3.) other

RECOMMENDATION:  #2, define it as a new subsection within the XCF --
within a new 'header' or 'prelude' or <whatever> element.

-Lofton.

At 10:29 AM 1/7/2008 -0700, Lofton Henderson wrote:
>At 02:49 PM 1/6/2008 -0800, Cruikshank, David W wrote:
>>Font mapping will be specified using an XML DTD
>
>[...] the Issues matrix:
>[1]
>http://www.oasis-open.org/committees/download.php/26654/WebCGM-2_1_issu
>es_resolution_matrix_V3.doc



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php