Closed Bug 103203 Opened 24 years ago Closed 22 years ago

Problems printing FrontPage quote character

Categories

(Core :: Printing: Output, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: grantbow, Assigned: dcone)

Details

Attachments

(2 files)

I intend to create a test case later for this unless someone beats me to it. " characters print fine. When a real quote character comes along, there is a box and the next few words are omitted. This makes printouts with Mozilla useless since it's missing data.
This is reproducable in both quirks and standard mode. My example comes from a FrontPage created file I cut down to size. It's actually not happening with real quotes, just the ~T that shows up in my VIM editor. Konqueror printed it OK and due to the high likelihood of encountering similar files I think this is something that is worth fixing.
Severity: major → critical
Summary: Problems printing real quote characters → Problems printing FrontPage quote character
This is a dupe of bug#92189. FYI--overview: Mozilla corrects FrontPage's "smart quotes" for display, but doesn't correct them for printing. Mozilla's behavior is technically correct because it's FrontPage's problem (broken font encoding), but I think the consensus so far is that we're gonna work around this rather than make MS fix their fonts.
Ah, yeah, I see some of the issues. However the difference between your 92189 and the real problem I was trying to describe is data loss during printing. It's not just the character itself, but several words after the bad quote thing that do not show up. So I see what you mean by duplicate and I realize it's Microsoft being stupid, but this bug will bite users on the ass when they try to print something that looks fine on the screen and get ****. For me this makes printing with Mozilla unreliable and unusable due to data loss. Just my $.02, thanks for looking into this.
Sorry, I'm a fellow volunteer with no real authority and I clearly didn't examine your bug closely enough. Looks like this really is a different bug, so have at it, Mozilla crew!
Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: critical → normal
Target Milestone: --- → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Can not see this bug on recently trunk and release 1.0.
dup of bug 68373?
Sorry, I meant dup of bug 67338.
retargeting
Target Milestone: mozilla1.0.1 → Future
I can't reproduce this problem, and it's not visible in the postscript sample from comment #8. I have no doubt this was a valid issue when reported but it doesn't seem to be any more. Resolving WFM.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: