From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Jason Rumney <jasonr@gnu.org>, emacs-devel@gnu.org
Subject: Re: bad tool-bar icons in Emacs 22.1 release
Date: Sat, 30 Jun 2007 11:46:34 +0200 [thread overview]
Message-ID: <4686267A.8050001@swipnet.se> (raw)
In-Reply-To: <v9lke2zobw.fsf@marauder.physik.uni-ulm.de>
Reiner Steib skrev:
> [ Shifting this from bug-gnu-emacs to emacs-devel: ]
>
> On Mon, Jun 11 2007, Jason Rumney wrote:
>> Richard Stallman wrote:
>>> Whether distributing third party libraries from ftp.gnu.org is
>>> a good idea, or allowable, is a different question.
>>>
>>> If it is just a few libraries, it is ok as long as we check
>>> their licenses carefully to make sure we do not violate them.
>> OK. Here is the license for libxpm, which is the most important for the
>> color versions of the tool-bar and other images that are a standard part
>> of Emacs. I think including just this library is enough to satisfy most
>> users, but that is open to discussion. If others think JPEG, PNG, TIFF
>> and GIF support are important enough to include, we can look at those
>> licenses and consider patent issues (for GIF at least, I don't think the
>> patents have expired in all jurisdictions yet) separately.
PNG is important. If we want Emacs to change icons when the Gnome/Gtk+ theme
changes, Emacs will then use PNG icons. Most (all?) Gnome/Gtk+ icons are in
PNG format. But this is code that Gtk+ loads dynamically with dlopen, so
Emacs itself does not know that PNG is used. Not sure if that affects the
license issue?
Jan D.
next prev parent reply other threads:[~2007-06-30 9:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DNEMKBNJBGPAOPIJOOICKEEIDNAA.drew.adams@oracle.com>
[not found] ` <uy7iskg91.fsf@gnu.org>
[not found] ` <v9ps44uogx.fsf@marauder.physik.uni-ulm.de>
[not found] ` <uir9vk3td.fsf@gnu.org>
[not found] ` <466C80A3.1040102@gnu.org>
[not found] ` <E1HxgS3-0008No-Vm@fencepost.gnu.org>
[not found] ` <466D34C5.8050604@gnu.org>
[not found] ` <E1Hy8nK-0008Q5-Jd@fencepost.gnu.org>
2007-06-29 17:02 ` bad tool-bar icons in Emacs 22.1 release Reiner Steib
2007-06-30 9:46 ` Jan Djärv [this message]
2007-06-30 10:47 ` Reiner Steib
2007-06-30 11:48 ` Eli Zaretskii
2007-07-01 0:30 ` Richard Stallman
2007-07-01 0:36 ` Lennart Borgman (gmail)
2007-07-01 16:31 ` Richard Stallman
2007-07-01 20:39 ` Lennart Borgman (gmail)
2007-07-02 19:47 ` Richard Stallman
2007-07-02 23:30 ` Jason Rumney
2007-07-01 17:14 ` Jason Rumney
2007-07-01 9:03 ` Reiner Steib
2007-07-01 16:32 ` Richard Stallman
2007-07-02 20:22 ` Reiner Steib
2007-07-03 4:24 ` Richard Stallman
2007-07-01 20:55 ` Christian Schlauer
2007-07-02 19:47 ` Richard Stallman
2007-07-03 19:36 ` Christian Schlauer
2007-07-05 1:30 ` Richard Stallman
2007-07-23 18:54 ` Christian Schlauer
2007-06-30 15:10 ` Richard Stallman
2007-06-30 18:38 ` Stefan Monnier
2007-06-30 18:54 ` Juanma Barranquero
2007-07-01 16:31 ` Richard Stallman
2007-07-01 17:15 ` Jason Rumney
2007-07-02 0:03 ` Dieter Wilhelm
2007-07-02 6:08 ` Jan Djärv
2007-07-02 21:23 ` Dieter Wilhelm
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=4686267A.8050001@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).