From: Antero Mejr via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63531@debbugs.gnu.org
Subject: bug#63531: [PATCH] View DICOM and Sixel images using image-convert
Date: Tue, 16 May 2023 17:38:06 +0000 [thread overview]
Message-ID: <87ttwcrxc1.fsf@mailbox.org> (raw)
In-Reply-To: <871qjgtc37.fsf@mailbox.org> (Antero Mejr's message of "Tue, 16 May 2023 17:34:04 +0000")
Antero Mejr <antero@mailbox.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Mon, 15 May 2023 23:30:13 +0000
>>> From: Antero Mejr via "Bug reports for GNU Emacs,
>>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>>
>>> These patches add .dcm and .six to auto-mode-alist, so they can be
>>> viewed with image-convert. The Six patch also adds SIX as an ImageMagick
>>> type.
>>
>> Do we want to include their support in Emacs? AFAIU, these aren't
>> free formats.
>
> I'm not an lawyer but to the best of my knowledge neither format has any
> sort of licensing, trademark, or patent encumberances.
>
> DICOM is free to implement and view without licenses. The specification
> is available online but the spec itself is copyright of NEMA. It's a
> metadata wrapper over JPEG mainly.
>
> I think the Sixel "format" is more of a simple convention than a formal
> specification with licenses, patents, etc. Implementations use the DEC
> VT330 manual as a "spec" I guess.
>
>> And since supporting them boils down to customizing
>> auto-mode-alist, why cannot users do that themselves?
>
> For usability I think it's good for things to (mostly) work out of the
> box.
Forgot to CC the mailing list, sorry.
next prev parent reply other threads:[~2023-05-16 17:38 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 [this message]
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
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=87ttwcrxc1.fsf@mailbox.org \
--to=bug-gnu-emacs@gnu.org \
--cc=63531@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=eliz@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).