Re: [NTG-context] Protrusion cancellation by index term
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 3/21/2016 10:59 PM, Jan Tosovsky wrote:
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?
it's not that trivial - for the index we can cheat a bit but then i also need to check lots of other cases for possible interference - for the footnote case there is no real solution as the heuristics of finding a protrusion character cannot be tricked too much without breaking it in other cases but ... i think i can cook up something extra in the engine to drive the process; i'll play with it but again. it will take a lot of testing so it will then probably be an option for a while Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/b725c6396317bce49729e7787da89aef.jpg?s=120&d=mm&r=g)
On 2016-03-22 Hans Hagen wrote:
On 3/21/2016 10:59 PM, Jan Tosovsky wrote:
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
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?
it's not that trivial
... for the index we can cheat a bit but then i also need to check lots of other cases for possible interference
Can you roughly estimate when this could be further investigated? Between 0.90-0.95, later or after 1.0? I hope there will be some way to fix it in ConTeXt one day. Jan
participants (2)
-
Hans Hagen
-
Jan Tosovsky