From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CMYK comparison to sRGB between platforms
Date: Wed, 9 Sep 2015 20:06:38 -0400 [thread overview]
Message-ID: <CAGfcS_=tUjJyGDhhcxRH026bao=YoHq=ZxvR0bKL2gBhKpKVFg@mail.gmail.com> (raw)
In-Reply-To: <201509081942.10580.michaelkintzios@gmail.com>
On Tue, Sep 8, 2015 at 2:42 PM, Mick <michaelkintzios@gmail.com> wrote:
> On the same hardware I noticed that a CMYK photograph converted to sRGB looked
> mostly the same (indistinguishable) on Linux, but the sRGB colours were
> brighter on MSWindows.
>
If everything is working correctly then the CMYK original and sRGB
copy should look identical, with the exception of any out-of-gamut
colors (as I understand it, very little of CYMK is out-of-gamut for
sRGB).
If they're not identical then something is wrong, so I wouldn't assume
that Linux is at fault (though it could be if the file looks wrong
when created on Linux and viewed on another OS, and both OSes are
using calibration).
Imagine if your original email read like this:
On the same hardware I noticed that when I saved my simple OpenOffice
document in MS Word format in Linux, and then opened the MS Word file,
the text was identical. I tried doing the same thing on both Windows
and OSX and in both cases there were lots of weird symbols in the text
of the document. What is wrong with my Linux OpenOffice program? Why
doesn't it mke my dcment lok lik ths like the other OSes?
or like this:
On the same hardware I noticed that when I copied a file from a fat32
USB stick to an ext4 USB stick the md5sum of the files remained
unchanged. However, if I perform the copy on OSX or Windows the
md5sum changes. What is wrong with my linux filesystem drivers? Why
doesn't it randomly modify my data when I try to copy it? And, darn
it, why does it seem like I never have to reboot the thing to keep it
from crashing?
Now if one OS or another isn't properly calibrated to your monitor the
same file could have different appearances, and if for whatever reason
your viewer for the CYMK file applies calibration data differently
than the viewer for the sRGB file that would also cause issues. So,
the problem might be in the viewing of the files, or in the
conversion. Based solely on the testing you performed I can't really
be sure which if any of your conversions are being done correctly.
The file might appear unchanged on Linux but it could be a result of
cancelling errors in the creation and rendering of the file.
However, since the whole goal of the conversion process is to avoid
making visible changes to the file to the greatest degree possible,
I'd tend to look at the other OSes for problems first.
--
Rich
next prev parent reply other threads:[~2015-09-10 0:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 18:42 [gentoo-user] CMYK comparison to sRGB between platforms Mick
2015-09-08 22:49 ` wraeth
2015-09-09 5:52 ` Mick
2015-09-09 8:28 ` Peter Humphrey
2015-09-09 13:41 ` Mick
2015-09-09 23:40 ` Peter Humphrey
2015-09-10 10:06 ` Peter Humphrey
2015-09-10 0:06 ` Rich Freeman [this message]
2015-09-10 21:07 ` wabenbau
2015-09-26 15:11 ` Mick
2015-09-27 8:58 ` Peter Humphrey
2015-09-27 9:47 ` Mick
2015-09-27 10:50 ` Peter Humphrey
2015-09-27 11:36 ` Mick
2015-09-28 8:42 ` Peter Humphrey
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='CAGfcS_=tUjJyGDhhcxRH026bao=YoHq=ZxvR0bKL2gBhKpKVFg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/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