Hello, We discovered a situation in our testing phase that a PCL file doesn't transform correctly when using pcl___xj.fco from UFST 5.0, meaning another font is selected based on priority of font characteristics specified in the PCL file. The same file is transforming ok with ghostPCL 1.40 and pcl____i.fco from UFST 4.6. The PCL file contains only Font Spacing and Font Pitch. Apparently ghostPCL 1.53 with UFST 5.0 doesn't match the scoring to select Courier font (which should be selected) and it selects another font (i'm guessing it's Letter Gothic ?!). I have attached a capture of the afp output we obtain with ghostPCL 1.53 and UFST 5.0 (pcl___xj.fco). Thanks
Created attachment 5014 [details] 48615.pcl
Created attachment 5015 [details] capture.bmp
Could you please tell us when you'll have a resolution to this problem? We cannot exit from our CVT (component verification test) phase with this problem being unsolved. And one of our customers is waiting for the new code, which makes the situation more difficult. Thanks
We provide a sample configuration that uses pclp2_xj.fco and that seems to work (selects courier) in 1.53 and other releases. You must change pl/plulfont.c to select different fcos and change the font table in pl/plftable.c if you want to use something other than the default configuration.
Unfortunatelly InfoPrint is not allowed by the contract with Agfa/Monotype to use the extended font set: pclp2_xj.fco. That's the reason why we are still using pcl__xj.fco. Could you give us more details on how should we change pl/plftable.c in order to use something else than the default configuration? Thanks
Well you certainly should remove any font in the table that is not a candidate for selection. That would improve the probability the font selection machinery would select the correct font but not necessarily guarantee it. As I recall the order of table entries is also significant - we believe this is true on the HP as well, and I think the table order changed going from 45 to 80 fonts. Beyond that you would need a consultant or you could also use our URW 80 font collection in lieu of Monotype, for each I recommend you contact Miles Jones. Good luck.
Hello As we previously had the problem with pcl___xj.fco that courier font was not selected as default, we tried to use #define AGFA_SCREENFONTS and that solved our problem but rose another problem with Arial Bold being substituted with Courier. After a few investigations in plftable.c we found that in macro fontnames (agfascreenfontname, agfaname, urwname) the agfaname and agfascreenfontname are not following the same pattern. Meaning there is Courier on first position (agfascreenfontname) and CourierMT on second position(agfaname) and for Arial Bold is vice versa Arial-BoldMT(agfascreenfontname) on first position and Arial- Bold(agfaname). Shouldn't they be specified the same way for all fonts, like for example all font names without MT suffix occupy the first position and those with MT suffix occupy the second position in that macro? Thanks
Changing customer bugs that have been resolved more than a year ago to closed.