You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2010/01/08 16:52:28 UTC
DO NOT REPLY [Bug 48512] New: Metrics needed with Type 1 fonts to
have accentuated chars
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
Summary: Metrics needed with Type 1 fonts to have accentuated
chars
Product: Fop
Version: 1.0dev
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: regression
Priority: P2
Component: fonts
AssignedTo: fop-dev@xmlgraphics.apache.org
ReportedBy: pascal.sancho@takoma.fr
Created an attachment (id=24821)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24821)
Conf file used to embed fonts
FOP: trunk r897221
Used font: any type 1 (tested with Sansa, Vectora, Helvvetica Neue)
If I don't provide xml metric file, I get a [Warn] in log file for each
accentuated char.
[WARN] FOUserAgent - Glyph "é" (0xe9, eacute) not available in font "xxx".
[WARN] FOUserAgent - Glyph "à" (0xe0, agrave) not available in font "xxx".
[WARN] FOUserAgent - Glyph "ô" (0xf4, ocircumflex) not available in font "xxx".
Note that Fop 0.95 behaves as expected with or without the metric files.
I can provide fonts only for testing and out off list (due to license
restrictions).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
Jeremias Maerki <je...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #6 from Jeremias Maerki <je...@apache.org> 2010-02-10 07:38:54 UTC ---
I've committed my patch. I got a bug report today which indicated problems with
character widths for certain glyphs in PostScript output (PSRenderer only).
Turns out it's the same bug.
http://svn.apache.org/viewvc?rev=908543&view=rev
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #4 from Jeremias Maerki <je...@apache.org> 2010-01-12 01:50:44 UTC ---
Created an attachment (id=24828)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24828)
Possible fix
Some Type1 fonts appear to specify a default encoding that doesn't match the
actual encoding of the glyphs in the AFM file. Add to that the fact that we're
currently mapping "AdobeStandardEncoding" to the "StandardEncoding" and
suddenly umlauts don't work with some Type 1 fonts. I've attached a patch the
will probably fix this but I haven't got time to properly test with all fonts I
have so I won't commit this just now.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #3 from Pascal Sancho <pa...@takoma.fr> 2010-01-12 00:42:29 UTC ---
(In reply to comment #2)
> I don't have the fonts that you mention, but with the Type 1 fonts I regularly
> test with, these glyphs work just fine for me with the latest FOP Trunk. Are
> your Type 1 fonts accompanied with AFM font files? But it should even work if
> there's only a PFM.
AFM font files are present.
I built FOP under JDK1.6.0_06, Win XP machine.
I'll send you OFF list if that can help to investigate.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #2 from Jeremias Maerki <je...@apache.org> 2010-01-11 13:36:13 UTC ---
I don't have the fonts that you mention, but with the Type 1 fonts I regularly
test with, these glyphs work just fine for me with the latest FOP Trunk. Are
your Type 1 fonts accompanied with AFM font files? But it should even work if
there's only a PFM.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #7 from Jeremias Maerki <je...@apache.org> 2010-02-16 09:37:48 UTC ---
My last change was not enough. Had to take a different approach:
http://svn.apache.org/viewvc?rev=910445&view=rev
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #1 from Pascal Sancho <pa...@takoma.fr> 2010-01-08 07:56:27 UTC ---
In resulting PDF, 'warned' chars are replaced with '#' (witch is coherent with
log...)
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
--- Comment #5 from Pascal Sancho <pa...@takoma.fr> 2010-01-12 07:48:35 UTC ---
(In reply to comment #4)
> Created an attachment (id=24828)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24828) [details]
> Possible fix
>
> Some Type1 fonts appear to specify a default encoding that doesn't match the
> actual encoding of the glyphs in the AFM file. Add to that the fact that we're
> currently mapping "AdobeStandardEncoding" to the "StandardEncoding" and
> suddenly umlauts don't work with some Type 1 fonts. I've attached a patch the
> will probably fix this but I haven't got time to properly test with all fonts I
> have so I won't commit this just now.
Thx Jeremias, the patch makes me happy with my fonts.
I can make further tests if you want. Just say me witch fonts to check.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 48512] Metrics needed with Type 1 fonts to have
accentuated chars
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=48512
Glenn Adams <gl...@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #8 from Glenn Adams <gl...@skynav.com> 2012-04-01 06:51:07 UTC ---
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.