Issue 14629

Summary:

Type 1 fonts cannot be used.

Product:

gsl

Reporter:

behrends <behrends>

Component:

code

Assignee:

philipp.lohmann

Status:

CLOSED DUPLICATE

QA Contact:

issues@gsl <issues>

Severity:

Trivial

Priority:

CC:

issues

Version:

OOo 1.1 Beta2

Target Milestone:

OOo 1.1 RC

Hardware:

OS:

Linux, all

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
.tgz with .pfb, .afm, and fonts.dir.	none

Description behrends 2003-05-19 17:21:12 UTC

Spadmin scans directories with type 1 fonts, but does not make them available
for selection. I tried both .pfb and .pfa fonts, and neither works.

When in the font path, Writer does not list .pfb fonts, but Draw does, though
they are not antialiased. Draw fails to embed them in printed output. Writer
lists .pfa fonts, though the preview in the dropdown menu is wrong.

Generally, Type 1 fonts seem to be entirely unusable with Beta2. The same fonts
work fine in Beta1.

Comment 1 christof.pintaske 2003-05-20 11:32:59 UTC

please provide a sample pfa or pfb file and the according afm file as
bugdoc.

Comment 2 behrends 2003-05-20 11:41:49 UTC

Created attachment 6295 [details]
.tgz with .pfb, .afm, and fonts.dir.

Comment 3 christof.pintaske 2003-05-20 17:48:02 UTC

cp->pl: please have a look. the font seems to be valid (at least
pfbtopfa creates a pfa font that looks ok to me). spadmin does not see
the font and copying the font to share/fonts/truetype has no effect as
well.

Comment 4 philipp.lohmann 2003-05-20 18:09:17 UTC

The reason for this misbehaviour was fixed with issue 12936 : at some
point type1 fonts would not be recognized anymore if their
corresponding .afm files where in the same directory and not in a afm/
subdirectory.

*** This issue has been marked as a duplicate of 12936 ***

Comment 5 philipp.lohmann 2003-05-20 18:10:25 UTC

closing duplicate