[
https://issues.apache.org/jira/browse/FOP-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner resolved FOP-2559.
Resolution: Duplicate
Dup of FOP-2557
> [PATCH] Kerning doesn't work for OTF/CFF f
[
https://issues.apache.org/jira/browse/FOP-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chunlinyao updated FOP-2559:
Labels: patch (was: )
> [PATCH] Kerning doesn't work for OTF/CFF f
[
https://issues.apache.org/jira/browse/FOP-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-2559:
---
Summary: [PATCH] Kerning doesn't work for OTF/CFF font (was: Kerning
doesn't work for OTF/CFF font
chunlinyao created FOP-2559:
---
Summary: Kerning doesn't work for OTF/CFF font
Key: FOP-2559
URL: https://issues.apache.org/jira/browse/FOP-2559
Project: FOP
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/FOP-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chunlinyao updated FOP-2559:
Attachment: patch.txt
I Enabled advanced features for OTF/CFF by the attached patch. The kerning
using GPOS
, advanced
features should be enabled.
> Kerning doesn't work for OTF/CFF font
> -
>
> Key: FOP-2559
> URL: https://issues.apache.org/jira/browse/FOP-2559
> Project: FOP
> Issue Type: Bug
bchr.README
bchr.pfb
bchr.afm
Support for Font Kerning is Broken
--
Key: FOP-1777
URL: https://issues.apache.org/jira/browse/FOP-1777
Project: FOP
Issue Type
[
https://issues.apache.org/jira/browse/FOP-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640553#comment-14640553
]
Thanasis Giannimaras commented on FOP-1777:
---
Fix for handling kerning
=r1623885.
Kerning is no longer applied
Key: FOP-2213
URL: https://issues.apache.org/jira/browse/FOP-2213
Project: Fop
Issue Type: Bug
Components: font/unqualified
Affects Versions: 1.1, trunk
[
https://issues.apache.org/jira/browse/FOP-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Tošovský updated FOP-2371:
--
Attachment: kern.pdf
kern.fo
Sample file.
Kerning is applied only to certain
a different logic which can be demonstrated on
dotlessi glyph used for small caped variant of 'i' character. While some
engines renders it corectly as dotless i, others incorrectly as dotted i.
If missing glyph names is the issue, I am curious why the kerning is not
disabled completely. Now
features are enabled in your
testing. If they are, then you need to look at the font's GPOS tables
associated with the 'kern' feature to determine if the font defines contextual
kerning. If the are not enabled, then you need to look at the font's 'kern'
table to determine if kerning entries
but no 'kern' feature in the GPOS table, then
the kern table should be used as a fallback, as indicated at
http://www.microsoft.com/typography/otspec/recom.htm:
When a kern table and GPOS table are both present in a font, and an OFF layout
engine is requested to apply kerning to a run of text
.
Kerning is no longer applied
Key: FOP-2213
URL: https://issues.apache.org/jira/browse/FOP-2213
Project: Fop
Issue Type: Bug
Components: fonts
Affects Versions: 1.1, trunk
[
https://issues.apache.org/jira/browse/FOP-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams reassigned FOP-2213:
Assignee: Glenn Adams
Kerning is no longer applied
Vincent Hennebert created FOP-2213:
--
Summary: Kerning is no longer applied
Key: FOP-2213
URL: https://issues.apache.org/jira/browse/FOP-2213
Project: Fop
Issue Type: Bug
kerning.fo
Sample FO file, fop.xconf (referring to the DejaVu LGC Serif font available in
test/resources/fonts/ttf).
Correct output produced by FOP 1.0.
Incorrect output produced by FOP 1.1.
Kerning is no longer applied
Key
:
--
In FOP 1.1 we get the right (i.e., the same as in 1.0) kerning with -nocs (CS
are enabled by default). If CS are enabled then glyph positioning uses the GPOS
tables if they are available. There is no guarantee that the positioning will
match the old kerning although one would expect it to be so
as in 1.0) kerning with -nocs (CS
are enabled by default). If CS are enabled then glyph positioning uses the GPOS
tables if they are available. There is no guarantee that the positioning will
match the old kerning although one would expect it to be so (at least similar).
This needs further
[
https://issues.apache.org/jira/browse/FOP-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bernardo updated FOP-2213:
---
Attachment: kerning-v2_1.1-cs.pdf
kerning-v2_1.1-nocs.pdf
kerning-v2.fo
gpa = font.performPositioning ( mcs, script, language );
} else if ( font.hasKerning() ) {
// handle standard (non-GPOS) kerning
[
https://issues.apache.org/jira/browse/FOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luis Bernardo closed FOP-2178.
--
the issue has been fixed. thanks.
incomplete kerning when complex script features
Glenn Adams created FOP-2178:
Summary: incomplete kerning when complex script features are
enabled
Key: FOP-2178
URL: https://issues.apache.org/jira/browse/FOP-2178
Project: Fop
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glenn Adams updated FOP-2178:
-
Attachment: kerningissue.pdf
kerningissue.fo.xml
incomplete kerning when complex
incomplete kerning when complex script features are enabled
---
Key: FOP-2178
URL: https://issues.apache.org/jira/browse/FOP-2178
Project: Fop
Issue Type: Bug
incomplete kerning when complex script features are enabled
---
Key: FOP-2178
URL: https://issues.apache.org/jira/browse/FOP-2178
Project: Fop
Issue Type: Bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
--- Comment #8 from Glenn Adams gl...@skynav.com 2012-04-07 01:44:44 UTC ---
resetting P2 open bugs to P3 pending further review
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
Glenn Adams gl...@skynav.com changed:
What|Removed |Added
Priority|P2 |P3
--
Configure
https://issues.apache.org/bugzilla/show_bug.cgi?id=40724
Glenn Adams gl...@skynav.com changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment
https://issues.apache.org/bugzilla/show_bug.cgi?id=48003
Glenn Adams gl...@skynav.com changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment
it
via their config. We can take up the issue of whether to change the
default at a future time.
I do not like the idea of changing the default value of Kerning from off
to on. The reason being that users who decide to upgrade their FOP
version will suddenly find the appearance of their documents
Hi,
I’m just remembering this bug, that may affect you:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
Vincent
On 06/09/10 06:58, Glenn Adams wrote:
Is there a reason that kerning of the base 14 fonts is disabled by default?
Furthermore, except by programmatic means, there does
I just took a look, and that bug seems to be a Type1 AFM/PS issue, different
from the enabling/disabling of base14 font kerning.
However, in the comment thread of it, you do make a point that is worth
repeating for those who aren't aware of it, namely, kerning occurs between
glyphs
of whether to change the default at a
future time.
I do not like the idea of changing the default value of Kerning from off
to on. The reason being that users who decide to upgrade their FOP
version will suddenly find the appearance of their documents changing.
Better to let users who are unsatisfied
the default value of Kerning from off to
on. The reason being that users who decide to upgrade their FOP version will
suddenly find the appearance of their documents changing. Better to let
users who are unsatisfied with the default inter character spacing to go and
enable kerning than force users
.
G.
On Mon, Sep 6, 2010 at 10:07 PM, Jeremias Maerki d...@jeremias-maerki.chwrote:
I think that is for historical reasons. When this was implemented (I
think it was me) I guess we didn't want to change the layout behaviour
for existing users. For a long time, kerning for base 14 fonts
Is there a reason that kerning of the base 14 fonts is disabled by default?
Furthermore, except by programmatic means, there does not seem to be a way
to enable it except by using FontManager.setBase14KerningEnabled() or the
deprecated method FopFactory.setBase14KerningEnabled(). This technique
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
--- Comment #7 from Jeremias Maerki jerem...@apache.org 2010-02-19 15:48:02
UTC ---
Ah, I see, they added many more kerning pairs from version 1.05 to 1.06 of
Nimbus Sans L.
The code that builds the kerning map from the AFM file
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
Summary: Support for Font Kerning is Broken
Product: Fop
Version: all
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
uses the Nimbus Sans L font available on most Unix systems and
downloadable here:
http://sourceforge.net/projects/gs-fonts/
The AFM file gives the same kerning between 'Y' and all the accented variants
of the 'A' letter. Yet kerning is applied only between 'Y' and non-accented
'A'.
--
Configure
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
--- Comment #2 from Vincent Hennebert vhenneb...@gmail.com 2010-02-18
14:35:42 UTC ---
Created an attachment (id=25017)
-- (https://issues.apache.org/bugzilla/attachment.cgi?id=25017)
PDF result; the right borders should be aligned
--
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
--- Comment #3 from Jeremias Maerki jerem...@apache.org 2010-02-18 15:15:25
UTC ---
Currently, kerning only works for characters within the main single-byte
encoding. The implementation uses character codes, not Unicode values, for
kerning
https://issues.apache.org/bugzilla/show_bug.cgi?id=48766
--- Comment #4 from Vincent Hennebert vhenneb...@gmail.com 2010-02-18
15:41:09 UTC ---
(In reply to comment #3)
Currently, kerning only works for characters within the main single-byte
encoding.
No, kerning doesn't work at all. Like I
with Nimbus Sans L (V 1.05) and kerning works just fine for
those combinations for which there is data in the AFM, with PDF and PS. The AFM
I have doesn't have kerning info for “YÆ” or “Fø”. Maybe you just expect
characters like A and Æ to be equivalent, but I don't remember any mention
in any
https://issues.apache.org/bugzilla/show_bug.cgi?id=48003
--- Comment #2 from Alexander Kiel alexanderk...@gmx.net 2009-10-16 05:07:53
UTC ---
Thanks for applying my patch.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail
https://issues.apache.org/bugzilla/show_bug.cgi?id=48003
Summary: [PATCH] Improved variable names around Kerning and
KnuthElement
Product: Fop
Version: all
Platform: PC
OS/Version: Linux
Status: NEW
https://issues.apache.org/bugzilla/show_bug.cgi?id=48003
Adrian Cumiskey d...@cumiskey.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Firstly install Microsoft Corefonts from http://corefonts.sf.net
$ cd /opt/fop-0.95
$ java -cp
build/fop.jar:lib/avalon-framework-4.2.0.jar:lib/commons-logging-1.0.4.jar:lib/commons-io-1.3.1.jar:lib/xmlgraphics-commons-1.3.1.jar
org.apache.fop.fonts.apps.TTFReader
--- Additional Comments From [EMAIL PROTECTED] 2007-04-09 02:20 ---
Fixed, kerning works in the current trunk
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching
On 13.01.2007 06:32:15 Manuel Mall wrote:
While looking into the support for the Soft Hyphen the area of
hyphenation combined with kerning is causing me trouble.
Aside 1: our fonts page claims we don't support kerning but I believe we
do.
Yes, we do.
Aside 2: Our tests are based
While looking into the support for the Soft Hyphen the area of
hyphenation combined with kerning is causing me trouble.
Aside 1: our fonts page claims we don't support kerning but I believe we
do.
Aside 2: Our tests are based on setting the base14kerning flag. I don't
think this flag
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40724.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40724.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/bugzilla/show_bug.cgi?id=40739).
Mapping the glyph indexes to unicode indexes when reading the XML
metrics file seemed more complicated than when creating the file, so I
have implemented the change in the TTFFile class, which now writes the
kerning info based on unicode code points.
A note
On 10/13/06, Jeremias Maerki [EMAIL PROTECTED] wrote:
...Maybe I'll try to figure
out if it's a small change to bypass the metrics file entirely. :-)
Shouldn't be hard at all, but right now I have to create a test
document to demonstrate the new font features for my own project, so
I won't be
Right, it isn't hard. Almost works after a train ride to Zurich and back.
:-)
On 13.10.2006 11:33:09 Bertrand Delacretaz wrote:
On 10/13/06, Jeremias Maerki [EMAIL PROTECTED] wrote:
...Maybe I'll try to figure
out if it's a small change to bypass the metrics file entirely. :-)
Shouldn't
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40724.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40724.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
://issues.apache.org/bugzilla/show_bug.cgi?id=40739).
Mapping the glyph indexes to unicode indexes when reading the XML
metrics file seemed more complicated than when creating the file, so I
have implemented the change in the TTFFile class, which now writes the
kerning info based on unicode code points
/show_bug.cgi?id=40724
Summary: Kerning does not work for user-specified CID fonts
Product: Fop
Version: 1.0dev
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: fonts
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40724.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi FOPpers,
See http://issues.apache.org/bugzilla/show_bug.cgi?id=40724 , kerning
doesn't work for me with user-specified CID fonts at the moment.
IIUC the code, org.apache.fop.layoutmgr.inline.TextLayoutManager
expects unicode indexes for kerning pairs, but currently the TTFReader
writes glyph
,
See http://issues.apache.org/bugzilla/show_bug.cgi?id=40724 , kerning
doesn't work for me with user-specified CID fonts at the moment.
IIUC the code, org.apache.fop.layoutmgr.inline.TextLayoutManager
expects unicode indexes for kerning pairs, but currently the TTFReader
writes glyph
On 10/11/06, Jeremias Maerki [EMAIL PROTECTED] wrote:
...If this change has an effect on the XML files generated, then we should
be careful because people might not recreate their metric files and
subsequently run into problems...
How about adding a version number to the XML metrics files?
Sure. However, as we discussed in Amsterdam, the goal should be that we
don't rely on those XML files much longer, so I wonder how much should
be invested in versioning of those files. But if you don't see a way
around it... I still don't understand why exactly this change is
necessary.
On
[Luca]
...
A little doubt concerning letter spaces: at the moment, a letter space
is assigned to the preceding character. Is this correct? I don't
remember any section in the specs stating about the ownership of
letter spaces ... I think that everything is simpler, from the point of
view of
Starting from your final summary:
Manuel Mall wrote:
IMO FOP should limit itself to:
a) Use kerning only for consecutive characters within the same fo
Ok, but more on this later in this message ...
b) Limit itself to the kerning information in the font
Ok
c) Only apply kerning
Hi Luca.
Its been over 15 years since I did any kerning, but, from what I remember,
kerning isn't just left or right, its also up and down (and possibly other
transforms/alterations for all I know). Consider the kerned symbols in the
LATeX logo. The A is raised and snuggled between the L
Started a new thread on the Kerning topic here as the old subject line
was inappropriate.
On Tue, 6 Dec 2005 12:15 am, Luca Furini wrote:
Manuel Mall wrote:
I wonder if the same argument does apply to kerning as well? The
moment you change font-size, text-decoration, background-color
69 matches
Mail list logo
