<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hello Edmund,<br>
    Your described workflow is part of my proposal described here:<br>
    <a class="moz-txt-link-freetext"
      href="http://www.freedesktop.org/wiki/OpenIcc/ColorMangedPrintingPath">http://www.freedesktop.org/wiki/OpenIcc/ColorMangedPrintingPath</a>
    <br>
    <br>
    It would be nice to get some comments on this proposal.<br>
    <br>
    best regards<br>
    Jan-Peter<br>
    <br>
    Am 09.05.11 11:38, schrieb edmund ronald:
    <blockquote
      cite="mid:BANLkTimGb-pJzyjLVtbJfWtnA8vv-yFU2A@mail.gmail.com"
      type="cite">Ok, here is a use case:
      <div><br>
      </div>
      <div>&nbsp;I am a hobby photographer, or an art printing service
        house.&nbsp;</div>
      <div>&nbsp;I get in some &nbsp;new heavy Acme media which looks nice but
        looks like it will soak up more ink than what I am using.</div>
      <div>&nbsp;I set the CPD to "Epson Heavy Matte" and indeed when it
        prints with the associated profile black is not yet really
        black.&nbsp;</div>
      <div>&nbsp;So I go to the "advanced" CPD tab, increase density, save
        the setting back out under "Acme Super Heavy Matte", and print a
        profile target, check that on target blacks are black, run a
        profile, use the advanced CPD to associate the profile with the
        new settings, and now "Acme Super Heavy Matte" can be used
        without complication from the "simple printing" tab of the CPD.&nbsp;<br>
      </div>
      <div><br>
      </div>
      <div>Edmund</div>
      <div><br>
      </div>
      <div><br>
        <div class="gmail_quote">On Mon, May 9, 2011 at 3:52 AM, Robert
          Krawitz <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rlk@alum.mit.edu">rlk@alum.mit.edu</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            <div class="im">On Mon, 09 May 2011 11:48:08 +1000, Graeme
              Gill wrote:<br>
              &gt; Robert Krawitz wrote:<br>
              &gt;&gt; I don't agree with this reasoning. &nbsp;I think it's
              important to have all<br>
              &gt;&gt; such options available from all programs with a
              print dialog; we<br>
              &gt;&gt; should figure out how to present them most
              effectively.<br>
              &gt;<br>
              &gt; My view is both to agree and disagree: I think that
              the ability to<br>
              &gt; setup a printer is something that should be put in
              well tested and<br>
              &gt; maintained code paths and be universally available,
              rather than<br>
              &gt; relegated to "optional" component that will probably
              fall into<br>
              &gt; disrepair, or make it hard to access or be
              inconsistent with the<br>
              &gt; normal printing path.<br>
              &gt;<br>
              &gt; On the other hand, I don't see anybody changing such
              detailed<br>
              &gt; settings arbitrarily on a print by print basis. The
              practical way of<br>
              &gt; handling printer setup is with a labelled
              configuration. The<br>
              &gt; configuration choice would be what can be set from
              the normal<br>
              &gt; printing dialogue, while creating or altering a
              configuration would<br>
              &gt; be a separate step "edit/create printer
              configuration". Where such<br>
              &gt; configuration information would be kept, and the
              method for<br>
              &gt; accessing and changing it is an interesting technical<br>
              &gt; question. Ideally it should be a remotely available
              operation, so<br>
              &gt; that creating or examining printing configurations
              can be done from<br>
              &gt; any place that you can print a document from,
              accessible from the<br>
              &gt; usual printer information GUI.<br>
              <br>
            </div>
            I have no problem with that. &nbsp;After all, if you really need
            to, you<br>
            can create a new configuration from the editor.<br>
            <div>
              <div class="h5">_______________________________________________<br>
                openicc mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.freedesktop.org/mailman/listinfo/openicc"
                  target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
openicc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/openicc">http://lists.freedesktop.org/mailman/listinfo/openicc</a></pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
----------  Please note the new adress --------------

homann colormanagement --------- fon +49 30 611 075 18
Jan-Peter Homann ------------ mobile +49 171 54 70 358
Cotheniusstr. 3 -------- <a class="moz-txt-link-freetext" href="http://www.colormanagement.de">http://www.colormanagement.de</a>
10407 Berlin -------- <a class="moz-txt-link-freetext" href="mailto:homann@colormanagement.de">mailto:homann@colormanagement.de</a>

</pre>
  </body>
</html>