--- In PageStreamSupport%40yahoogroups.com">PageStreamSupport
yahoogroups.com, Don Cox <doncox...> wrote:
>
> On 16/09/07, PageStream Support wrote:
>
>
> >>
> > I took a quick look through the unicode character set and did not find
>; > any such precomposed glyph. It would have been easy to do this as a
> > ligature. Otherwise, using character spacing or kerning is the only
>; > way to do this in PageStream.
> >
> > I suppose a application specific unicode value could be used. It would
> > not be too hard to display this in PageStream by using existing
> > characters.
>
> It would be easy to add a custom character to a typeface using
> Typesmith.
>
> Regards
> --
> Don Cox
> doncox...
>
Not so simple as it sounds. While it's easy enough to insert a custom
character, it won't be a unicode font anymore as Typesmith can't generate
characters higher than ascii 255.
You can certainly create a custom font, but don't pretend it's the
equivalent of the unicode font you're trying "fix", because it won't
be. Better to make an entirely new font that you will use for a
specific purpose -- that is, IF you are trying to do it with Typesmith.
And it's not even so simple to create a custom font. I don't recall now
exactly how I accomplished it without going through my documentation, but
I did create a custom bar code for use with Pagestream (actually I used it
with QuarkXpress also) and I had to "borrow" a pre-existing font
with custom encoding and work from that framework. There's something
required in a custom encoded font that Typesmith is not implementing when
attempting to create a custom encoded font from scratch. Perhaps I could
figure it out yet with a bit more work.
Anyhow, I succeeded, and the font works well. I have intentions of turning
that work over to Deron to incorporate in Pagestream, but so far I can't
seem to get free enough of other demands to wrap it up.
Typesmith is a great program, and it's infortunate that the developers
have evaporated somewhere into the electronic ether.
-Ernest
.
