From: Michal Kvasnicka <quasar@econ.muni.cz>
Subject: Changes/bugs in the new Context
Date: Thu, 11 Sep 2003 16:07:06 +0200 [thread overview]
Message-ID: <3F60818A.5010900@econ.muni.cz> (raw)
Dear Mr. Hagen.
I'm sorry I bother you, but I really need a help. Some time ago I
uploaded and installed the new version of ConTeXt (ConTeXt ver:
2003.8.21). After that I was not able to compile some of my documents
due to changes (bug?) in the new version (the changes may be older). I'd
like to ask how should I handle the following two cases in the new version.
1) Changes in colors
In some older version I could write things like this:
\setupheader[style={\ss\bfb\red}]
\setuphead[chapter]
[textstyle={\ss\bfc\setupinterlinespace[line=24pt]\red}]
\setupinteraction[state=start, style=\red]
where \red is a color.
Now it makes errors. How should I handle it now? In heads and headers I
can use command option and \setupheadertexts respectively. But how sould
I set the interactioncolor? (This is the real cause of the problem I
have ask the last week -- by my mistake atributed to the content-lists.)
2) Chagnes (bug?) in references
Some time ago command \reference[...]{...} expanded the term in the
second (curly?) braces before writing to auxiliary files. Now it
doesn't. I use this command in my macros like this
\reference[#1]{\the\somenumber.\the\anothernumber}}
Now the commands \the\somenumber.\the\anothernumber are placed to
.tui/.tuo files without expansion. I had to redefine it in the following
way:
\global\let\OriReference=\reference
\gdef\reference[#1]#2{%
\edef\MyRefO{#2}%
\def\MyRef##1!!{%
\OriReference[#1]{##1}%
}
\expandafter\MyRef\MyRefO!!%
}
Is it a bug or a feature? How should I use it? Doesn't my solution
interfere with the genious ConTeXt macros?
Nonetheless I want to thank you very much for providing such a powerful
macro package as ConTeXt is to all of us for free. The ConTeXt is really
great. Thank you.
Thank you very much for your kind help.
Your sincerely
Michal Kvasnicka
next reply other threads:[~2003-09-11 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:07 Michal Kvasnicka [this message]
2003-09-11 14:54 ` Giuseppe Bilotta
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=3F60818A.5010900@econ.muni.cz \
--to=quasar@econ.muni.cz \
--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).