From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Hanging punctuation misalignment in footnotes
Date: Sat, 22 Feb 2014 12:36:00 +0100 [thread overview]
Message-ID: <14522.8207963102$1393068985@news.gmane.org> (raw)
In-Reply-To: <530873FD.7020804@wxs.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
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-02-22 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00c101cf2f5a$dccfc600$966f5200$@tosovsky@tiscali.cz>
2014-02-22 0:25 ` Jan Tosovsky
[not found] ` <00c201cf2f64$9c6d7d50$d54877f0$@tosovsky@email.cz>
2014-02-22 9:55 ` Hans Hagen
2014-02-22 11:36 ` Jan Tosovsky [this message]
[not found] ` <5307ee93.437e0e0a.70d2.413eSMTPIN_ADDED_BROKEN@mx.google.com>
2014-02-23 18:50 ` Wolfgang Schuster
2016-03-29 21:07 ` Jan Tosovsky
[not found] ` <025b01d189ff$02089e00$0619da00$@tosovsky@email.cz>
2016-03-30 6:28 ` Hans Hagen
[not found] <5307de3d.c8670e0a.6ad6.ffffcff0SMTPIN_ADDED_BROKEN@mx.google.com>
2014-02-21 23:34 ` Thangalin
2014-02-21 23:15 Jan Tosovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='14522.8207963102$1393068985@news.gmane.org' \
--to=j.tosovsky@email.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).