unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Antero Mejr via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 63531@debbugs.gnu.org
Subject: bug#63531: [PATCH] View DICOM and Sixel images using image-convert
Date: Thu, 02 Nov 2023 17:06:52 +0000	[thread overview]
Message-ID: <87cyws5bkj.fsf@mailbox.org> (raw)
In-Reply-To: <CADwFkmkakvO30Gmxnnm7p2J88xim7x7eOpH71PHpo_sRHNCTeQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 22 Oct 2023 11:36:44 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> Since these formats are not encumbered by patents and so on, I don't see
> any reason why we can't support them.  It's always nice if stuff like
> that works OOTB.
>
> So I think we should install these patches.

I agree, both are popular formats so it would be good to support them.
I did another check regarding the licenses, hopefully it will address
the previous concerns.

The DICOM standard committee website explicitly states:
"No license is required to download or implement the DICOM Standard."
https://www.dicomstandard.org/patent

For Sixel, we already use the DEC VTxxx manuals for terminal emulation,
see the "References" comment on line 2975 of term.el. The Sixel file
format reference comes from the same sources.

Thanks,
Antero





  reply	other threads:[~2023-11-02 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 23:30 bug#63531: [PATCH] View DICOM and Sixel images using image-convert Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-16 16:23 ` Eli Zaretskii
     [not found]   ` <871qjgtc37.fsf@mailbox.org>
2023-05-16 17:38     ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22 18:36       ` Stefan Kangas
2023-11-02 17:06         ` Antero Mejr via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-21 13:28           ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22  3:07           ` Stefan Kangas

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=87cyws5bkj.fsf@mailbox.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63531@debbugs.gnu.org \
    --cc=antero@mailbox.org \
    --cc=eliz@gnu.org \
    --cc=stefankangas@gmail.com \
    /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).