Japanese characters printed with extra spaces

RESOLVED INCOMPLETE

Status

()

Core
Printing: Output
RESOLVED INCOMPLETE
11 years ago
7 years ago

People

(Reporter: Beata, Unassigned)

Tracking

1.8 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [closeme 2011-03-15], URL)

Attachments

(1 attachment, 1 obsolete attachment)

179.55 KB, application/octet-stream
Details
(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061220 Mandriva/1.5.0.9-1mdv2007.0 (2007.0) Firefox/1.5.0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061220 Mandriva/1.5.0.9-1mdv2007.0 (2007.0) Firefox/1.5.0.9

1) When I display page everything is displayed correctly
2) When I look at print preview everything is displayed correctly
3) When I print or print into file extra spaces are introduced.

For details see attached ps file

Reproducible: Always

Steps to Reproduce:
1) When I print or print into file
webpage with certain japanese characters 
extra spaces are introduced.

http://wiki.sixtease.net/nejap/doku.php?id=minule_lekce

This does not show on screen or in print preview
also in konqueror it prints correctly ... 
(therefore it seems to be browser thing)
(Reporter)

Comment 1

11 years ago
Created attachment 258777 [details]
Postscript file showing the defect
(Reporter)

Updated

11 years ago
Attachment #258777 - Attachment is obsolete: true
(Reporter)

Comment 2

11 years ago
Created attachment 258778 [details]
Postscript file showing the defect
Assignee: nobody → printing
Component: OS Integration → Printing
Product: Firefox → Core
QA Contact: os.integration
Version: unspecified → 1.8 Branch
Assignee: printing → nobody
QA Contact: printing

Comment 3

7 years ago
do you see this issue still with version 3.6 or 4.0 beta?
Whiteboard: [closeme 2011-03-15]
No response to needed information. -> incomplete report
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.