From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Bug in label and setuphead
Date: Thu, 17 Jan 2013 13:20:44 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.02.1301171313560.19160@ybpnyubfg.ybpnyqbznva> (raw)
Hi,
(This is based on a question on tex.se:
http://tex.stackexchange.com/q/94170/323)
If a new head is defined based on an existing head, it still uses the
label of the previous head.
\definehead[whatever][chapter]
\setuplabeltext[en][whatever=Whatever~]
\setuplabeltext[en][chapter=Chapter~]
\starttext
\whatever{Animals}
\chapter{Plants}
\stoptext
Uses the label Chapter for both heads. This is because the .tuc file
contains label=chapter for both elements.
utilitydata_structures_lists.collected={
{
["metadata"]=1,
["numberdata"]=3,
["references"]={
["block"]="bodypart",
["internal"]=1,
["realpage"]=1,
["section"]=1,
},
["titledata"]={
["label"]="chapter",
["title"]="Animals",
},
},
{
["metadata"]=4,
["numberdata"]=6,
["references"]={
["block"]="bodypart",
["internal"]=2,
["realpage"]=2,
["section"]=2,
},
["titledata"]={
["label"]="chapter",
["title"]="Plants",
},
},
}
Adding
\setuphead[whatever][label=whatever]
does not change anything. This looks like a bug to me.
Otherwise, what is the right way of changing the label of a section head?
Aditya
___________________________________________________________________________________
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 reply other threads:[~2013-01-17 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 18:20 Aditya Mahajan [this message]
2013-01-18 1:36 ` Wolfgang Schuster
2013-01-18 17:04 ` Aditya Mahajan
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=alpine.LNX.2.02.1301171313560.19160@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).