Create an account on the HP Community to personalize your profile and ask a question
03-02-2016 11:12 AM
Pretty Self explanatory. When we use the Lato TTF font on a M401 Printer, we see corruption at the bottom of every letter. See image below.
When we use other printers, like a Laserjet P3015 Series Printer, it comes through fine:
Both printers are on latest firmware. WIndows 10 64-bit, latest drivers for each printer as supplied by the operating system.
Solved! Go to Solution.
03-03-2016 05:14 AM
I don't know the answer to your problem, just some comments, and suggestions for investigating where the problem may lie:
- The Lato font is not one of the standard fonts which are printer-resident on most (but not all) LaserJet printers.
- So in order to print using such a font, the printer driver will (in most cases) dynamically generate and download to the printer a printer-format soft font equivalent of the 'donor' TrueType font.
- The printer format will depend on which Page Description Language (PCL5, PCL6 (a.k.a PCL XL) or PostScript) is in use by the driver.
- Driver options will also determine whether the downloaded soft font is in bitmap format (one font per required size), or as a scalable encapsulated TrueType outline format font.
One thing to try:
- 'Print' your test document again to the 'good' printer, but select the 'print to file' option in the Print dialogue in order to capture the print job to a nominated .prn file.
- 'Send' the content of this file direct to the printer port of the 'bad' printer to see what happens.
- How to do this 'send' depends on how the printer is connected; e.g. for a network printer, use the lpr command within a Windows command-prompt session; or you could try the PRN File Print tool in the PCL Paraphernalia application, available via http://www.pclparaphernalia.eu.
- Then (for completeness) 'print' your test document again to the 'bad' printer, but again select the 'print to file' option in the Print dialogue in order to capture the print job to a (different) nominated .prn file.
- 'Send' the content of this file direct to the printer port of the 'good' printer to see what happens.
Assuming that you're using a PCL5 or PCL6 printer driver, you could also use the PRN File Analyse tool in the above application to attempt to find out what differences there are in how the fonts are rendered, in case this yields any clues.
You'd probably want to select the 'Interpret font header data' option in the PCL, or PCL XL, tab (as approprate) of the Set options dialogue associated with the tool, in order to discover basic details of the font format.
04-29-2017 07:32 AM
Strangely, the Lato font does work with the M401 printers for us (latest Printer Firmware with HP Universal Print PCL 6 v6.4.1).
It does however NOT work with the newer white HP models such als the M402 (b/w) and M477 (color) series printers!
If does of course print perfectly fine with other Xerox, Ricoh and Brother printers in the Office. It is just the M402 and M477 series which need this "send true type as bitmap" as workaround.... Switching to the Postscript driver does not help either.
HP, please fix this :smileyindifferent:
04-29-2017 08:20 AM
>> ... the Lato font does work with the M401 printers for us (latest Printer Firmware with HP Universal Print PCL 6 v6.4.1).
>> ... It does however NOT work with the newer white HP models such als the M402 (b/w) and M477 (color) series printers!
It's not clear from this whether the fault is with the printers themselves, or with the printer drivers (and the underlying library routines which these may call).
It would be interesting to see the results of the following:
- Print a (small, sanitised data) document to the LJ M401 device (using the driver you say is successful), but select the "print to file" option in the Print dialogue.
- "Send" the content of the resultant .prn file direct to the printer port of the LJ M401 to confirm that it prints OK.
- How to 'send' the content of such a file depends on how the device is connected, and on the operating system in use; for a network-connected device, from a Windows workstation, use the 'lpr' command within a command-prompt session. Note that it may be necessary to enable certain Windows 'features' to make the command available.
- For example, to 'send' the content of myfile.prn to a printer with the TCP/IP address 192.168.1.65:
lpr -S 192.168.1.65 -P any myfile.prn
- Then send the content of the same 'capture' file to the equivalent ports of the LJ M402 and LJ M477 printers; is the fault now apparent, or not?
Perhaps also repeat the above, but starting with a 'capture' file generated by the LJ M402 driver, and then again with that produced by the LJ M477 driver.
If you do have time to run the above tests, you could also send the test .prn file(s) to me (send to the support mailbox 'at' pclparaphernalia.eu), and I'll see if analysis of these yields any clues.