ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Erik Margraf <erik.margraf@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Colors: printing vs. on screen
Date: Tue, 21 Jun 2011 22:28:32 +0200	[thread overview]
Message-ID: <BANLkTinJw64Uczzd329JH6Rt_s9Ytnzdgg@mail.gmail.com> (raw)
In-Reply-To: <381341F6-C924-44F8-9BE5-A741F084756E@fiee.net>


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

Thanks! I'll go for the calibration and some trials in CMYK colors for
printing.

kind regards
Erik

2011/6/19 Henning Hraban Ramm <hraban@fiee.net>

> Yes, because your monitor uses RGB and your printer uses CMYK. The
>> conversion between thetwo is not too complicated, but actually getting the
>> same output from the two is hard. RGB is an additive model, CMYK is
>> subtractive (read about the different models, wikipedia will do). The color
>> impression you get by looking at the output is generated in completely
>> different ways.
>>
>
> Most office printers cope well with RGB (sRGB) colors, a lot of inkjet
> printers even better than with CMYK colors, because they're optimized for
> home dummy use.
>
> But (as Christoph pointed out) your printer can be as great as it goes,
> you'll never get a similar color impression if your monitor's set to some
> extreme setting - and most monitors that I saw outside of the graphical
> branch are set to "nonsense" settings, e.g. max contrast.
>
> Greetlings from Lake Constance!
> Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
>
> ______________________________**______________________________**
> _______________________
> 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 <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/<http://foundry.supelec.fr/projects/contextrev/>
> wiki     : http://contextgarden.net
> ______________________________**______________________________**
> _______________________
>

[-- Attachment #1.2: Type: text/html, Size: 2790 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:[~2011-06-21 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 11:53 Erik Margraf
2011-06-19 12:03 ` Hans Hagen
2011-06-19 12:08 ` Christoph Redecker
2011-06-19 19:33   ` Henning Hraban Ramm
2011-06-21 20:28     ` Erik Margraf [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=BANLkTinJw64Uczzd329JH6Rt_s9Ytnzdgg@mail.gmail.com \
    --to=erik.margraf@googlemail.com \
    --cc=erik.margraf@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).