ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Thomas Schmitz <tschmit1@uni-bonn.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>,
	Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: where to place \index (again)
Date: Sun, 26 Jun 2011 22:52:19 +0200	[thread overview]
Message-ID: <BC4507F4-B0B9-4931-A2BC-B0D2084BB774@googlemail.com> (raw)
In-Reply-To: <web-7487910@be2.uni-bonn.de>


Am 26.06.2011 um 22:18 schrieb Thomas Schmitz:

>> \setuplayout[width=6.3cm]\showframe
>> %\let\forcecolorhack\relax
>> \starttext
>> This is a short sentence to check \index{test}the \tex{index} command.
>> This is another sentence for the test\index{test}.
>> \stoptext
>> The problem when you put the \index command before a word is that
>> it can end in a visible space at the end of the previous line.
>> Wolfgang
> Thanks, Wolfgang. Just to confirm: yes, this short test does indeed show exactly the effects I was referring to. So question to Taco: could some lua trickery somehow get around these nasty effects?  Because they really make finishing a long project somewhat difficult...

The effect is caused by \forcecolorhack and when uncomment
my redefinition you can see that the output is as expected
but there has to be a reason why Hans use it.

Wolfgang

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-06-26 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26 12:54 Thomas A. Schmitz
2011-06-26 16:35 ` Steffen Wolfrum
2011-06-26 17:47 ` Hans Hagen
2011-06-26 19:13   ` Steffen Wolfrum
2011-06-26 19:29     ` Wolfgang Schuster
2011-06-26 20:18       ` Thomas Schmitz
2011-06-26 20:52         ` Wolfgang Schuster [this message]
2011-06-27 18:01           ` Hans Hagen
2011-06-27  7:38         ` Steffen Wolfrum
2011-06-27 16:01         ` Hans Hagen

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=BC4507F4-B0B9-4931-A2BC-B0D2084BB774@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=tschmit1@uni-bonn.de \
    /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).