From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Protrusion cancellation by index term
Date: Mon, 21 Mar 2016 22:59:29 +0100 [thread overview]
Message-ID: <31101.5009101995$1458597615@news.gmane.org> (raw)
In-Reply-To: <5309C61E.2050302@wxs.nl>
On 2014-02-23 Hans Hagen wrote:
> On 2/22/2014 2:38 PM, Jan Tosovsky wrote:
> > On 2014-02-22 Jan Tosovsky wrote:
> > >
> > > when a punctuated phrase appears at the beginning of the line,
> > > it is not protruded correctly when preceded by an index term.
> > >
> > > ... \index{foo}>Bar< ...
> > >
> > > A minimal example is available at
> > > http://drifted.in/other/sample.tex
> > >
> > > I cannot place the space character between these two parts
> > > (which helps) as I sometimes need to join this and the previous
> > > phrase with the non-breaking space.
> > >
> >
> > It is more serious issue than expected. Consider next two
> > variants:
> >
> > (1) sentence, \index{primary}>Primary<
> > (2) sentence,\index{primary} >Primary<
> >
> > When the line is broken after a comma:
> > ad 1) starting guillemet is not protruded
> > ad 2) ending comma is not protruded
> >
> > When \index is surrounded by spaces from both sides, the space is
> > rendered at the beginning of the next line (resulting in
> > 'indenting').
> >
> > I'd be grateful for ignoring any non document content preceding
> > punctuation to avoid its influence on protrusion.
>
> well, think of it like this:
>
> [something]<text>[something else]
>
> with [something] being bound to < ... so that is then the boundary of
> the word, not < ... i might know a solution (but such -major- changes
> have to fit into my schedule)
are there any improvements here with revamped token processing implemented
in recent versions?
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:[~2016-03-21 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00c301cf2f67$2df79150$89e6b3f0$@tosovsky@email.cz>
2014-02-22 13:38 ` Jan Tosovsky
[not found] ` <000f01cf2fd3$532e9380$f98bba80$@tosovsky@email.cz>
2014-02-23 9:57 ` Hans Hagen
2016-03-21 21:59 ` Jan Tosovsky [this message]
[not found] ` <01ac01d183bc$f2213d50$d663b7f0$@tosovsky@email.cz>
2016-03-22 16:48 ` Hans Hagen
2016-03-30 19:53 ` Jan Tosovsky
[not found] ` <017c01d18abd$c8d37b90$5a7a72b0$@tosovsky@email.cz>
2016-03-30 22:10 ` Hans Hagen
2016-03-31 19:28 ` Jan Tosovsky
[not found] ` <56fd7a8a.e559c20a.ada5.350bSMTPIN_ADDED_BROKEN@mx.google.com>
2016-03-31 20:47 ` Wolfgang Schuster
2016-04-01 7:17 ` Hans Hagen
2016-04-01 19:59 ` Jan Tosovsky
[not found] ` <01b401d18c51$08930ef0$19b92cd0$@tosovsky@email.cz>
2016-04-03 17:38 ` Hans Hagen
2016-04-10 10:53 ` Jan Tosovsky
[not found] ` <006801d19317$49110c80$db332580$@tosovsky@email.cz>
2016-04-10 14:47 ` Hans Hagen
[not found] ` <020f01d18b83$8635bb60$92a13220$@tosovsky@email.cz>
2016-04-01 7:23 ` Hans Hagen
2014-02-22 0:44 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='31101.5009101995$1458597615@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).