ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <schultzk@uni-trier.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Change the default text colour for entire document
Date: Mon, 27 Jan 2014 12:30:31 +0100	[thread overview]
Message-ID: <17542E07-8FBF-4253-8649-D438DA9E3F5F@uni-trier.de> (raw)
In-Reply-To: <52E63E95.4000808@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 3524 bytes --]

Hi Everybody,

If I remember right colors can be defined in ConTeXt, right?

So why not just redefine black!

If this is stupid, the defaults get initialize before a redefined occurs!

forget it!

Just a stupid simplistic idea!

regards
	Keith.
 
Am 27.01.2014 um 12:10 schrieb Hans Hagen <pragma@wxs.nl>:

> On 1/27/2014 12:24 AM, Wolfgang Schuster wrote:
>> 
>> Am 22.01.2014 um 02:15 schrieb Thangalin <thangalin@gmail.com>:
>> 
>>> Hi,
>>> 
>>> In ConTeXt to change the default text colour for the entire document,
>>> there are at least two settings that need to be configured:
>>> 
>>>  \setupcolors[textcolor=red]
>>>  \setupinmargin[line=13,color=red,style=slanted,]
>>> 
>>> The border colour for tables remains black:
>>> 
>>> \setupcolors[textcolor=red]
>>> \setupinmargin[color=red]
>>> 
>>> \starttext
>>> {\bTABLE
>>> \bTR \bTD One \eTD \bTD Two \eTD \eTR
>>> \eTABLE}
>>> \stoptext
>>> 
>>> How can you override *all* instances of black? (Ideally there would be
>>> a single setting that is inherited by all.) That is, it is difficult
>>> to know all the various aspects of a ConTeXt document that use the
>>> default black colour -- margins, body text, table borders, and
>>> possibly more that I don't know about.
>> 
>> Notes (local notes excluded because they use a different placement system)
>> and margin texts ignore the global text color because both mechanism reset
>> colors and many other settings to avoid unwanted output from local changes
>> in the main text etc.
>> 
>> Even though there is a comment about this problem for margin notes in
>> the source it wasn’t fixed yet but I think it makes sense to to so.
> 
> \appendtoks
>    \inheritmaintextcolor
> \to \everybeforenoteinsert
> 
> \appendtoks
>    \inheritmaintextcolor
> \to \everymargindatacontent
> 
> could work, but it needs testing as we cannot predict side effects
> 
>> The problem with the black frames for natural tables are a result of the explicit
>> framecolor setup for it (I guess to avoid problems when you use metapost
>> backgrounds which use the framecolor value). A possible way to fix this is to
>> add a framecolor setup to \setupcolors which argument is now used as default
>> color for the frame of natural tables, this way can use this color also in other
>> commands (core functions as well as third party modules) to set a default value.
> 
> needs some thinking
> 
> \setupTABLE
>  [framecolor=\maintextcolor]
> 
> some settings date from mkii times but again we need to think of side effects
> 
> Hans
> 
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>    tel: 038 477 53 69 | voip: 087 875 68 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 5494 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2014-01-27 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  1:15 Thangalin
2014-01-26 23:24 ` Wolfgang Schuster
2014-01-27 11:10   ` Hans Hagen
2014-01-27 11:30     ` Keith J. Schultz [this message]
2014-01-27 11:45       ` Thangalin

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=17542E07-8FBF-4253-8649-D438DA9E3F5F@uni-trier.de \
    --to=schultzk@uni-trier.de \
    --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).