ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: metapost and luatex (or xetex)
Date: Sat, 4 Oct 2008 00:40:36 +0200	[thread overview]
Message-ID: <6faad9f00810031540i531508faydf69558ffce06efa@mail.gmail.com> (raw)
In-Reply-To: <48E68EF5.5050105@wxs.nl>

On Fri, Oct 3, 2008 at 11:30 PM, Hans Hagen wrote:
> Diego Depaoli wrote:
>> Hi all,
>> from metafun manual, page 157, I took this example
>>
>> \startuniqueMPgraphic{copyright}
>> picture p ; p := btex COPYRIGHT etex rotated 90 ;
>> setbounds p to boundingbox p enlarged 1pt ;
>> draw p withcolor .8white ;
>> xyscale_currentpicture(\the\leftmarginwidth,\the\textheight) ;
>> \stopuniqueMPgraphic
>> \setuptexttexts [margin] [] [\uniqueMPgraphic{copyright}]
>> \starttext
>> \input knuth
>> \stoptext
>>
>> but compiling it I get some trouble
>>
>> texexec --pdf works as expected
>> texexec --lua drops colors (COPYRIGHT is black)
>
> is ok, use btex color[white]{COPYRIGHT} etex instead

But that doesn't work in mkii then unless some other "hacks" are added.
(I know, mkii and mkiv are not compatible, but there are no obvious
limitations why they could not work in the same way.)

> (no colorization of pictures with text in mkiv)

(In the particular case of gnuplot, I have no idea how to deal with
that situation without a bunch of extra work since it's not so simple
to convert some color from metapost variable into one that ConTeXt
accepts in \color[...]. I have \chardef\TeXtextcolormode\zerocount in
mkii, but I still consider it ugly.)

In the case of XeTeX: no, it's not normal. If you add
\loadmapfile[lm-ec.map] this solves the problem, but if I was on your
place, I would use \sometxt{COPYRIGHT} instead of btex COPYRIGHT etex.

Loading map files has been removed from XeTeX a while ago. Maybe lm-ec
should be added back for such cases? (I remember some problems with
btex etex in past after map files have been removed, but I don't
remember solving anything at that time.)

Mojca
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-10-03 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 19:18 Diego Depaoli
2008-10-03 21:30 ` Hans Hagen
2008-10-03 22:40   ` Mojca Miklavec [this message]
2008-10-04 10:16     ` Hans Hagen
2008-10-04 12:19     ` Diego Depaoli
2008-10-04 12:14   ` Diego Depaoli
2008-10-06 21:48     ` Mojca Miklavec
2008-10-07 19:56       ` Diego Depaoli
2008-10-06 22:06     ` luigi scarso

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=6faad9f00810031540i531508faydf69558ffce06efa@mail.gmail.com \
    --to=mojca.miklavec.lists@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).