Query on printer drivers

  • Thread starter Thread starter psankarv
  • Start date Start date
P

psankarv

Hi

I have a query.
For certain applications in Windows XP, when fired to printer , some
characters are getting wrongly scaled. But the prn seems to be proper.
The problem is found only when directly fired to the printer..

On debugging it could be found that the Wrong Character Scale
obtained is due to the incorrect value obtained for pdev-
cgs.FontXForm.eM11 when directly fired to printer...The value should
ideally be 0.018880861 for eM11 and eM22 which is obtained when the
application is print to file.
But on directly printing to the printer the value of eM11 is getting
changed to 0.059503075 and eM22 is same as 0.018880861 ..For scaling
calculation , the xscale (Horizontal Character Scale) is obtained by
dividing eM11 by eM22..As the value obtained for eM11 is incorrect
when fired to printer, the horizontal scale of the character obtained
is wrong..

The transforms, including pdev->cgs.FontXForm.eM11, is obtained by
using the function XFORMOBJ_iGetXForm() ..

Do u have any suggestion to resolve this problem?
 
Hi

I have a query.
For certain applications in Windows XP, when fired  to printer , some
characters are getting wrongly scaled. But the prn seems to be proper.
The problem is found only when directly  fired to the printer..

On debugging it could be found that the Wrong Character Scale
obtained  is due to the incorrect value obtained for pdev->cgs.FontXForm..eM11 when directly fired to printer...The value should

ideally be 0.018880861 for eM11 and eM22 which is obtained when the
application is print to file.
But on directly printing to the printer the value of eM11 is getting
changed to 0.059503075 and eM22 is same as 0.018880861 ..For scaling
calculation , the xscale (Horizontal Character Scale) is obtained by
dividing eM11 by eM22..As the value obtained for  eM11 is incorrect
when fired to printer, the horizontal scale of the character obtained
is wrong..

 The transforms, including pdev->cgs.FontXForm.eM11, is obtained by
using the function XFORMOBJ_iGetXForm() ..

Do u have any suggestion to resolve this problem?

No solution! This will always be a problem since manufacturers can /
will decide what to include / remove from the printer. Printing
directly to the printer, not using th Windows Print Spooler system,
will / can cause different results. Most new printers are "Windows
only" printers since the printer does not have the electronic controls
to prepare the "printed" page. You need a module in WIndows, hence
the term used is "Host only" printing.
 
Back
Top