Re: [NTG-context] Hanging punctuation misalignment in footnotes
On 2/22/2014 1:25 AM, Jan Tosovsky wrote:
On 2014-02-22 Jan Tosovsky wrote:
when hanging in footnotes is enabled and the starting character is a punctuation, it is not protruded. However, the same character in the footnote body works fine. When both cases are close each other, it looks weird, see the screenshot:
http://drifted.in/other/footnote_alignment.png
Would it be possible make this behaviour uniform - either do not protrude it on the starting (left) edge or protrude it everywhere?
A minimal example is available at http://drifted.in/other/sample.tex
(those guillemets would be lost here in the mailing list)
Tested in the current beta on Windows (it requires Palatino Linotype font).
Hard to solve that one fast .. basically all that gets bound to a next characters makes that next character not protrude. This is not something the engine can solve as it doesn't know what it deals with (so the current behaviour is as it should be). Maybe in a future version of context I can deal with it (as I know how to do it, but that doesn't help much now). 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 2014-02-22 Hans Hagen wrote:
On 2/22/2014 1:25 AM, Jan Tosovsky wrote:
On 2014-02-22 Jan Tosovsky wrote:
when hanging in footnotes is enabled and the starting character is a punctuation, it is not protruded. However, the same character in the footnote body works fine. When both cases are close each other, it looks weird, see the screenshot:
http://drifted.in/other/footnote_alignment.png
Would it be possible make this behaviour uniform - either do not protrude it on the starting (left) edge or protrude it everywhere?
A minimal example is available at http://drifted.in/other/sample.tex
(those guillemets would be lost here in the mailing list)
Tested in the current beta on Windows (it requires Palatino Linotype font).
Hard to solve that one fast .. basically all that gets bound to a next characters makes that next character not protrude. This is not something the engine can solve as it doesn't know what it deals with (so the current behaviour is as it should be).
:-/
Maybe in a future version of context I can deal with it (as I know how to do it, but that doesn't help much now).
I am looking forward to it. While I can intervene manualy now {\hskip -0.7mm}>Fel..., it is of no use for dynamic publishing. Thanks, Jan
participants (2)
-
Hans Hagen -
Jan Tosovsky