From: Bernhard Rosensteiner <brosensteiner@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [Fwd: hyphen breaking (URGENT)]
Date: Wed, 24 Feb 2010 22:54:06 +0100 [thread overview]
Message-ID: <5432BD99-8990-4591-9CAE-4282E5B3DDB0@gmail.com> (raw)
In-Reply-To: <4B859C69.2040105@googlemail.com>
Am 24.02.2010 um 22:38 schrieb Wolfgang Schuster:
> Am 24.02.10 22:26, schrieb Steffen Wolfrum:
>
>> Perhaps I can also add comments to a writebetweenlist now?
>> Can you some further example on how to use "userdata"?
>
> A example i wrote for Idris a while (April 2009) ago:
>
> \setuphead[chapter][align=middle,command=\TitleCommand]
>
> \define[2]\TitleCommand
> {\startframedtext[frame=off,width=\hsize,align=middle]
> #2\hairline
> \structureuservalue{author}\hfill\structureuservalue{date}
> \stopframedtext}
>
> \starttext
>
> \startchapter
> [title={How to make Idris happy?},reference={sec:happy}]
> [author={Wolfgang Schuster},date=\currentdate]
>
> It's not as hard you think, just show him a few nice things
> and he is happy.
>
> See \in{section}[sec:happy] at \at{page}[sec:happy].
>
> \stopchapter
>
> \stoptext
>
> Wolfgang
Hi,
for curiosity i tried the above code and it gives an error (undefined control sequence)
i searched in the source and found that \structureuservariable is valid not \structureuservalue
best regards
Bernhard
___________________________________________________________________________________
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:[~2010-02-24 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AE30A6B.4090505@wxs.nl>
[not found] ` <4AE310D6.6080907@elvenkind.com>
[not found] ` <ACE81C10-B0B9-4933-BE83-713367A631F6@st.estfiles.de>
[not found] ` <4AE33550.2060900@elvenkind.com>
[not found] ` <245A7276-8D47-4AAF-AE06-2F8F1732BB56@st.estfiles.de>
[not found] ` <4AE3EC92.3090303@elvenkind.com>
[not found] ` <2097E39C-F4AB-4781-9DA2-7AF6295B4521@st.estfiles.de>
[not found] ` <4AE424CE.60806@elvenkind.com>
[not found] ` <4AE45078.1040506@wxs.nl>
[not found] ` <A2DCCEB9-2524-402A-A7AE-64B02AF52FA6@st.estfiles.de>
[not found] ` <4AE465FD.3040409@wxs.nl>
[not found] ` <18A1C982-94C8-4E6F-9C56-4067A147A85D@st.estfiles.de>
[not found] ` <4AE4B631.7040206@wxs.nl>
[not found] ` <D2E56CCB-B29B-45B5-AEFC-059D77049AD2@st.estfiles.de>
2010-02-23 15:23 ` Hans Hagen
2010-02-23 20:18 ` Steffen Wolfrum
2010-02-23 22:27 ` Hans Hagen
2010-02-24 7:50 ` Steffen Wolfrum
2010-02-24 10:31 ` Hans Hagen
2010-02-24 21:01 ` Steffen Wolfrum
2010-02-24 21:26 ` Steffen Wolfrum
2010-02-24 21:38 ` Wolfgang Schuster
2010-02-24 21:54 ` Bernhard Rosensteiner [this message]
2010-02-24 22:11 ` Wolfgang Schuster
2010-02-24 22:22 ` Bernhard Rosensteiner
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=5432BD99-8990-4591-9CAE-4282E5B3DDB0@gmail.com \
--to=brosensteiner@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).