Creator issue with Apple Chancery
Dave Balderstone
dave.balderstone at producer.com
Wed Jun 4 09:22:11 CDT 2008
On 4-Jun-08, at 7:23 AM, Steve Mills wrote:
> On Jun 3, 2008, at 23:41:49, Dave Balderstone wrote:
>
>> Why not, Steve? You sound rather dismissive...
>
> Because it's not what I'd consider a professional grade font, and
> because of the way it was designed, which leads to the bug. It also
> is not an attractive typeface and is way overused where it has no
> business being used, but that's my personal opinion.
I don't disagree with your opinion, there are a number of fonts that
fit this category <cough comic sans <cough>.
>> What's the issue whereby Creator doesn't support that particular
>> font,
>
> Apple Chancery has swashed glyphs for almost every character, to be
> used in certain cases, but the "standard" glyph for each character
> is the swashed version, rather than the unswashed version (which,
> IMO, would've been the correct way to design the font). So unless
> the text engine has knowledge of this, it won't be able to allow the
> *font* to choose the correct glyphs. The text engine in OS X,
> naturally, knows how to deal with this. Creator's does not. An
> upcoming version of Creator will handle this case for OpenType
> fonts, but not for this particular Apple font.
That IS odd. I wasn't aware of it, thanks for the explanation.
>> and what other fonts are "known issues"?
>
>
> Apple Chancery is the only one I'm aware of with this problem.
More information about the Creator
mailing list