Re: [tlug] Re: CJK Printing from Web Browsers in Debian 3.3.2

[Bart Mathias <mathias@example.com>]

Josh Glover wrote:
> On 13/11/06, Jim Breen <Jim.Breen@example.com> wrote:
>
> > On inspecting the Postscript, it appears that Firefox has done all the
> > text in Unicode, with no embebbed fonts, e.g.:
> >
> > 840 13697 moveto
> > (\123\060\214\060\157\060\306\060\271\060\310\060\140\060\121\060\002\060) 
> > unicodeshow
> >
> > My guess is this is the main difference between Mozilla Suite and
> > Firefox, and the reason Bart can't print from Firefox is that his
> > printer setup can't grok native Unicode in Postscript.
>
>
> You da man, Jim.
>
> With this hint, I think I know how to fix Bart's config files.
>
> Bart, you can do one of two things:
>
> 1. Wait for me to find time to help you.
> 2. Google for: firefox print postscript
>
> You basically need to find the about:config setting that will render
> to Postscript (level 2 is best, I think) before sending the job to the
> printer. That should fix your font problem, I think.

After some experimenting with things I found with that Google search, I
was successful in getting kanji etc. when I printed out a Google page.
The only problem was that everything was about 15 times normal size, and
even what stayed on the paper was kind of chopped up. I gave up for the
year.

I had a few minutes to spare today, so I tried a desperate measure:

bart@example.com:~$ cp .mozilla/default/x1qwmlrs.slt/prefs.js 
.mozilla-thunderbird/xmm1khnz.default/user.js

Presumably this overrules just about everything in Thunderbird's
prefs.js, and I have yet to see how it may hurt me, but I relaunched
Thunderbird thereafter and printed kanji and stuff!

I sort of understand that, but although I had not yet done the same for
Firefox, I printed out a Google search on Japanese web pages to use as
a "Before" sample, and that came out printed properly too!

Oh, well, whatever works.  I don't mind a bit of magic sometimes.

Bart Mathias