131088 - [ps] japanese printing ignores defined sans serif font and prints in serif latin

Status: RESOLVED EXPIRED

(MailNews Core :: Printing, defect)

Description

[u32858]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031115

japanese printing ignores defined sans serif font and prints in serif latin

Reproducible: Always
Steps to Reproduce:
1.get a japanese email
2.try and print it
3.see the fonts come out in japanese + latin serif font

Actual Results:  see the fonts come out in japanese + latin serif font

Expected Results:  Should be the same font as i defined for japanese, as
displayed fine in the messenger window. Or a Sans serif equivelent as that was
my specification for "Message display format" in prefs.

The font is quite large as well, bigger than my latin only emails, even though
all charsets are set to 16pt fonts

Comment 1

[Roland Mainz]

Reporter:
- Which print module do you use (printer named "PostScript/default" etc. are
PostScript module, printer names with an '@'-char in the middle are usually
Xprint printers) ?
- Can you provide a screenshot from the resulting PostScript job, please ?

Comment 2

[u32858]

hi Roland,

I was using "PostScript/default" to print via cups, it worked ok in other programs.

JG

Comment 3

[Roland Mainz]

[e-mail] wrote:
> I was using "PostScript/default" to print via cups, it worked ok in other 
> programs.

Thanks!

Adding "[ps]" to the summary (as indicator for PostScript-module bugs) ...

Comment 4

[simon annear]

Reporter

Are you able to reproduce with a newer version of mozilla - if so, can you
please attach as a sample email

Thanks

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.