unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David.Kastrup@t-online.de (David Kastrup)
Cc: emacs-devel@gnu.org
Subject: Re: PNG pictures have gamma correction twice applied
Date: Sat, 30 Nov 2002 14:36:14 +0100	[thread overview]
Message-ID: <200211301336.gAUDaEU9005748@localhost.localdomain> (raw)
In-Reply-To: E18BBfs-0002H9-00@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

> Would you like to rewrite the png code thoroughly?

Unfortunately, it is not just the PNG code, it is the entire
color/image management that is involved here.

> If only the png library does its own gamma correction, it would seem
> Emacs should still do gamma correction for images itself.  But perhaps
> it can do that in a more efficient way.
> 
>     nowadays), the whole pixel lookup and color allocation business is
>     utterly unnecessary, anyway, since one can directly map requested
>     color to available color
> 
> We could keep the ability to do the lookup but use it only on
> devices where it is needed.
> 
> Anyway, please do clean up this mess.

It probably would not be the best idea to separate color handling of
text and images too much, or we will not be able to have images blend
seamlessly into the background of the buffer, the images being
rendered to a different palette part than the "exact match" colors.

Anyhow, the way I see it there is not much sense in reinventing the
wheel.  This sort of color management is rather tedious to do in X11,
and the work has been done already.  For example, the Gdk library
deals with all sorts of different color models, and there is even a
Windows port (avaunt!) available if I am not mistaken.

So it would make sense either to use Gdk where available, or probably
to borrow from its code base _if_ copyright issues would permit
that.

I don't know whether it would make sense to factor out the color
management into separate files, thus maybe better facilitating
exchanging one scheme for another.

Opinions?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2002-11-30 13:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200211061556.gA6FuCU6005082@localhost.localdomain>
2002-11-07 15:08 ` PNG pictures have gamma correction twice applied Richard Stallman
2002-11-09 22:40   ` David Kastrup
2002-11-11 10:20     ` Richard Stallman
2002-11-30 13:36       ` David Kastrup [this message]
2002-12-03 14:59         ` Richard Stallman
2002-12-03 15:21           ` David Kastrup
2002-12-05 15:08             ` Richard Stallman
2002-12-05 15:34               ` David Kastrup
2002-12-05 17:31               ` David Kastrup
2002-12-06 15:52                 ` Richard Stallman
2002-12-06 16:01                   ` David Kastrup
2002-11-11 16:58     ` Stefan Monnier
2002-11-11 17:30       ` David Kastrup
2002-11-11 17:43         ` Stefan Monnier
2002-11-18 11:31           ` David Kastrup

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200211301336.gAUDaEU9005748@localhost.localdomain \
    --to=david.kastrup@t-online.de \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).