Re: Re: xprint probs
Don Spoon wrote:
> I am using:
> 1. Mozilla 1.4-4
> 2. xprt-xprintgorg 0.0.8.cvs2003050
> 3. CUPS version 1.1.19 final
>
> All worked well "out of the box" without any edits to the
> initscripts. Dunno what your problem might be, as I haven't had
> any problems getting xprint to work correctly with Mozilla in
> Debian here. I am tracking Testing/Unstable, and I think most of
> the above packages may be from Unstable.
> Maybe you could explain "work" and "doesn't work" in a bit more
> detail?? Besides printing everything in Courier font (mine
> doesn't) what else didn't it do before you made the edits? What
> were the edits you had to make in the /etc/init.d/xprint file to
> make it "work"??
Thanks for replying. Maybe we can fid out what is the matter here.
There are actually three modes, "doesn´t work", "work", and "work
properly".
"Doesn´t work" means not doing anything at all, refusing to start,
saying (in /var/log/syslog) that it cannot find the default font
"fixed".
"Work" means printing something through xphelloworld (in cursive
courier only), being visible in mozilla´s print dialog, and
printing web pages.
I got it that far by changing in /etc/init.d/xprint
echo "$fontpath") | \
tr "," "\n" | sort | uniq
to
echo "$fontpath") | \
tr "," "\n" | sort -r | uniq
(The idea here is to put the misc fonts, and therefore 'fixed', at
the top of the list, which this in my case does. I have no idea
why I need this).
However, "work" in my case also means that the default print font
is courier (I retract my earlier statement that it *only* prints
courier, but it still *mostly* prints courier):
- pages which do not specify a <font face> get printed in courier
(in other words, most pages).
- pages which specify <font face=sans-serif> get printed in
Helvetica.
- pages which specify <font face=serif> get printed in courier.
- pages which specify <font face=monospace> get printed in
courier.
- pages which specify <font face=Times> get printed in a Times
New Roman-like font.
- pages which specify a specifically named font, i.e.
<font face="Bitstream Vera Sans Mono">, get printed in courier.
So xprt does not seem to care about the preferences in
/etc/fonts/fonts.conf.
"Work properly" means: printing the same font on paper as is used
for display, in all cases. Well anyway I thought that was the
whole point of xprt. I´d very much like to know if it works
properly in your case.. but by now I begin to suspect that xprt is
not fontconfig-aware, so this may not be possible. If you say it
works out of the box, do you mean it works "properly" out of the box?
A good test page is
http://xprint.mozdev.org/bugs/attachment.cgi?id=870&action=view
It has 'Arial', 'Helvetica', and 'sans-serif' which look different
on the screen but are printed exactly the same. For testing, I
saved the page and added <font face=..> statements.
I am also using testing/unstable, with:
mozilla-browser-snapshot 0.0.20030618.15.trunk-1
lprng 3.8.20-4
xprt-xprintorg 0.0.8.cvs20030508-5
Regards, Jan
Reply to: