From: Berend de Boer <berend@pobox.com>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Palet option in setuptyping not working
Date: Thu, 11 Jan 2007 09:20:40 +1300 [thread overview]
Message-ID: <87ejq2ocpz.fsf@dullio.nederware.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
(I've repeated this post, because I didn't see any answers. Sample
file included, you can easily check if I'm wrong or right).
It seems user palets don't work (anymore?), just downloaded the new
version but still has the same problem as the version I used before
(aug 2006).
Sample file:
- --------------------------------------------------
% interface=en
\setupbodyfont
[postscript,16pt]
\setupcolors
[state=start]
\setupalign
[hyphenated]
\definepalet
[MYcolorpretty]
[prettyone=colorprettyone,
prettytwo=colorprettytwo,
prettythree=colorprettythree,
prettyfour=colorprettyfour]
\setuptyping
[TEX]
[palet=MYcolorpretty]
\starttext
\startTEX
\this \is \a \test
\stopTEX
\stoptext
- --------------------------------------------------
As you will see, there are no colors anymore.
My tex and context versions:
This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) (format=cont-en 2007.1.4) 4 JAN 2007 20:14
entering extended mode
ConTeXt ver: 2007.01.02 13:44 MK II fmt: 2007.1.4 int: english/english
- --
Live long and prosper,
Berend de Boer
PS: This email has been digitally signed if you wonder what the strange
characters are that your outdated email client displays.
PGP public key: http://www.pobox.com/~berend/berend-public-key.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFFpUqYIyuuaiRyjTYRAlccAKCNjxWNXOJd3Z7I9XiYr3rRB5VQTQCfdgEJ
AImWg4IZYM9fkXuFIM9TIjY=
=gaQu
-----END PGP SIGNATURE-----
next reply other threads:[~2007-01-10 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 20:20 Berend de Boer [this message]
2007-01-11 22:48 ` Aditya Mahajan
2007-01-11 23:32 ` Taco Hoekwater
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=87ejq2ocpz.fsf@dullio.nederware.nl \
--to=berend@pobox.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).