Issue 17586

Summary:

Problem with Zapf Dingbats

Product:

Reporter:

rblackeagle <rbe>

Component:

Assignee:

ulf.stroehler

Status:

CLOSED IRREPRODUCIBLE

QA Contact:

issues@ui <issues>

Severity:

Trivial

Priority:

CC:

issues

Version:

OOo 1.1 RC2

Target Milestone:

---

Hardware:

OS:

Linux, all

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
ZapfDingbats font file	none

Description rblackeagle 2003-07-29 20:25:49 UTC

When printing a document with the Zapf Dingbats graphics inserted, the graphic
appears correctly on the screen,but the print is two lines up (try "Insert >
Special Characters).  I don't know if this is an OOo defect or a defect in the
coding of Zapf Chancery.  I have to use one of the pencil graphics to print out
a star graphic -- weird.

Will attach a copy of the font.

Comment 1 rblackeagle 2003-07-29 20:28:23 UTC

Created attachment 8125 [details]
ZapfDingbats font file

Comment 2 stefan.baltzer 2003-07-30 15:42:35 UTC

Reassigned to Ulf.

Comment 3 rblackeagle 2003-08-17 04:13:55 UTC

Unfortunately, this is still in RC3.  I am almost certain the problem
is with the Zaph Dingbats font and not OOo.

Comment 4 con.hennessy 2003-10-30 20:13:11 UTC

Hi, 
	Is this still present in 1.1.0 ? 
Thanks

Comment 5 rblackeagle 2003-10-31 11:07:30 UTC

After etensive conversations with MAC, Solaris, Windows, Uinix, Linux 
and some other strange OS's, I conclclude that the Zapf Chancery is 
no good.  It ides not follow stadard coding practices.  If they want 
to be taken seriously, they need to code seriosly.

Robert Black Eagle

Comment 6 rblackeagle 2004-03-05 17:28:01 UTC

This apparently was not a Zapf Dingbats problem as in 1.1.1rc it works as
expected.  The problem no longer appears.

Comment 7 flibby05 2004-03-21 11:46:46 UTC

ok, closing for now, please reopen, if you can reprocude with a recent stable build.

Comment 8 flibby05 2004-03-21 11:47:01 UTC

Comment 9 rblackeagle 2004-04-24 20:03:15 UTC

Just a follow-up.  Works perfectly in 1.1.2rc. I will not bother checking again
unless it crops up by accident (that is my normal usage -- not actually by
accident).

Thanks to the developers and volunteers for fixing this.