>>Only problem is that using the same code as paragraph symbol means you don't >>see the right charater while typing in LineDesign. Fixed in latest version of ProWesS, see http://www.progs.be/downloads/
>Yes it does but currently I don't think that ProForma fonts can contain >more than 255 characters Oh yes no problem. However, the conversion program only works properly for characters with a known name. Previously, you could get some pretty strange results, but the latest version should do something about that too (unknown character names are now mapped a bit more intelligently, no longer overwriting "known" characters). >Anyone knows if PFB2PFF takes into account the Family info and character >set? I converted Symbol for use with ProForma but although FontShow does >show all the characters when I try to preview it with either FontPreview or >by assinging it to one of the fonts in the Reader all I can see is a >Courier font. Same kind of problems. Everything works with character names. The names used for symbol fonts are not known by PROforma, so the characters can be mapped rather strangely. When rendering a character in PROforma, it first tried to render the character from the selected font. When the requested character does not exist in the current font, PROforma tries to get the character from the "builtin" font. The idea was that a simple, well hinted (with hints which are easy for the renderer to do right) and complete font would be created. We started doing this (which resulted in the "complete" font), but never finished the job. Designing fonts by hand, without a font editor is not an easy thing to do :-( Joachim
