> That would work great if Proforma could actually render fonts that were > converted from a unicode original.... As I told you (unless there is > something wrong with my pfb2pff an older version maybe?) Proforma hangs > when converting ANY Unicode font. It only works with older (emptier....) > fonts/encodings. For example try to convert the standard Windows Arial..... > It converts fine, adds fine but try to use it..... The ProWesS app HANGS on > startup... Tried every combination... even tried to make it the resident > font in ProWesS.. no luck... Apparently there IS a problem...
There are some problems. In short I don't know the Postscript name for the euro symbol or the convention they use to indicate unicode characters. It would not be too difficult to convert pfb2pff to include these mappings. Secondly, I have some assumptions that the Adobe Type 1 format has been extended without this being documented (probably some cases of extra encodings used inside the font, but possibly also with multiple glyphs for rendering at different sizes etc. I know these extensions were "in the pipeline" and that I too could not convert every font I encountered a few years back. Please note that all this is based on the book "Adobe Type 1 Font Format" by Adobe, dating back to 1990. Joachim
