From: Henning Hraban Ramm <angerweit@gmx.net>
Cc: ntg-context@ntg.nl
Subject: Re: colorizing
Date: Sat, 2 Feb 2002 19:44:19 +0100 [thread overview]
Message-ID: <200202021844.g12IiJf07965@nathir.fiee.lan> (raw)
In-Reply-To: <5.1.0.14.1.20020129205315.02b02f68@server-1>
Am Dienstag, 29. Januar 2002 21:01 schrieb Hans Hagen:
> >e.g. I use a bitmap logo that should show exactly the same color as
> > defined for backgrounds. If I define the "same" color with PhotoShop it
> > looks
> ah, so it's tuned for some kind of paper
I switched off all color management and used absolute measures.
I "solved" the problem with a clip path. And I was surprised that Photoshop 6
isn't able to write a spot color bitmap as PDF -- I know such is possible, at
least with PDF 1.4 -- another disappointment by Adobe.
> ...; btw: quite funny to be able to search for invisible text).
That feature is for scanned documents with OCR'ed text. Some firms or boards
use PDF to archive their documents...
> >It should as easy as in other functions to assign foreground and
> > background color, maybe even transparency?
>
> when i browsed the specs some time ago i got the impression that this is
> doable, but so far i didn't need it (although i will probably need it
> soon). Building ther sources is trivial (once i understand it) and we can
> probably hook things into the resource dict of graphics, but cooking up a
> proper interface will take me some time. We can look into the specs at the
> coming dante meeting to see what can be done.
Uäh, specs... ;-(
;-)
Grüßlis vom Hraban!
next prev parent reply other threads:[~2002-02-02 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 17:17 colorizing Henning Hraban Ramm
2002-01-29 20:01 ` colorizing Hans Hagen
2002-02-02 18:44 ` Henning Hraban Ramm [this message]
2002-02-03 18:22 ` colorizing Hans Hagen
2002-02-04 19:19 ` colorizing specs Henning Hraban Ramm
2002-02-05 8:39 ` Hans Hagen
2002-02-05 17:25 ` Henning Hraban Ramm
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=200202021844.g12IiJf07965@nathir.fiee.lan \
--to=angerweit@gmx.net \
--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).