FOP 1.1: Unwanted Ligatures in Latin Scripts
Hi all, I just upgraded from 0.95 to 1.1 and one of the issues that crept up is that suddenly FOP uses ligatures, which it did not use before. Latin words containing the letters fi or fl are now rendered using ligatures in the PDF, although they are written as two seperate characters in the XML input file. I can open a bug and/or supply concrete test cases if needed, but I just wanted to ask beforehand whether that is a known problem or perhaps a configuration option? I am using a TrueType font, Pragmatica Condensed. It may well have to do with this font, since the standard FOP examples do not seem to have this problem. Many thanks in advance for any pointers, Ulrich - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
Hi Ulrich, On 28/05/13 11:01, Ulrich Mayring wrote: Hi all, I just upgraded from 0.95 to 1.1 and one of the issues that crept up is that suddenly FOP uses ligatures, which it did not use before. Latin words containing the letters fi or fl are now rendered using ligatures in the PDF, although they are written as two seperate characters in the XML input file. Why would you /not/ want to have ligatures? They are there to make the text look better. I can open a bug and/or supply concrete test cases if needed, but I just wanted to ask beforehand whether that is a known problem or perhaps a configuration option? I am using a TrueType font, Pragmatica Condensed. It may well have to do with this font, since the standard FOP examples do not seem to have this problem. Many thanks in advance for any pointers, Ulrich Vincent - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
Vincent Hennebert wrote: Hi Ulrich, On 28/05/13 11:01, Ulrich Mayring wrote: Hi all, I just upgraded from 0.95 to 1.1 and one of the issues that crept up is that suddenly FOP uses ligatures, which it did not use before. Latin words containing the letters fi or fl are now rendered using ligatures in the PDF, although they are written as two seperate characters in the XML input file. Why would you /not/ want to have ligatures? They are there to make the text look better. For two reasons: 1. The text looks in fact worse, at least with the font I'm using. 2. Testability. We have thousands of integrations tests for the PDFs we generate with fop and our test framework does not support ligatures. For example, it looks for the phrase identification and does not find it in the PDF, if the fi ligature is used. Ulrich - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
Ulrich Mayring wrote: Vincent Hennebert wrote: Hi Ulrich, On 28/05/13 11:01, Ulrich Mayring wrote: Hi all, I just upgraded from 0.95 to 1.1 and one of the issues that crept up is that suddenly FOP uses ligatures, which it did not use before. Latin words containing the letters fi or fl are now rendered using ligatures in the PDF, although they are written as two seperate characters in the XML input file. Why would you /not/ want to have ligatures? They are there to make the text look better. For two reasons: 1. The text looks in fact worse, at least with the font I'm using. 2. Testability. We have thousands of integrations tests for the PDFs we generate with fop and our test framework does not support ligatures. For example, it looks for the phrase identification and does not find it in the PDF, if the fi ligature is used. I have confirmed that this happens only with our font. The supplied FOP examples that use Helvetica, Times Roman etc. do not produce ligatures. Is this considered to be a bug (ligatures should not appear per default) or a missing feature (no way to turn ligatures off, but there should be) or even a works as designed (we never want to render without ligatures, if they are available)? Ulrich - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
Hi, ligature feature depends on font capabilities. It comes with the complex script new feature added in FOP 1.1 (see [1]). There is an (incomplete) list of fonts that support such feature (see [2]). You can disable such behaviour in 2 ways: - either disable the whole feature (see [3]), - or inserting a ZWNJ where it is relevant (see [4]). [1] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html [2] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html#supported_fonts [3] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html#Disabling-complex-scripts [4] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html#join_controls 2013/5/28 Ulrich Mayring u...@denic.de Ulrich Mayring wrote: Vincent Hennebert wrote: Hi Ulrich, On 28/05/13 11:01, Ulrich Mayring wrote: Hi all, I just upgraded from 0.95 to 1.1 and one of the issues that crept up is that suddenly FOP uses ligatures, which it did not use before. Latin words containing the letters fi or fl are now rendered using ligatures in the PDF, although they are written as two seperate characters in the XML input file. Why would you /not/ want to have ligatures? They are there to make the text look better. For two reasons: 1. The text looks in fact worse, at least with the font I'm using. 2. Testability. We have thousands of integrations tests for the PDFs we generate with fop and our test framework does not support ligatures. For example, it looks for the phrase identification and does not find it in the PDF, if the fi ligature is used. I have confirmed that this happens only with our font. The supplied FOP examples that use Helvetica, Times Roman etc. do not produce ligatures. Is this considered to be a bug (ligatures should not appear per default) or a missing feature (no way to turn ligatures off, but there should be) or even a works as designed (we never want to render without ligatures, if they are available)? Ulrich --**--**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org -- pascal
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether ligatures are used or not.
The following features are enabled by default for all scripts which do not
otherwise override this feature set:
GSUB: {ccmp, liga, locl}
GPOS: {kern, mark, mkmk}
See org.apache.fop.complexscripts.scripts.DefaultScriptProcessor.
If you read the description of these features [1], you will find that they
are defined as should be active by default.
[1] http://www.microsoft.com/typography/otspec/featurelist.htm
So, if a font designer includes a 'liga' table in the font, then those
substitutions will apply. As Pascal has pointed out, you can disable CS
entirely, in which case none of the GSUB or GPOS processing is performed.
Another work around would be to use something like:
fo:character character=f/fo:character character=i/
which happens to work at the moment due to a bug that prevents performing
GSUB processing across an element boundary, but that may be fixed at some
point.
A better long term solution is to introduce the CSS3 Font Module's
font-variant-ligatures property [2], or, more generally, the
font-feature-settings property [3] as fox: extension attributes.
[2] http://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop
[3] http://www.w3.org/TR/css3-fonts/#font-feature-settings-prop
Regards,
Glenn
On Tue, May 28, 2013 at 3:01 AM, Ulrich Mayring u...@denic.de wrote:
Hi all,
I just upgraded from 0.95 to 1.1 and one of the issues that crept up is
that suddenly FOP uses ligatures, which it did not use before. Latin words
containing the letters fi or fl are now rendered using ligatures in the
PDF, although they are written as two seperate characters in the XML input
file.
I can open a bug and/or supply concrete test cases if needed, but I just
wanted to ask beforehand whether that is a known problem or perhaps a
configuration option?
I am using a TrueType font, Pragmatica Condensed. It may well have to do
with this font, since the standard FOP examples do not seem to have this
problem.
Many thanks in advance for any pointers,
Ulrich
--**--**-
To unsubscribe, e-mail:
fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail:
fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
Thanks a lot guys for the information. I noticed the new feature Complex
Scripts, but did not look at it more closely, because I thought it would not
apply to me using plain English :)
I have turned the feature off for now, which not only got rid of the
ligatures, it has also fixed the kerning for numbers, such as postal codes,
dates and account numbers. With the Complex Scripts feature on these numbers
are basically rendered in a monospaced way, which looks real ugly in most
places. Not sure which of the features mentioned are responsible for that
strange kerning (or lack thereof).
I cannot use any of the suggested workarounds, because the text I process is
in parts dynamically generated and outside of my control. It would of course
be great if it were possible to enable/disable the various Complex Scripts
features independent of each other, preferably not just globally, but on a
per-paragraph level.
Kind regards,
Ulrich
Glenn Adams wrote:
The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether ligatures are used or not.
The following features are enabled by default for all scripts which do not
otherwise override this feature set:
GSUB: {ccmp, liga, locl}
GPOS: {kern, mark, mkmk}
See org.apache.fop.complexscripts.scripts.DefaultScriptProcessor.
If you read the description of these features [1], you will find that they
are defined as should be active by default.
[1] http://www.microsoft.com/typography/otspec/featurelist.htm
So, if a font designer includes a 'liga' table in the font, then those
substitutions will apply. As Pascal has pointed out, you can disable CS
entirely, in which case none of the GSUB or GPOS processing is performed.
Another work around would be to use something like:
fo:character character=f/fo:character character=i/
which happens to work at the moment due to a bug that prevents performing
GSUB processing across an element boundary, but that may be fixed at some
point.
A better long term solution is to introduce the CSS3 Font Module's
font-variant-ligatures property [2], or, more generally, the
font-feature-settings property [3] as fox: extension attributes.
[2] http://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop
[3] http://www.w3.org/TR/css3-fonts/#font-feature-settings-prop
Regards,
Glenn
On Tue, May 28, 2013 at 3:01 AM, Ulrich Mayring u...@denic.de wrote:
Hi all,
I just upgraded from 0.95 to 1.1 and one of the issues that crept up is
that suddenly FOP uses ligatures, which it did not use before. Latin words
containing the letters fi or fl are now rendered using ligatures in the
PDF, although they are written as two seperate characters in the XML input
file.
I can open a bug and/or supply concrete test cases if needed, but I just
wanted to ask beforehand whether that is a known problem or perhaps a
configuration option?
I am using a TrueType font, Pragmatica Condensed. It may well have to do
with this font, since the standard FOP examples do not seem to have this
problem.
Many thanks in advance for any pointers,
Ulrich
--**--**-
To unsubscribe, e-mail:
fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail:
fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
FOP 1.0 Wrap text in table cell
Hi all, I already tried wrap-option=wrap,keep-together.within-column=always but still can't put the text wrapping in the table cell. anyone know what to do? Thanks -- View this message in context: http://apache-fop.1065347.n5.nabble.com/FOP-1-0-Wrap-text-in-table-cell-tp38595.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.1: Unwanted Ligatures in Latin Scripts
On Tue, May 28, 2013 at 9:59 AM, Ulrich Mayring u...@denic.de wrote:
Thanks a lot guys for the information. I noticed the new feature Complex
Scripts, but did not look at it more closely, because I thought it would
not apply to me using plain English :)
I have turned the feature off for now, which not only got rid of the
ligatures, it has also fixed the kerning for numbers, such as postal codes,
dates and account numbers. With the Complex Scripts feature on these
numbers are basically rendered in a monospaced way, which looks real ugly
in most places. Not sure which of the features mentioned are responsible
for that strange kerning (or lack thereof).
Actually, that may be due to another registered bug on my hit list:
https://issues.apache.org/jira/browse/FOP-2213
I cannot use any of the suggested workarounds, because the text I process
is in parts dynamically generated and outside of my control. It would of
course be great if it were possible to enable/disable the various Complex
Scripts features independent of each other, preferably not just globally,
but on a per-paragraph level.
This would be possible if we introduce an fox:font-feature-settings
property as defined in [3] cited below, or at least if they add a generic
'none' or 'off' value that disables all features. However, I doubt you
would ever want to disable all font features, but rather would prefer to
control them on a feature by feature basis, as presently defined in [3].
For example, you could specify:
fo:block fox:font-feature-setting='liga' off
Disable common ligature substitutions for 'ff', 'fi', 'fl', 'ffi', 'ffl',
etc.
/fo:block
I think it probably undesirable to turn of CS on a block basis, though that
could probably be implemented as well without undue difficulty.
I've added a couple of New Feature issues on these items:
https://issues.apache.org/jira/browse/FOP-2256
https://issues.apache.org/jira/browse/FOP-2257
Kind regards,
Ulrich
Glenn Adams wrote:
The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether ligatures are used or not.
The following features are enabled by default for all scripts which do not
otherwise override this feature set:
GSUB: {ccmp, liga, locl}
GPOS: {kern, mark, mkmk}
See org.apache.fop.complexscripts.**scripts.**DefaultScriptProcessor.
If you read the description of these features [1], you will find that they
are defined as should be active by default.
[1]
http://www.microsoft.com/**typography/otspec/featurelist.**htmhttp://www.microsoft.com/typography/otspec/featurelist.htm
So, if a font designer includes a 'liga' table in the font, then those
substitutions will apply. As Pascal has pointed out, you can disable CS
entirely, in which case none of the GSUB or GPOS processing is performed.
Another work around would be to use something like:
fo:character character=f/fo:character character=i/
which happens to work at the moment due to a bug that prevents performing
GSUB processing across an element boundary, but that may be fixed at some
point.
A better long term solution is to introduce the CSS3 Font Module's
font-variant-ligatures property [2], or, more generally, the
font-feature-settings property [3] as fox: extension attributes.
[2]
http://www.w3.org/TR/css3-**fonts/#font-variant-ligatures-**prophttp://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop
[3]
http://www.w3.org/TR/css3-**fonts/#font-feature-settings-**prophttp://www.w3.org/TR/css3-fonts/#font-feature-settings-prop
Regards,
Glenn
On Tue, May 28, 2013 at 3:01 AM, Ulrich Mayring u...@denic.de wrote:
Hi all,
I just upgraded from 0.95 to 1.1 and one of the issues that crept up is
that suddenly FOP uses ligatures, which it did not use before. Latin
words
containing the letters fi or fl are now rendered using ligatures in
the
PDF, although they are written as two seperate characters in the XML
input
file.
I can open a bug and/or supply concrete test cases if needed, but I just
wanted to ask beforehand whether that is a known problem or perhaps a
configuration option?
I am using a TrueType font, Pragmatica Condensed. It may well have to do
with this font, since the standard FOP examples do not seem to have this
problem.
Many thanks in advance for any pointers,
Ulrich
--**
--**-
To unsubscribe, e-mail:
fop-users-unsubscribe@**xmlgra**phics.apache.orghttp://xmlgraphics.apache.org
fop-users-**unsubscribe@xmlgraphics.**apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.**a**
pache.org
http://apache.orgfop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org
--**--**-
To unsubscribe, e-mail:
