Bug 85428 – Italic Helvetica font does not generate Adobe PS-compatible output

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 85428 - Italic Helvetica font does not generate Adobe PS-compatible output

Summary:	Italic Helvetica font does not generate Adobe PS-compatible output

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	gnumeric (Show other bugs)
Sub Component:
Version:	phoebe
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Havoc Pennington
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-03-02 10:13 EST by Jos Vos
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-03-23 12:13:32 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jos Vos 2003-03-02 10:13:23 EST

Description of problem:
When using all default settings in a Gnumeric spreadsheet, the PS output of a
spreadsheet does not print on a HP LJ4M+ (original Adobe PS Level 2) as soon as
you have used italic text in a cell, using the default Helvetica font. Normal
Helvetica and bold works fine.

Version-Release number of selected component (if applicable):
1.0.9-2 (RH 8.0), 1.0.12-3 (RH 8.1b5)

How reproducible:
Open new sheet, insert text in a cell, make text italic style, print sheet on PS
printer.

Additional info:
Ghostscript shows the page ok.

Comment 1 Jos Vos 2003-03-23 12:13:32 EST

Seems to be related to some (lack of) memory problem in our printer, when you
have loaded many custom PS fonts.  Now it seems to work fine again.

Note You need to log in before you can comment on or make changes to this bug.