Phoebus, Sounds normal, when the conversion program doesn't recognize the font name, the character is placed at an unused character, which can be anything. So please do send one of these fonts over (preferably with as little encoding as possible, or else a version you can convert with pfb2pff).
We might be able to fix this quite swiftly then :-) Joachim ----- Original Message ----- From: "Phoebus Dokos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, October 21, 2001 9:45 PM Subject: Re: [ql-users] ProWesS Fonts > At 01:27 μμ 21/10/2001 +0200, you wrote: > > > 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. > > The PS name for Euro is..... Euro :-) and the Unicode mapping is 20ac. > > >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 > > > I did some further research after receiving your mail... and I got > interesting results. > > Indeed something MUST have changed in the PS encoding since 1995 because > after I installed the Unicode update for Fontographer 3.5, all fonts that > would work after being saved via Fontographer 4.1 or TypeCreator that WERE > unicode, > DO work with ProWesS. And they are VERY fast too... (Especially after > setting QPC to 128 Megs of Ram (hehe) and ProWesS font cache to 132768 (and > higher... believe it or not... IT works ;-)) So fast that I don't even had > to make them default as I have with my Helvetica Regular Greek Font that I > use as my system font. However.... the encoding.... My oh My!... Even the > regular english characters are shot to hell :-)... Instead of A for example > I get the Ptas symbol or instead of B some obscure Thai character :-D > > Should I send you a font so you could examine it quickly? Or should I just > stick with the (up to 255 ASCII) old encoding and we will deal with Unicode > some other time???? > > > Phoebus > >
