From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: backgroundcolor broken in 2006-06-07
Date: Fri, 9 Jun 2006 23:49:22 +0200 [thread overview]
Message-ID: <9DE73D7F-A6B4-4EC3-9D1C-1E5E70763A51@science.uva.nl> (raw)
In-Reply-To: <44896CBD.5020106@elvenkind.com>
On Jun 9, 2006, at 14:42, Taco Hoekwater wrote:
>
>
> Hans van der Meer wrote:
>> In the latest context version of 2006-06-7 coloring the background
>> seems
>> broken.
>> Reverting to the version 2006-05-28 remedied this, but I have no
>> intention of course, to freeze my system at that point.
>>
>> Here is a minimal example that colors the background in 2006-05-28
>> and
>> does not in 2006-06-07:
>>
>> \setupcolors[state=start]
>> \definetextbackground[showbkg][frame=off,location=text,
>> background=color,backgroundcolor=orange,backgroundoffset=0pt]
>> \starttext
>> tekst \startshowbkg background \stopshowbkg{} tekst.
>> \stoptext
>>
>> Can someone look into this? I am relying on this coloring!
>
> Backgrounds work ok here (on Linux).
THANKS for those who checked this on their system and found nothing
wrong. But that was bad news for me.
I switched back and force between the versions of 2006-05-28 and
2006-06-07 by replacing all context related files from cont-tmf.zip,
taking care to first remove all the old contents, regenerating the
formats afterwards. Definitely the 2006-05-28 works, the 2006-06-07
does not work here.
At the brink of giving up I thought it should be metapost related and
then found in cont-sys.tex some patches I had received earlier and
these now had to be taken out. So back to normal!
QUESTION: is the issue related to these patches now resolved from
version 2006-06-07 onwards?
These patches were:
"% PATCH FOR SUPPRESS "unknown"s IN METAPOST COMMUNICATION OF textext"
\unexpanded\def\startcolor
{\ifincolor
\expandafter\doglobalstartcolor
\else
\expandafter\noglobalstartcolor
\fi}
\unexpanded\def\stopcolor
{\ifincolor
\doglobalstopcolor
\else
\noglobalstopcolor
\fi}
and
"% PATCH FOR STANDALONE GRAPHICS WHERE textext WAS NOT WORKING"
\long\def\writecheckedMPgraphic#1%
{\ifforceMPTEXgraphic
\global\MPTEXgraphictrue
\else
\global\MPTEXgraphicfalse
\edef\ascii{#1}\convertcommand\ascii\to\MPascii
\the\MPTEXgraphicchecks\relax % \relax is end condition!
\fi
\flushMPTEXgraphic % verbatimtex etc
\writeMPgraphic{#1}}
Hans van der Meer
next prev parent reply other threads:[~2006-06-09 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 12:21 Hans van der Meer
2006-06-09 12:42 ` Taco Hoekwater
2006-06-09 14:07 ` Aditya Mahajan
2006-06-09 21:49 ` Hans van der Meer [this message]
2006-06-10 6:37 ` Hans van der Meer
2006-06-10 7:10 ` Taco Hoekwater
2006-06-10 14:57 ` Hans van der Meer
2006-06-11 9:56 ` Taco Hoekwater
2006-06-11 13:55 ` Hans van der Meer
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=9DE73D7F-A6B4-4EC3-9D1C-1E5E70763A51@science.uva.nl \
--to=hansm@science.uva.nl \
--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).