ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: Tomas Hala <tomas.hala@mendelu.cz>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Questions to PDF/A compliant documents: missing ICC files?
Date: Mon, 18 Jun 2018 09:35:49 -0600	[thread overview]
Message-ID: <20180618093549.6f67923a@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <20180618152015.GA26014@akela.mendelu.cz>

On Mon, 18 Jun 2018 17:20:15 +0200
Tomas Hala <tomas.hala@mendelu.cz> wrote:

> Hi all,
> 
> at http://wiki.contextgarden.net/PDF/A I found the following:
> 
> """""
> In ConTeXt mkiv, in order to create such a compliant PDF/A file, one
> can do as follows: first install (or check that they are present) the
> following color profiles files
> 
> default_cmyk.icc 
> default_gray.icc 
> default_rgb.icc
> ISOcoated_v2_300_eci.icc
> 
> into tex/texmf-context/colors/icc/profiles of your Context standalone
> directory. The default_*.icc files are part of ghostscript... """""
> 
> So I checked that they are present (CentOS 6.6, GPL Ghostscript 8.70)
> and I discovered that these files are not present at any ConTeXt (or
> TeX) installation from TeXlive neither as separate files, nor at file
> context/colors/icc/context/colorprofiles.xml. 
> 
> Only default_gray.icc is present as a part of ConTeXt installations
> from our garden.
> 
> Therefore, I would like to ask
> (a) where I can find the set of original default*.icc files,


/usr/local/share/color/icc/ghostscript
on my system...



> (b) what is the reason why these files are not included in the
> TeXlive and garden installations, (c) if it is possible to add it
> there for future, and (d) if the produced PDF (with
> \setupbackend[format={pdf/a-1b:2005}...]) is PDF/a compliant when
> these icc files are not present and the whole content of the document
> is only in black (i.e. no grayscale, no colours).
> 
> Our university decided to be "PDF/a compliant", that is the reason
> why I am asking.
> 
> Best wishes,
> 
> Tomáš
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-06-18 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 15:20 Tomas Hala
2018-06-18 15:35 ` Alan Braslau [this message]
2018-06-18 16:13 ` luigi scarso
2018-06-18 16:48 ` Pablo Rodriguez
2018-06-18 21:38 ` Henri Menke
2018-07-20 15:05   ` Questions to PDF/A compliant documents: missing ICC files? -- II Tomas Hala
2018-07-20 19:24     ` Hans Hagen
2018-07-26  7:34       ` Tomas Hala
2018-07-26  8:27         ` Hans Hagen

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=20180618093549.6f67923a@poo.hsd1.co.comcast.net \
    --to=braslau.list@comcast.net \
    --cc=ntg-context@ntg.nl \
    --cc=tomas.hala@mendelu.cz \
    /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).