<br><font size=2 face="Verdana">A few thoughts ...</font>
<br>
<br><font size=2 face="Verdana">Target Font - how will this be specified?
Does it need to be on the same system -or- can it be on a server
/ internet e.g. http://ibm.com/fonts/CourierIBM.ttf ? What is the
'unique name' ... Full Font Name - file name - WWS - combination of these?
I would like to see a way to specify a font that isn't on the current
system. Possibly, define a web solution then get W3C to use this
iso standard - just so the W3C doesn't come up with another mechanism to
implement. </font>
<br>
<br><font size=2 face="Verdana">Scaling - we have implemented vertical
size and a horizontal scale factor (percentage of the vertical) - but we're
ok with going with any scheme.</font>
<br>
<br><font size=2 face="Verdana">Baseline Shift - we have implemented this
function on some of our system and we're ok with going with any scheme.</font>
<br>
<br><font size=2 face="Verdana">Other parameters such as Unicode Ranges
- we haven't done but it's on my list.</font>
<br>
<br><font size=2 face="Verdana">Language Tag - do we need a method of stating
that the language is Complex and that layout engines shouldn't try to use
other ComponentFonts during composition? Do we intend on allowing
Complex Scripts to span ComponentFonts? This could get messy.</font>
<br>
<br><font size=2 face="Verdana">Sizing - it would be helpful to be able
to specify a different font depending on the pointsize requested. This
would help with migration of legacy applications. </font>
<br>
<br><font size=2 face="Verdana">I apologize for having more questions than
solutions.</font>
<br>
<br><font size=2 face="Verdana">Best Regards,<b><br>
Jeff Engelman</b></font><font size=2 color=#2f2f2f face="Wingdings 2"><br>
' </font><font size=2 face="Verdana">720-663-3617</font><font size=2 color=#2f2f2f face="Wingdings"><br>
* </font><font size=2 face="Verdana">jeff.engelman@infoprint.com</font><font size=2 color=#2f2f2f face="Wingdings"><br>
Ä </font><font size=2 color=#808080 face="Verdana">Typography for the IBM
Corporation and InfoPrint Solutions Company, a Ricoh | IBM Joint Venture</font><font size=2 face="Verdana"><br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Ken Lunde <lunde@adobe.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: mpeg-OTspec@yahoogroups.com</font>
<p><font size=1 face="sans-serif">08/14/2009 03:07 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">mpeg-OTspec@yahoogroups.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[mpeg-OTspec] Toward a Composite Font
format specification</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3> </font>
<br>
<table align=center>
<tr>
<td>
<br>
<p><font size=3>All,<br>
<br>
In an effort to move the discussions forward, I would like to <br>
enumerate the primary functional tags, along with my initial ideas <br>
about what properties or attributes can be specified for each. I have <br>
already floated these ideas, but now that we're in basic agreement <br>
about some principles, I am able to condense this into a more readable
<br>
format.<br>
<br>
Here we go:<br>
<br>
Tag: <ComponentFont><br>
Attribute: Target (required; a unique name for the font)<br>
Attribute: ScaleFactor (optional; scaling factor, expressed as a <br>
percentage)<br>
Attribute: BaselineShift (optional; baseline shift, expressed as a <br>
percentage)<br>
<br>
Tag: <Language> (optional)<br>
Attribute: Target (required; an IETF language tag, as specified by <br>
RFC 4646)<br>
<br>
Tag: <Encoding> (optional)<br>
Attribute: Target (required; the Unicode ranges to be used in the <br>
Composite Font)<br>
Attribute: Original (optional; the encoding ranges in the Component <br>
Font, if different than the "Target" attribute)<br>
<br>
Of course, an appropriate XML namespace will need to be specified.<br>
<br>
In looking at the Composite Font feature of Adobe InDesign, there are <br>
two types of scaling factors, both of which are independent from one <br>
another, meaning that both can be specified. One is a uniform scaling,
<br>
applying to both the X- and Y-axis. The other is axis-independent <br>
scaling. While I am all for giving people enough rope to hang <br>
themselves, I consider this to be comparable to supplying the <br>
developer with razor-impregnated rope, and strongly suggest that the <br>
specification allows for only uniform scaling for the "ScaleFactor"
<br>
attribute for the <ComponentFont> tag.<br>
<br>
To everyone in this discussions, please think about additional <br>
attributes for these three functional tags.<br>
<br>
Regards...<br>
<br>
-- Ken</font><font size=1 color=white>.</font></table>
<br>
<br>
<BR>
_____________________________________________________________________________<BR>
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." _____________________________________________________________________________<BR>