re: [cgmo-webcgm] ISSUE: font mapping (continued)

[Don <dlarson@cgmlarson.com>]

dave

Here's my thoughts on font substitution issue.

I think that we need standard (viewer independent way) to do font 
substitution in the viewer for all the reasons you have mentioned.

I do think though, that variances in font names like whitespaces, 
hyphens and upper/lower case will cause a matching problem as Benoit
suggested, e.g.

Courier-BoldOblique 
Courier BoldOblique
CourierBoldOblique 

 
My thinking is that we need to further specify that when the 
viewer is trying to match fonts in CGM for substitution, it
should ignore whitespace, hyphens, and convert to lower 
case in the font names.  

We do this now in our font substitution algorithm and it has 
worked well for us.

 
Regards,
Don
 >  There was a long thread (primarily between PTC and Boeing) concerning
 >  the font mapping requirement.

 >  See:
 >  http://lists.oasis-open.org/archives/cgmo-webcgm/200803/msg00111.html

 >  It's time to get other's opinions.  Please review the thread and reply
 >  with you're thoughts (vendors?, users?)

 >  My position is that when the font in the CGM file is not a match to a
 >  font on the user platform, I want a "standard" method to specify which
 >  font to substitute..

 >  Thx...Dave

 >  Technical Fellow - Graphics/Digital Data Interchange
 >  Boeing Commercial Airplane
 >  206.544.3560, fax 206.662.3734
 >  david.w.cruikshank@boeing.com


 >  ---------------------------------------------------------------------
 >  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