From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: authors in the toc
Date: Sat, 11 Apr 2015 12:02:32 -0400 [thread overview]
Message-ID: <55294598.5010509@rik.users.panix.com> (raw)
In-Reply-To: <F9528CA1-CF6A-40E3-BEF2-29A1A2DA2397@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1878 bytes --]
On 2015-04-11 03:27, Wolfgang Schuster wrote:
>
>> Am 10.04.2015 um 19:33 schrieb Rik Kabel <context@rik.users.panix.com
>> <mailto:context@rik.users.panix.com>>:
>>
>> Another bump. The example on the wiki still fails.
>>
>> On 2014-10-02 13:42, Rik Kabel wrote:
>>> On 2014-10-02 05:18, Wolfgang Schuster wrote:
>>>> There is a example on the wiki. You have to set your own values
>>>> with the second argument of the \startchapter etc. command, to
>>>> display the entry in the roc you have to write your own layout
>>>> where you access it with the \structurelistuservariable command.
>>>>
>>>> http://wiki.contextgarden.net/Generate_Authorlist_from_Head_Content
>>>>
>>>> Wolfgang
>>>>
>>> This example fails for me using the current (2014-09-27) standalone
>>> beta and with TL14. The failure is that the list of authors is
>>> presented as a grid without contents.
>>>
>>> Changing any of the lines in the example that construct the table
>>> cells, such as
>>>
>>> \bTD \structureuservariable{author} \eTD
>>>
>>> to
>>>
>>> \bTD xx \structureuservariable{author} \eTD
>>>
>>> results in a table with the new text, but no user variable text,
>>> showing that the \structureuservariable commands are not returning
>>> any text in this example.
>>>
>>> Has something relevant changed since the example was prepared
>>> (2010-11 or earlier)?
>>>
>>> (A pointer to useful descriptions of \structureuservariable and
>>> \structurelistuservariable would also be welcome. In the wiki, the
>>> startsection command description describes the former, but I have
>>> come across no comprehensive description for either in the
>>> documentation.)
>
> You have to expand the whole content of the sort entry with
>
> \expanded{\author[…]{…}}
>
> Wolfgang
Thank you for the fix. Wiki updated.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 4906 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2015-04-11 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 23:17 Andrea Valle
2014-10-02 9:18 ` Wolfgang Schuster
2014-10-02 17:42 ` Rik Kabel
2014-10-02 19:22 ` Wolfgang Schuster
2014-10-03 19:09 ` Generate Authorlist example fails, was " Rik Kabel
2015-04-10 17:33 ` Rik Kabel
2015-04-11 7:27 ` Wolfgang Schuster
2015-04-11 16:02 ` Rik Kabel [this message]
2014-10-03 14:32 ` Andrea Valle
2014-10-03 17:00 ` Rik Kabel
2014-10-03 20:04 ` Andrea Valle
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=55294598.5010509@rik.users.panix.com \
--to=context@rik.users.panix.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).