ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX problems with \seeindex and \from
Date: Mon, 14 Apr 2008 15:40:11 +0200	[thread overview]
Message-ID: <48035EBB.4020507@wxs.nl> (raw)
In-Reply-To: <6607a2f30804130257ha29a255s27845a69d0e31a6d@mail.gmail.com>

Drazen Baic wrote:
> Hi,
> 
> this is my first posting to this list but I'm following it through the
> archives for quite a long time.
> 
> First I would like to thank the list for this huge archive. By reading
> the documentation and searching this archive most of my questions
> about ConTeXt where answered. I searched for these problems but couldn't
> find anything.
> 
> Now to my question: I was generating my documents with XeTeX until I
> switched to LuaTeX and MKIV a few days ago. After I changed my
> typescripts almost everything worked perfectly but the commands
> \seeindex[]{}{} and \from[].
> 
> 1) \seeindex simply doesn't seem to work. The index is generated but all
> \seeindex entries are missing. It works perfectly when generated with
> 'texexec --xtx'. Generating the document with \version[temporary] shows
> in the margin '> i Indexentry' and '> see Showindexentry' so it seems
> that both entries are ok. I set up the register with
> '\completeindex[interaction=text,align=yes]'
> 
> Is this a bug or are \seeindex entries handled different with LuaTeX?

can be a bug ... so you need to make a small example file

-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-04-14 13:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13  9:57 Drazen Baic
2008-04-14  7:57 ` Taco Hoekwater
2008-04-14 16:50   ` Drazen Baic
2008-04-15  9:15     ` Taco Hoekwater
2008-04-15  9:28       ` Mojca Miklavec
2008-04-15  9:33         ` Taco Hoekwater
2008-04-15 14:03     ` Taco Hoekwater
2008-04-15 16:46       ` Drazen Baic
2008-04-15 16:51         ` Taco Hoekwater
2008-04-14 13:40 ` Hans Hagen [this message]
2008-04-14 16:50   ` Drazen Baic
2008-04-15 16:51     ` Hans Hagen
2008-04-15 18:47       ` Drazen Baic
2008-04-15 22:02         ` Drazen Baic
2008-04-16 21:43           ` Drazen Baic

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=48035EBB.4020507@wxs.nl \
    --to=pragma@wxs.nl \
    --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).