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: Bug with overprinting in Mark II/IV?
Date: Fri, 11 Dec 2009 18:19:05 +0100	[thread overview]
Message-ID: <4B227F09.9000602@wxs.nl> (raw)
In-Reply-To: <fe8d59da0912110842r218e4799i41f0622f6b783c23@mail.gmail.com>

luigi scarso wrote:
> On Fri, Dec 11, 2009 at 5:37 PM, Oliver Heins <olli@sopos.org> wrote:
>> Hi Luigi,
>>
>> luigi scarso <luigi.scarso@gmail.com> writes:
>>
>>> hm I believed  was
>>>
>>> \color[red]{......}
>>>
>>> and
>>> \startcolor[red]
>>> ...
>>> \stopcolor
>> You're right, I mixed things up here.  But nontheless, my example was
>> (unintendedly) syntactically correct, because either \color[black]{\bf
>> ...} and \color[black]\startoverprint ... \stopoverprint define a
>> block. :-)
> ok, just to be sure : can you rewrite in a correct way ?
> Can be a problem with mkii .

overprint and similar features will not change in mkii

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


      parent reply	other threads:[~2009-12-11 17:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 12:53 Oliver Heins
2009-12-11 13:40 ` Peter Rolf
2009-12-11 13:53   ` Taco Hoekwater
2009-12-11 14:41     ` Peter Rolf
2009-12-11 16:32   ` Oliver Heins
2009-12-11 17:35     ` Peter Rolf
2009-12-11 17:57       ` Oliver Heins
2009-12-11 18:18         ` luigi scarso
2009-12-11 18:23         ` Peter Rolf
2009-12-12 15:41           ` Oliver Heins
2009-12-12 15:46             ` Martin Schröder
2009-12-12 16:17             ` Hans Hagen
2009-12-12 17:43               ` Oliver Heins
2009-12-13 15:20             ` Peter Rolf
2009-12-11 14:07 ` luigi scarso
2009-12-11 16:37   ` Oliver Heins
2009-12-11 16:42     ` luigi scarso
2009-12-11 17:00       ` Oliver Heins
2009-12-11 17:19       ` Hans Hagen [this message]

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=4B227F09.9000602@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).