Bug 6237

Summary:	&#xFB01 (fi ligature) produces a "sharp"?
Product:	Fop - Now in Jira	Reporter:	Micah Cowan <micah>
Component:	pdf	Assignee:	fop-dev
Status:	CLOSED FIXED
Severity:	normal
Priority:	P3
Version:	all
Target Milestone:	---
Hardware:	PC
OS:	Linux

Description Micah Cowan 2002-02-05 06:22:22 UTC

Unicode character mappings don't seem to actually map to the appropriate
characters in the PDF output.  I'd really like ligatures and circled alphanums,
but can't get 'em 'cause FOP apparently mistranslates some of the codes.  The
summary is one example.

Comment 1 keiron 2002-02-07 11:27:16 UTC

The mappings depend on the font. If the font does not contain the character 
then it will output a #.

Comment 2 Micah Cowan 2002-02-10 02:48:06 UTC

The font, Times New Roman, definitely contains the fi ligature, as I have other
documents using the same font, but produced via other means (pdftex, for
example).  All docs use the base fonts from Adobe - no embedded fonts.

Comment 3 J.Pietschmann 2002-06-20 13:23:11 UTC

The problem here appears to be that FOP sets up a Times-Roman font with
a platform specific encoding. In the most likely case, which is Win-Ansi,
the fi-ligature Unicode character can not be mapped.
A work around is to use a Unicode user font with a glyph for the ligature.

Comment 4 Pascal Sancho 2007-10-23 07:04:22 UTC

This works for me in latest Trunk (rev 584703), and probably in FOP 0.94

Comment 5 Glenn Adams 2012-04-01 06:37:55 UTC

batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed