<HTML>
<HEAD>
<TITLE>Re: [mpeg-OTspec] Toward a Composite Font format specification</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Vladimir:<BR>
<BR>
Do you believe a composite font recipe cannot be useful to a consumer unless it fulfills the creator’s intent?<BR>
<BR>
Regards,<BR>
<BR>
— daan Strebe<BR>
Senior Computer Scientist<BR>
Adobe Systems Incorporated<BR>
<BR>
<BR>
On 09/09/15 15:55, "Levantovsky, Vladimir" <<a href="Vladimir.Levantovsky@MonotypeImaging.com">Vladimir.Levantovsky@MonotypeImaging.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Daniel, <BR>
<BR>
You wrote:<BR>
“Meanwhile, what is a specification? It is a rigorous communication of intent. Because of the many variables we cannot control, and because of inability to anticipate the consumer’s intent, we are left to ask what it is we are communicating. The answer is that we are communicating the creator’s intent. That is this specification’s raison d’être. If we start issuing instructions to the consumer about what we have decided is necessary from that recipe, then we are no longer communicating the creator’s intent — which is already conveyed by the recipe — but instead we are communicating OUR intent. How did our intent come into play here?”<BR>
<BR>
<BR>
I am in full agreement with your statement that the only reason for specification to be developed is to communicate the creator’s intent. This is exactly why the specification must issue the instructions to the consumer about what has to be done on the implementation side to ensure that creator’s intent can be fulfilled. Please note – this is necessary only for the purpose to fulfill the creator’s intent, and it has nothing to do with OUR intent.<BR>
<BR>
Ideally, all provisions of the spec have to be implemented by all consumers – this will guarantee the 100% interoperability between different implementations. At a minimum, in order to enable the guaranteed minimal level of interoperability we ought to come up with the list of elements (data formats, attributes, etc.) that must be supported by all consumers - this has to be done so that <B>the creator’s intent</B> (not <B>our</B> intent) can be fulfilled. Making everything optional would make it impossible for creators to communicate their intent reliably, knowing full well that consumers may disregard any and all parts of their recipe.<BR>
<BR>
“Any consumer who cares about typographic fidelity ought to implement the entire specification.”<BR>
<BR>
Again, I agree with you. In ideal world – this is exactly what we should do, and the spec must mandate everything. In reality - this is just another reason why I believe that the spec ought to say what must be implemented (and why), and what may be implemented if a certain outcome is desired. (OpenType specification is a good example of this – it has mandatory required tables, conditional mandatory tables that are necessary only if a certain type of outlines is supported, and optional table that are needed only if certain functionality is needed.)<BR>
<BR>
I believe that making everything optional and giving consumers the complete freedom to implement any parts of the spec of their own choosing will make it impossible to fulfill the creator’s intent and will result in interoperability nightmare.<BR>
<BR>
Regards,<BR>
Vladimir<BR>
<BR>
<BR>
<BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><B>From:</B> Daniel Strebe [<a href="mailto:dstrebe@adobe.com">mailto:dstrebe@adobe.com</a>] <BR>
<B>Sent:</B> Friday, September 11, 2009 3:52 PM<BR>
<B>To:</B> Levantovsky, Vladimir; Ken Lunde; <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><BR>
<B>Subject:</B> Re: [mpeg-OTspec] Toward a Composite Font format specification<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Vlad, and colleagues,<BR>
<BR>
I had hoped our policy in this regard was settled so we could move on.<BR>
I see the interoperability as the main benefit of standardization since it provides a certain level of guarantee for a content creator (in this case, for a Composite Font creator) that the font resource (a Composite Font) and a content that uses it will be processed and presented to an end-user as intended by the author.<BR>
<BR>
The specification we produce will guarantee nothing regardless of how we write it. Composite fonts will be only a tiny component of a broader environment that we have no control over even if we “mandate” aspects of consumer behavior. Specifically, we cannot guarantee:<BR>
</SPAN></FONT><OL><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>The presence of the base fonts by some loose match (i.e, font name).
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>The presence of the base fonts by some strict match (i.e., font technology, version number, or computational hash).
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>The ability of the environment at large to render according to the component fonts’ specifications.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Strict adherence of the component fonts to their formats’ specifications.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Clarity (lack of ambiguity) in the specifications of the component fonts’ formats.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Anything at all about how the viewing application lays out text.
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Anything at all about the intent of the consumer. <BR>
</SPAN></FONT></OL><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
PDF has control over everything except (4) and (5), and could conceivably even make reasonable contingencies or clarifications for both. How does PDF have control over the intent of the consumer? It doesn’t directly, of course. But the implied intent of the consumer is PDF’s raison d’être. It is built on the assumption that the consumer wishes to display a document in exactly the same way it was created, now and forever, even if the original constructing software is not available. PDF purports to separate construction of a document from display of the completed document so that it retains its fidelity during subsequent communications in and through hostile environments. That is its utility. If that is not your intent, you do not need to use PDF.<BR>
<BR>
We have already agreed, however, that we cannot anticipate the intent of the composite font consumer. We have imagined typographic scenarios, where details of layout are critica</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>l</SPAN></FONT><SPAN STYLE='font-size:11pt'>. We have imagined fallback scenarios where layout is subordinate to legibility. We have imagined deployment in mobile environments where typography has no meaning. We have imagined propriety systems where the intent is some implied contract outside the composite font specification. Even if the creator had some intent, the fact that the consumer “violates” that intent in no way invalidates the utility of the recipe. It is the consumer who ultimately determines the utility of what is consumed, not the creator. You can create an exquisite chocolate, but you cannot make the eater taste it as you do.<BR>
<BR>
Meanwhile, what is a specification? It is a rigorous communication of intent. Because of the many variables we cannot control, and because of inability to anticipate the consumer’s intent, we are left to ask what it is we are communicating. The answer is that we are communicating the creator’s intent. That is this specification’s raison d’être. If we start issuing instructions to the consumer about what we have decided is necessary from that recipe, then we are no longer communicating the creator’s intent — which is already conveyed by the recipe — but instead we are communicating OUR intent. How did our intent come into play here?<BR>
<BR>
Nor do I find the argument of interoperability compelling. Any consumer who cares about typographic fidelity ought to implement the entire specification. If typographic fidelity is not the intent of the consumer, then what do we mean by “interoperability”? From whose standpoint? And how does dictating some portions of the specification but not others contribute to interoperability? If the consumer receives a document containing a richly specified composite font, but the consumer is only concerned with legibility, then what is wrong with the consumer saving the document with only the abbreviated portion of the recipe that it knows how to deal with? It is hardly likely that the remaining traits of the original document were otherwise preserved by the viewing application, since its purpose never was typographic fidelity. Alternatively, what if the consumer saves the full recipe? What good is that when it strips out all the typography of the document anyway? <BR>
<BR>
Hence I cannot agree that PDF provides an analogy for our circumstances. The factors that contributed to its success differ greatly from the factors in play here. We would be better served by looking at XML, for example. There is a case where the specification of creator’s intent is rigorous but the consumer is free to deal with “recipes” as best it may. Needless to say, XML is extremely successful, and indeed we seem to have settled on it ourselves for creating recipes.<BR>
<BR>
Let me suggest we issue recommendations on minimal support levels for various consumer intentions we identify. I do not even see much harm in “requiring” such support in order to be “compliant” with those specific categories of intent. Perhaps that will make the job of consumers easier: they can pick some canned definition of their intent and implement against it without having to think hard about it. I strongly advise against precluding implementations outside those recommendations, however. No one is well-served by throttling innovative uses — and I have a strong suspicion we will witness uses we never imagined.<BR>
<BR>
— Regards,<BR>
<BR>
Daniel “daan” Strebe<BR>
Senior Computer Scientist<BR>
Adobe Systems Incorporated<BR>
<BR>
<BR>
On 09/09/11 7:55, "Levantovsky, Vladimir" <<a href="vladimir.levantovsky@monotypeimaging.com">vladimir.levantovsky@monotypeimaging.com</a>> wrote:<BR>
<BR>
<BR>
<BR>
<BR>
<FONT COLOR="#1F497D">Ken,<BR>
<BR>
I do understand your concerns and agree that in some circumstances the mandate to implement a particular feature may put an additional burden on the consumers of the Composite Font recipe.<BR>
<BR>
At the same time, the main intent of any standardization activity is to create an environment where multiple different implementations are compliant and interoperable. I see the interoperability as the main benefit of standardization since it provides a certain level of guarantee for a content creator (in this case, for a Composite Font creator) that the font resource (a Composite Font) and a content that uses it will be processed and presented to an end-user as intended by the author.<BR>
<BR>
Developing a standard that does not provide this guarantee of baseline interoperability defeats the purpose of standardization. We may end up having multiple different implementations that are all compliant with the specification but incompatible with each other, producing different results when presented with the same content for rendering. This would be a very unfortunate outcome. <BR>
<BR>
Currently, we have very few consumers that support Composite Font functionality. For many, the Composite Fonts specification will offer a guideline of what (and how) new features should be implemented. I am sure that in many circumstances the implementers will appreciate specification that provides clear and unambiguous description of the features to be supported, rather than presenting them with many different options for implementers to choose from. Striking the healthy balance between the core set of features (that we want to see supported by all interoperable implementations) and a set of optional features (that we wish to see supported) is the ultimate challenge that in my opinion should be looked at not only from the position of the implementer (a consumer of the Composite Font recipe) but first and foremost from the creator point of view. PDF is a good example – its success was to significant extent determined by the guarantees of consistency of presentation of PDF documents it offered to content creators.<BR>
<BR>
Best regards,<BR>
Vlad<BR>
<BR>
<BR>
</FONT><BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><B>From:</B> <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> [<a href="mailto:mpeg-OTspec@yahoogroups.com">mailto:mpeg-OTspec@yahoogroups.com</a>] <B>On Behalf Of </B>Ken Lunde<BR>
<B>Sent:</B> Friday, September 04, 2009 4:47 PM<BR>
<B>To:</B> <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><BR>
<B>Subject:</B> Re: [mpeg-OTspec] Toward a Composite Font format specification<BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'><BR>
<BR>
<BR>
Vladimir,<BR>
<BR>
My main fear in this is that we'd be asking consumers to do something <BR>
that they are already doing, or overriding it. Some consumers may lack <BR>
the ability to override the behavior that dictates whether a device or <BR>
embedded (or web) font is used.<BR>
<BR>
Ultimately, each consumer will need to decide whether it can honor the <BR>
intent of the Composite Font recipe.<BR>
<BR>
Regards...<BR>
<BR>
-- Ken<BR>
<BR>
On 2009/08/31, at 12:17, Levantovsky, Vladimir wrote:<BR>
<BR>
> Ken,<BR>
><BR>
> I agree that existing implementations already deal with the scenarios<BR>
> where fonts may be present locally and/or embedded, and that consumers<BR>
> who support embedded fonts may behave differently with regard to <BR>
> giving<BR>
> preferences to embedded vs. local fonts. I see this uncertainty in<BR>
> consumer behavior as a potential interoperability problem.<BR>
><BR>
> It is true that embedded fonts are most likely to be used when a<BR>
> producer cares about content presentation and appearance, and this is<BR>
> when the attribute about font location is likely to be present. I <BR>
> think<BR>
> it would be seen as a benefit to give producers a certain level of<BR>
> assurance of consumer's behavior. In fact, I know that in some<BR>
> environments this has already been done. For example, in Java MIDP3.0<BR>
> profile - if there is an apparent conflict between embedded and local<BR>
> font (e.g. both fonts have the same names), the embedded (or <BR>
> downloaded)<BR>
> font is always given a preference to make sure that the content is<BR>
> rendered using a resource chosen by producer (author).<BR>
><BR>
> In general, I believe that we should try (whenever possible) to reduce<BR>
> potential uncertainty in consumer behavior, especially if a feature<BR>
> under consideration (e.g. a preference between embedded and local <BR>
> font)<BR>
> is not going to affect implementation complexity and cost. A good<BR>
> specification should have a healthy balance between mandatory and<BR>
> optional features - a specification that is overly strict may be <BR>
> seen as<BR>
> burden for implementers, but, alternatively, a specification where<BR>
> everything is optional (MMS come to mind) will likely result in<BR>
> producing incompatible implementations.<BR>
><BR>
> Regards,<BR>
> Vladimir<BR>
><BR>
><BR>
>> -----Original Message-----<BR>
>> From: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> [<a href="mailto:mpeg-">mailto:mpeg-</a> <BR>
>> <a href="OTspec@yahoogroups.com">OTspec@yahoogroups.com</a> <<a href="mailto:OTspec%40yahoogroups.com">mailto:OTspec%40yahoogroups.com</a>> ]<BR>
>> On Behalf Of Ken Lunde<BR>
>> Sent: Saturday, August 29, 2009 10:32 AM<BR>
>> To: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> <BR>
>> Subject: Re: [mpeg-OTspec] Toward a Composite Font format<BR>
> specification<BR>
>><BR>
>> Vladimir,<BR>
>><BR>
>> In thinking about the issue that you raised, I don't think that we<BR>
>> need to worry about the case when a font with the same name exists on<BR>
>> the device and also embedded in the file. Consider the fact that<BR>
>> consumers who support embedded fonts already need to deal with this<BR>
>> scenario, and obviously prefer one over the other. So, if this<BR>
>> attribute specifies one or the other (device versus embedded), that <BR>
>> is<BR>
>> sufficient to guide the consumer. And, there are some consumers that<BR>
>> are unable to support files with embedded fonts. Likewise, some<BR>
> closed-<BR>
>> environment consumers may even be unable to support device fonts,<BR>
>> though there will be very few of these in the real world.<BR>
>><BR>
>> In any case, if the producer cares about font location (device,<BR>
>> embedded, or web), what this attribute constitutes is a preference. <BR>
>> If<BR>
>> it is flagged as a device font, a path to the font may be included as<BR>
>> part of this attribute. If it is flagged as embedded, it is treated <BR>
>> as<BR>
>> a boolean, because it is a binary condition.<BR>
>><BR>
>> My reasoning is that producers would be asking consumers to do<BR>
>> something that they already support, or already have a strong<BR>
>> preference one way or another, and also that producers may be<BR>
>> specifying information that a consumer would be forced to ignore.<BR>
>><BR>
>> Feel free to prove me wrong about this issue.<BR>
>><BR>
>> -- Ken<BR>
>><BR>
>> On 2009/08/28, at 14:02, Levantovsky, Vladimir wrote:<BR>
>><BR>
>>> Ken,<BR>
>>><BR>
>>> I like your proposed approach, and I agree that issues such as<BR>
>>> rendering and font access permissions should be left out of<BR>
>>> composite font recipe. With regards to font location, one additional<BR>
>>> case that we should consider and clarify is if the font is embedded<BR>
>>> in a document (or in a CF recipe) and is also present on a device. I<BR>
>>> believe that some implementations in these circumstances may<BR>
>>> sometime disregard the embedded font and use local copy instead,<BR>
>>> although I can imagine there may be circumstances when authors may<BR>
>>> want the embedded font be used at all times, regardless of whether<BR>
>>> the same font is present on a device (e.g. if embedded font contains<BR>
>>> additional character set that may not be part of the local font).<BR>
>>><BR>
>>> Regards,<BR>
>>> Vladimir<BR>
>>><BR>
>>><BR>
>>>> -----Original Message-----<BR>
>>>> From: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> [<a href="mailto:mpeg-">mailto:mpeg-</a><BR>
>>>> <a href="OTspec@yahoogroups.com">OTspec@yahoogroups.com</a> <<a href="mailto:OTspec%40yahoogroups.com">mailto:OTspec%40yahoogroups.com</a>> ]<BR>
>>>> On Behalf Of Ken Lunde<BR>
>>>> Sent: Friday, August 28, 2009 4:41 PM<BR>
>>>> To: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> <BR>
>>>> Subject: Re: [mpeg-OTspec] Toward a Composite Font format<BR>
>>>> specification<BR>
>>>><BR>
>>>> Mikhail and others,<BR>
>>>><BR>
>>>> Sorry for the delay. I was discussing this issue internally with a<BR>
>>>> couple different development teams. I wanted to make sure that our<BR>
>>>> bases are covered before I suggested some working definitions.<BR>
>>>><BR>
>>>> I like the idea of using "LocationHint" as the name of this<BR>
>>>> <ComponentFont> attribute.<BR>
>>>><BR>
>>>> Getting back to the issue, I think that there are three of them to<BR>
>>>> consider:<BR>
>>>><BR>
>>>> 1) Font location. Installed onto the device proper, meaning in a<BR>
>>>> standard location, embedded in the file that references it, either<BR>
>>>> directly or via a Composite Font recipe, or elsewhere (web fonts).<BR>
>>>><BR>
>>>> 2) Rendering. Done by the OS, the application itself, or some other<BR>
>>>> rendering client such as a library.<BR>
>>>><BR>
>>>> 3) Access. This boils down to private versus public. In general, if<BR>
>> a<BR>
>>>> font is embedded in the file that references it, it is effectively<BR>
>>>> private, and available only to the consumer. If a font is installed<BR>
>>>> on<BR>
>>>> the device in a standard location, it is effectively public,<BR>
>> multiple<BR>
>>>> consumers have access to it, and can thus use it.<BR>
>>>><BR>
>>>> In the context of Composite Fonts, and considering producers (those<BR>
>>>> who create the Composite Font recipes) and consumers (those who use<BR>
>>>> or<BR>
>>>> "consume" the Composite Font recipes), I cannot think of any usage<BR>
>>>> scenarios that specify how rendering is to be done. So, Issue #2<BR>
>>>> becomes moot. The consumer already knows how to handle this, and<BR>
>>>> simply knowing where to look for the font is sufficient.<BR>
>>>><BR>
>>>> And, Issue #3 is a non-issue in the sense that the location of the<BR>
>>>> font implies its access level.<BR>
>>>><BR>
>>>> Thus, what we have left is Issue #1, which is about location.<BR>
>>>> Embedded<BR>
>>>> fonts do not need a location, but need a name (this is required<BR>
>>>> anyway<BR>
>>>> for any Component Font), and it may be useful to flag it as an<BR>
>>>> embedded font. Device fonts can benefit from a location, such as a<BR>
>>>> path, and the usage scenario you gave helps. I assume that web<BR>
> fonts<BR>
>>>> merely require a URL.<BR>
>>>><BR>
>>>> The following are three definitions to consider:<BR>
>>>><BR>
>>>> Device font:<BR>
>>>> A font installed on the device, in a standard location, and thus<BR>
>>>> accessible by multiple consumers.<BR>
>>>><BR>
>>>> Embedded font:<BR>
>>>> A font or subset of a font that is embedded in a file that<BR>
>>>> references it, and thus accessible only by the file's consumer.<BR>
>>>><BR>
>>>> Web font:<BR>
>>>> A font that is neither installed on the device nor embedded in a<BR>
>>>> file, but is otherwise accessible through the network.<BR>
>>>><BR>
>>>> Thoughts?<BR>
>>>><BR>
>>>> -- Ken<BR>
>>>><BR>
>>>> On 2009/08/26, at 15:52, Mikhail Leonov wrote:<BR>
>>>><BR>
>>>>> Hi Ken,<BR>
>>>>> This type of issue came up in some of my recent conversations as<BR>
>>>> well.<BR>
>>>>><BR>
>>>>> Conceptually, recipe creators want to specify some additional<BR>
>>>>> properties about a component font, such as its location. For some<BR>
>>>>> scenarios a simple Boolean flag is sufficient, while for other<BR>
>>>>> scenarios something like a URL or an internal resource path is<BR>
>>>>> necessary.<BR>
>>>>><BR>
>>>>> To give an example of the latter, a document could embed 2<BR>
> versions<BR>
>>>>> of the same font and use different resource paths, for example /<BR>
>>>>> Resources/Fonts/1/arial.ttf and /Resources/Fonts/2/arial.ttf.<BR>
>>>>><BR>
>>>>> Given there is a large number of potential methods for storing<BR>
> font<BR>
>>>>> file locations, I(tm)fd like to suggest for this property to be<BR>
> opaque<BR>
>>>>> and optional, akin to a hint rather than a strict directive.<BR>
>>>>><BR>
>>>>> How does a new string property LocationHint sound?<BR>
>>>>><BR>
>>>>> Thanks!<BR>
>>>>> Mikhail Leonov<BR>
>>>>> Microsoft<BR>
>>>>><BR>
>>>>><BR>
>>>>> From: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> [<a href="mailto:mpeg-">mailto:mpeg-</a><BR>
>>>>> <a href="OTspec@yahoogroups.com">OTspec@yahoogroups.com</a> <<a href="mailto:OTspec%40yahoogroups.com">mailto:OTspec%40yahoogroups.com</a>> ] On Behalf Of Ken Lunde<BR>
>>>>> Sent: Wednesday, August 26, 2009 2:26 PM<BR>
>>>>> To: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> <BR>
>>>>> Subject: Re: [mpeg-OTspec] Toward a Composite Font format<BR>
>>>>> specification<BR>
>>>>><BR>
>>>>><BR>
>>>>><BR>
>>>>> All,<BR>
>>>>><BR>
>>>>> Slight topic deviation ahead...<BR>
>>>>><BR>
>>>>> I was in a meeting this morning, and its discussions led to an<BR>
> idea<BR>
>>>>> for another <ComponentFont> attribute that we have not yet<BR>
>>>> considered.<BR>
>>>>> Under some circumstances, especially when dealing with embedded<BR>
>>>> fonts,<BR>
>>>>> it may be useful to specify whether the font is embedded (in a<BR>
> file<BR>
>>>>> that references the Composite Font or the Component Font) or<BR>
>>>> available<BR>
>>>>> on the device (a "device" font). This, of course, would be<BR>
>> optional,<BR>
>>>>> but I guarantee that some producers will want to specify this.<BR>
>>>>><BR>
>>>>> I am not sure about the best way to characterize this, in terms of<BR>
>>>>> an<BR>
>>>>> attribute name, but perhaps we can state that all <ComponentFont><BR>
>>>>> instances are "device fonts" unless an "IsEmbedded" boolean flag<BR>
> is<BR>
>>>>> specified.<BR>
>>>>><BR>
>>>>> I would welcome any thoughts about this.<BR>
>>>>><BR>
>>>>> -- Ken<BR>
>>>>><BR>
>>>>> On 2009/08/26, at 12:20, Thomas Phinney wrote:<BR>
>>>>><BR>
>>>>>> My first assumption would be that all scaling should include<BR>
>>>>>> scaling<BR>
>>>>>> metrics, though I am mindful of the issues Karsten brings up.<BR>
>>>>>><BR>
>>>>>> T<BR>
>>>>>><BR>
>>>>>> On Wed, Aug 26, 2009 at 9:27 AM, Daniel<BR>
>>>> Strebe<<a href="dstrebe@adobe.com">dstrebe@adobe.com</a> <<a href="mailto:dstrebe%40adobe.com">mailto:dstrebe%40adobe.com</a>> <<a href="mailto:dstrebe%40adobe.com">mailto:dstrebe%40adobe.com</a><BR>
>>>>>>>><BR>
>>>>>> wrote:<BR>
>>>>>>><BR>
>>>>>>> Thomas,<BR>
>>>>>>><BR>
>>>>>>> Thanks for chiming in. To clarify, do you mean to advocate<BR>
>> scaling<BR>
>>>>>>> horizontally within the same design space when you mention faux<BR>
>>>>>>> small caps?<BR>
>>>>>>> (Meaning, without increasing the glyph advance width,<BR>
> escapement,<BR>
>>>>>>> and<BR>
>>>>>>> kerning values?)<BR>
>>>>>>><BR>
>>>>>>> Regards,<BR>
>>>>>>><BR>
>>>>>>> (tm)\ daan Strebe<BR>
>>>>>>> Senior Computer Scientist<BR>
>>>>>>> Adobe Systems Incorporated<BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>> On 09/08/25 21:51, "Thomas Phinney"<BR>
>>>> <<a href="tphinney@cal.berkeley.edu">tphinney@cal.berkeley.edu</a> <<a href="mailto:tphinney%40cal.berkeley.edu">mailto:tphinney%40cal.berkeley.edu</a>> <<a href="mailto:tphinney%40cal.berkeley.edu">mailto:tphinney%40cal.berkeley.edu</a><BR>
>>>>>>>>><BR>
>>>>>>> wrote:<BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>> I'd advocate keeping the three different scaling factors<BR>
>> (overall,<BR>
>>>> X<BR>
>>>>>>> and Y). I can honestly imagine plenty of use cases for them,<BR>
> both<BR>
>>>> in<BR>
>>>>>>> traditional and non-traditional cases.<BR>
>>>>>>><BR>
>>>>>>> One use for asymmetric X/Y scaling is in manufacturing small<BR>
>> caps.<BR>
>>>>>>> One<BR>
>>>>>>> could use a composite font mechanism to build faux small caps,<BR>
>>>>>>> possibly scaled slightly so as to be slightly wider than<BR>
> strictly<BR>
>>>>>>> proportional scaling. Ditto for creating numeric (or alphabetic)<BR>
>>>>>>> inferiors or superiors. Using the composite font mechanism would<BR>
>>>>>>> allow<BR>
>>>>>>> for taking the base glyphs from a heavier weight of the "same"<BR>
>>>>>>> typeface....<BR>
>>>>>>><BR>
>>>>>>> cheers,<BR>
>>>>>>><BR>
>>>>>>> T<BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>>><BR>
>>>>>><BR>
>>>>>><BR>
>>>>>><BR>
>>>>>> --<BR>
>>>>>> "Men occasionally stumble over the truth, but most of them pick<BR>
>>>>>> themselves up<BR>
>>>>>> and hurry off as if nothing ever happened."<BR>
>>>>>> - Sir Winston Churchill<BR>
>>>>>><BR>
>>>>>><BR>
>>>>>> ------------------------------------<BR>
>>>>>><BR>
>>>>>> Yahoo! Groups Links<BR>
>>>>>><BR>
>>>>>><BR>
>>>>>><BR>
>>>>><BR>
>>>><BR>
>>>><BR>
>>>><BR>
>>>> ------------------------------------<BR>
>>>><BR>
>>>> Yahoo! Groups Links<BR>
>>>><BR>
>>>><BR>
>>>><BR>
>><BR>
>><BR>
>><BR>
>> ------------------------------------<BR>
>><BR>
>> Yahoo! Groups Links<BR>
>><BR>
>><BR>
>><BR>
<BR>
<BR>
<BR>
<FONT COLOR="#FFFFFF"><BR>
</FONT><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>