OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cgmo-webcgm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [cgmo-webcgm] Action Item: PROPOSAL: setStyleProperty - text-font


Lofton,
 
I am not sure whether I understand your concern:
-----Original Message-----
From: Lofton Henderson [mailto:lofton@rockynet.com]
Sent: Monday, June 20, 2005 5:42 PM
To: dieter@itedo.com; cgmo-webcgm@lists.oasis-open.org
Subject: Re: [cgmo-webcgm] Action Item: PROPOSAL: setStyleProperty - text-font

I'm uncomfortable with one aspect of this proposal:  two different applications processing the same WebCGM 2.0 content could mysteriously get very different results.  This is not supposed to happen in WebCGM.  For example, let's suppose this link occurs in a HTML + WebCGM parts list application:

<a href="pump.cgm#xcf(pump-styles.xml)">Pump subassembly</a>
and the XCF contains:
<webcgm ... text-font="Lofton_Calligraphic" >
[DW] following my proposal, the application would do the following (in pseudo-code):
 
if "Lofton_Calligraphic" is available then
    for each text element in the selected APS
        if "Lofton_Calligraphic" contains all glyphs needed to represent the text
            set text font to "Lofton_Calligraphic"
    end for
end if
 
As I assume that the font does not exist, the first check would fail, and hence the application
would not do anything.
If a font with that name really exists, the next test would detect whether it covers the glyphs
needed for the text elements. If this is not the case, nothing will happen either.
I do not understand how two different applications would come to different results other than
if they run in two different environments, one with this font installed, and the other one without?
 
Please let me know if I am missing anything.
Regards,
Dieter
 

I know that it is not part of Dieter's design intent, but this in fact provides a loophole to completely evade the tight text restrictions and highly predictable graphical text results of WebCGM 1.0.

I am not yet convinced that this is a wise thing to do.

-Lofton.

At 12:28 PM 6/20/2005 +0200, Dieter  Weidenbrück wrote:
All,
 
here is my proposal regarding the text-font style property:
 
"text-font: The text-font style property redefines the text font that is used for drawing graphical text within the APS to which it is applied. Text-font corresponds to the font set inside a CGM using the FONT LIST and TEXT FONT INDEX elements. The required behavior is as follows: the application needs to check first whether the specified font resource exists. If so, it has to further ensure that all glyphs of the text it will be applied to exist in that font. If both checks are successful, the application shall apply the font to the text. In all other cases the text remains unchanged."
 
 
Comment: I wanted to specify a simply yet clear way for a successful font change. By restricting it to the cases where the font is installed and appropriate I think this can be accomplished.
 
Regards,
Dieter
 
 
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]