ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lost colors (mkiv)
Date: Wed, 26 Dec 2007 20:12:55 +0100	[thread overview]
Message-ID: <4772A7B7.4000802@wxs.nl> (raw)
In-Reply-To: <4771063F.2050301@gmx.net>

Peter Rolf wrote:
> Hi,
> 
> can anyone with an actual *luatex* test, if this fails (live ConTeXt is
> broken). My binaries are from the minimals at contextgarden (pragma
> tree), ConTeXt is the latest beta.

if you consider how color is implemented, this is actually not a bug

what do you expect in the following case ...

	\setbox\scratchbox{hi there}

	\hbox{\bf \copy\scratchbox}

till we had luatex, only fonts could be considered an attribute, and a 
rather limited one: each glyph node has a font id attached; luatex has a 
more generalized concept, attributes, and *each* node can have attributes

colors (and more) in mkiv are implemented using attributes and therefore 
things behave a bit different

i'm still not sure what mkiv should provide, since both methods have 
their (dis)advantages

and so it may not come as a surprise that there is some hackery around 
this compatibility issue ..

% engine=luatex

\setupcolors[state=start]

\enableattributeinheritance
\starttext

\newbox\TESTbox \setbox\TESTbox\hbox{Silence is sexy.}

\hbox{\color[red]{Silence is sexy.}{\color[blue]{Silence is sexy.}}}

\hbox{\color[red]{\attributedcopy\TESTbox}\color[blue]{\attributedbox\TESTbox}}

\stoptext

i may reimplement this at some point using the new attr feature that 
comes with boxes (i had no time yet)

when testing this a few minutes ago, i found out that this mechanisms 
was disabled; i uploaded a beta that should work ok

it will take a while before such thinsg are sorted out, esp because 
there is no best way, most logical approach, no method that makes most 
sense (which is also why it's left to macro packages to deal with it)

(btw, this phenomena is mentioned in mk.pdf, of which there is an 
updated version)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2007-12-26 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 13:31 Peter Rolf
2007-12-25 13:57 ` Arthur Reutenauer
2007-12-25 14:02 ` Wolfgang Schuster
2007-12-25 14:36 ` Gour
2007-12-25 19:44 ` luigi scarso
2007-12-25 21:04   ` Gour
2007-12-26 19:12 ` Hans Hagen [this message]
2007-12-27 10:26   ` Peter Rolf
2007-12-25 21:47 Vyatcheslav Yatskovsky

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=4772A7B7.4000802@wxs.nl \
    --to=pragma@wxs.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).