special case to disable italic correction
Hi Hans, after reading the relevant part for italic correction in fonts-mkiv.pdf and enabling it in my documents, I have found a case in which the italic correction could be improved. My settings are: \definefontfeature[default][default][itlc=yes] \setupitaliccorrection[global,always] If I get it right, the italic correction should be avoided before points and commas (these are all the exceptions I can imagine for this case). The explanation is simple: the space is already at the base line, since at the glyph base, the inclination of the italic or slanted glyph makes the right side-bearing larger at the baseline. The issue with italic correction is mainly with ascenders or at the cap height, but I think it isn’t at the base line (or the descenders). Because of that I think it is important to disable italic correction before points and commas. The sample shows the issue: \setuppagenumbering[location=] \definefontfeature[default][default][itlc=yes] \setupitaliccorrection[global,always] \starttext \startTEXpage[offset=1ex] Abf. {\em Abf}.\\ Abf, {\em Abf},\\ Abf. {\it Abf}.\\ Abf, {\it Abf}, \stopTEXpage \stoptext I think it might be worth considering. Many thanks for your help and your excellent work, Pablo -- http://www.ousia.tk
On 1/26/2014 8:24 PM, Pablo Rodriguez wrote:
Hi Hans,
after reading the relevant part for italic correction in fonts-mkiv.pdf and enabling it in my documents, I have found a case in which the italic correction could be improved.
My settings are:
\definefontfeature[default][default][itlc=yes] \setupitaliccorrection[global,always]
If I get it right, the italic correction should be avoided before points and commas (these are all the exceptions I can imagine for this case). The explanation is simple: the space is already at the base line, since at the glyph base, the inclination of the italic or slanted glyph makes the right side-bearing larger at the baseline. The issue with italic correction is mainly with ascenders or at the cap height, but I think it isn’t at the base line (or the descenders). Because of that I think it is important to disable italic correction before points and commas.
The sample shows the issue:
\setuppagenumbering[location=] \definefontfeature[default][default][itlc=yes] \setupitaliccorrection[global,always] \starttext \startTEXpage[offset=1ex] Abf. {\em Abf}.\\ Abf, {\em Abf},\\ Abf. {\it Abf}.\\ Abf, {\it Abf}, \stopTEXpage \stoptext
I think it might be worth considering.
Many thanks for your help and your excellent work,
Hard coded char checking is talking all punctuation is tricky, so i now use a threshold instead (enabled by default). \disabledirectives[typesetters.threshold] % % % % test: \definefontfeature [default] [default] [itlc=yes] \setupitaliccorrection [global,always] % \enabletrackers[typesetters.italics] \starttext \startTEXpage[offset=1ex] f. {\em f}.\par f, {\em f},\par f. {\it f}.\par f, {\it f},\par f: {\it f}:\par f; {\it f};\par x. {\em x}.\par x, {\em x},\par x. {\it x}.\par x, {\it x},\par x: {\it x}:\par x; {\it x};\par \stopTEXpage \stoptext Will be in next beta. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 01/28/2014 03:14 PM, Hans Hagen wrote:
On 1/26/2014 8:24 PM, Pablo Rodriguez wrote:
[...] If I get it right, the italic correction should be avoided before points and commas (these are all the exceptions I can imagine for this case). The explanation is simple: the space is already at the base line, since at the glyph base, the inclination of the italic or slanted glyph makes the right side-bearing larger at the baseline. The issue with italic correction is mainly with ascenders or at the cap height, but I think it isn’t at the base line (or the descenders). Because of that I think it is important to disable italic correction before points and commas. [...] Hard coded char checking is talking all punctuation is tricky, so i now use a threshold instead (enabled by default). [,,,] Will be in next beta.
Many thanks for your implementation, Hans. It works fine now. Many thanks again for your work, Pablo -- http://www.ousia.tk
participants (2)
-
Hans Hagen -
Pablo Rodriguez