All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai-Uwe Behrmann <ku.b-list@gmx.de>
To: James Cloos <cloos@jhcloos.com>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] pwgtoraster vs calibrated spaces
Date: Thu, 05 Jun 2014 13:59:08 +0200	[thread overview]
Message-ID: <53905B8C.5090906@gmx.de> (raw)
In-Reply-To: <m3k38v1zg7.fsf@carbon.jhcloos.org>

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

Am 05.06.2014 11:23, schrieb James Cloos:
>>>>>> "KB" == Kai-Uwe Behrmann <ku.b-list@gmx.de> writes:
> KB> Data Color Space: Unknown 'sGra' = 73477261
>
> So Data Color Space is a 32bit int, then?

Yes, big endian.
http://www.color.org/ICC_Minor_Revision_for_Web.pdf
6.1.5 Color Space signature
grayData
'GRAY'
47524159h
uInt32Number

>
> Fixed.
>
> As I wrote, I based this on the xml conversion of the sRGB shipped with
> Argyll.
>
> Are the viewingConditionsType and measurementType sections of value?

Not many software uses these tags. Can not test. Otherwiese they should
be fine in plain copying.

kind regards
Kai-Uwe

[-- Attachment #2: Type: text/html, Size: 2524 bytes --]

      reply	other threads:[~2014-06-05 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  9:30 [Printing-architecture] pwgtoraster vs calibrated spaces James Cloos
2014-06-02  1:29 ` James Cloos
2014-06-02 11:53   ` Michael Sweet
2014-06-02 18:24     ` James Cloos
2014-06-02 18:34       ` Michael Sweet
2014-06-02 19:04         ` James Cloos
2014-06-03  0:44           ` James Cloos
2014-06-03  2:49             ` Chris Murphy
2014-06-03 11:51             ` Kai-Uwe Behrmann
2014-06-03 17:15               ` Chris Murphy
2014-06-05  9:23               ` James Cloos
2014-06-05 11:59                 ` Kai-Uwe Behrmann [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=53905B8C.5090906@gmx.de \
    --to=ku.b-list@gmx.de \
    --cc=cloos@jhcloos.com \
    --cc=printing-architecture@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.