From: [email protected]

Package: xprt-xprintorg
Version: 0.0.9.final.001-2
Severity: normal

It appears that Xprt is using only the URWGothicL font when printing
to a PostScript printer. Specifically, my setup is:

- Mozilla 1.7.2-2
- HP PSC2110 printer connected via CUPS/ijs

I configured Mozilla to use the "Arial" font by default. If I create
a document test.html containing nothing other than:

hello

view it in Mozilla and then print it into a file, I get a PostScript
file that ends with:

$ tail -7 mozilla.ps
/URWGothicL-Book_iso8859-1 100 f Tf
500 598 moveto
[ /h /e /l /l /o ]{glyphshow}fa gr gr sp
%%PageTrailer
%%Trailer
%%Pages: 1
%%EOF

Indeed, Xprt seems to be using the URWGothicL font no matter what font
I choose in Mozilla.

The fontpath of the Xprt server is as follows:

$ DISPLAY=:64 xset q|grep PRINTER
PRINTER:/usr/share/Xprint/xserver/C/print//models/PS2PDFspooldir-GS//fonts/,PRINTER:/usr/share/Xprint/xserver/C/print//models/PSspooldir//fonts/,PRINTER:/usr/share/Xprint/xserver/C/print//models/PSdefault//fonts/,/usr/X11R6/lib/X11/fonts/Type1,/usr/
lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/TrueType,/usr/X11R6/lib/X11/fonts/TrueType/larabie-deco,/usr/X11R6/lib/X11/fonts/TrueType/larabie-straight,/usr/X11R6/lib/X11/fonts/TrueType/larabie-uncommon,/usr/share/fonts/truetype,/var/lib/defoma/x-
ttcidfont-conf.d/dirs/TrueType,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/100dpi/,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/misc

which looks OK to me (the TrueType fonts are in /usr/share/fonts/truetype).

The URWGothicL font happens to be the first font listed in /usr/X11R6/lib/X11/fonts/Type1/fonts.alias, but I'm not sure whether
that's the (only) reason it ends up being used in the PostScript file.

This behavior appears to be unaffected by the locale setting (I tried
both with POSIX C and de_CH locale with no change).

Is there any way to solicit debug output from Xprt so I can see how
it's doing the font-mapping and why it's choosing URWGothicL?

Thanks,

--david

-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-rc2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages xprt-xprintorg depends on:
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li ii libxaw7 4.3.0.dfsg.1-6 X Athena widget set library
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte ii libxmu6 4.3.0.dfsg.1-6 X Window System miscellaneous util ii libxp6 4.3.0.dfsg.1-6 X Window System printing extension ii libxt6 4.3.0.dfsg.1-6 X Toolkit Intrinsics
ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m ii xprt-common 0.0.9.final.001-1 Xprint - the X11 print system (con

-- no debconf information


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

view it in Mozilla and then print it into a file, I get a
PostScript file that ends with:

$ tail -7 mozilla.ps
/URWGothicL-Book_iso8859-1 100 f Tf

Confirmed. Sigh. And I'd had it working so nicely...

I blame the new mozilla versions. Perhaps they have forgotten to compile
with xft2 support. See discussion on bug #235592.

Is there any way to solicit debug output from Xprt so I can
see how it's doing the font-mapping and why it's choosing URWGothicL?

"/etc/init.d/xprint diag" gives some diagnostics, but not really what you're asking for.

Drew


DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you.




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

Hi Drew,

On Sun, 15 Aug 2004 19:49:14 +1000, Parsons, Drew
<[email protected]> wrote:

view it in Mozilla and then print it into a file, I get a
PostScript file that ends with:

$ tail -7 mozilla.ps
/URWGothicL-Book_iso8859-1 100 f Tf

Confirmed. Sigh. And I'd had it working so nicely...

I blame the new mozilla versions. Perhaps they have forgotten to compile
with xft2 support. See discussion on bug #235592.

Do you know which version of mozilla/firefox had this working? I
looked for a bug-report regarding this on the mozilla package page but
couldn't find it. Did I miss it?

Is there any way to solicit debug output from Xprt so I can
see how it's doing the font-mapping and why it's choosing URWGothicL?

"/etc/init.d/xprint diag" gives some diagnostics, but not really what you're asking for.

Ah, that's useful, nevertheless.

Thanks,

--david


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

-----Original Message-----
From: david mosberger [mailto:[email protected]]
Sent: Tuesday, 17 August 2004 2:15 AM

I blame the new mozilla versions. Perhaps they have forgotten to
compile with xft2 support. See discussion on bug #235592.

Do you know which version of mozilla/firefox had this
working? I looked for a bug-report regarding this on the
mozilla package page but couldn't find it. Did I miss it?

I may be premature in blaming firefox. I find that Xprint 009 (not 009.001) prints with correct spacing, although it still uses sans-serif font instead
of serif.

But the preceding version of firefox that I believe to have been working normally would have been v0.8 (debian 0.8-12).

Note that Jan Willem Stumpel has suggested a workaround for mozilla/firefox: use userContent-example.css in the chrome directory in ~/.mozilla/default, renaming it to userContent.css. In it, place:

@media print {
body {
color: black;
font-family: 'Times New Roman', times, serif;
font-size: 12pt;
}
tt, pre {
font-family: 'Courier New', courier, typewriter, monospace;
}
:link, :visited {
color: black !important;
text-decoration: underline !important;
}
}

This makes serif get printed as serif, when fonts are not explicitly
specified in the web page (we don't experience the problem on pages where
fonts are specified).

Drew


DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you.




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)