ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Latest beta: reference to items broken in mkiv
Date: Wed, 1 Apr 2015 10:24:04 +0200	[thread overview]
Message-ID: <322AD220-CC2B-4364-8196-549F29EE499C@gmail.com> (raw)

Hi Hans,

It seems that referencing to items is broken in the latest beta mkiv: for example in the example below the command
	\in{Item}[ref:2]
does not show item number 2.
However it works fine in mkii and previous releases.
Best regards: OK
PS: a minimal example follows
%%% begin ref-item-broken.tex
\starttext 

\startitemize[n]

\startitem[ref:1]
Item 1, reference 1
\stopitem

\startitem[ref:2]
Item 2, reference 2
\stopitem

\startitem[ref:3]
Item 3, reference 3
\stopitem
	
\stopitemize

See \in{Item}[ref:2] above.

\stoptext
%%% end ref-item-broken.tex
___________________________________________________________________________________
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:[~2015-04-01  8:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01  8:24 Otared Kavian [this message]
     [not found] <F473C14E-DAEF-4EEE-8061-62A36000F454@hccnet.nl>
     [not found] ` <A58B6AB4-C2E8-43AB-94FB-8B79B2C10F2D@gmail.com>
2018-02-07  9:58   ` r.ermers
2018-02-07 10:03     ` Wolfgang Schuster
2018-02-07 10:46       ` r.ermers
2018-02-07 11:37         ` Otared Kavian
2018-02-07 11:56           ` r.ermers
2018-02-07 13:28             ` Otared Kavian
2018-02-07 13:53             ` Otared Kavian
2018-02-07 15:59               ` r.ermers
2018-02-09 16:18               ` r.ermers

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=322AD220-CC2B-4364-8196-549F29EE499C@gmail.com \
    --to=otared@gmail.com \
    --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).