Am Dienstag, 5. Juni 2001 09:19 schrieb Giuseppe Ghibo':
> Giuseppe Ghibo' wrote:
> > Thanks a lot. Hmmm, it seems bitmap vector tracing, which could
> > have problems of precisions. If I remember right, METAPOST can
> > extract outlines in type3 too, so the problem would be to
> > convert type3 outlines to type1 and add the hints manually. MetaFOG
> > from
>
> of course Type3 fonts are not "outlines", and the Type3 -> Type1
> conversion is still the key for a more precise conversion, but does
> exists a such generic tool?
Sorry, but you are wrong! Type3 fonts can be vector outlines and/or
bitmaps. In opposite to Type1 fonts that cannot not have some postscript
commands, glyphs for Type3 fonts can contain full postscript programs. For
example with a Type3 font you can create colorful pictures for each glyph.
The other difference between Type1 and Type3 is only a historic one: The
format of Type3 was published, the one for Type1 closed and only available
for Adobe and its fonts ...
But back to the topic:
Metapost can produce one postscript file per glyph. And since Type3 fonts
can contain normal postscript commands -- voila, there is your postscript
font. But this isn't as easy at it may look, cause Metapost isn't able to
process most of the metafont fonts _and_ the result (if there is one) needs
a lot of postprocessing ...
Uwe
--
mailto:[EMAIL PROTECTED]
http://rcswww.urz.tu-dresden.de/~koloska/
-- --
right now the web page is in german only
but this will change as time goes by ;-)
