From: Jim <zlists+context@jdvb.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: JPEG 2000 extensions
Date: Sat, 11 Jan 2025 10:54:22 -0400 [thread overview]
Message-ID: <Z4KGHpnrNhkOmYGQ@x360.localdomain> (raw)
In-Reply-To: <d81238c5-1447-41e6-a508-73a4096b4963@xs4all.nl>
Hi Hans,
On Sat, Jan 11, 2025 at 11:48 (+0100), Hans Hagen wrote:
> On 1/11/2025 1:47 AM, Jim wrote:
>> Hi,
>> in .../tex/texmf-context/tex/context/base/mkiv/grph-inc.lua I see (at line
>> 333)
>> ["jp2"] = { list = { "jp2" } },
>> That is (AIUI) the proper extension for JPEG2000 (Part 1) images.
>> The JPEG2000 (Part 2) images I looked at have the same magic bytes as
>> listed in line 349 of that file.
>> AIUI, JPEG2000 (Part 2) images should have the extension .jpx. Is it
>> possible to change line 333 to read
>> ["jp2"] = { list = { "jp2", "jpx" } },
>> ?
>> (I hope this is the only change needed.)
>> I may be the only (vocal) person using .JPX files right now, but in the
>> years to come, who knows how many people will use it?
>> Thanks.
>> Jim
>> P.S. I know that I can use
>> \definegraphictypesynonym [jpx] [jp2]
>> but in the interest of helping others who may run into this issue in
>> the future, ...
> did you check if pdf viewers can handle both? or is it just a suffix issue
All the PDF viewers (and other tools) I tried can handle JPX files. These
include
- (ancient) Adobe acroread for Linux
- evince
- kpdf
- firefox and chromium's PDF viewers
- emacs' pdfview
- xpdf
- diffpdf
- ghostview
- mupdf
- qpdfview
- okular
- zathura
- xournal
- xournalpp
Admittedly, the list isn't exhaustive, but large enough that I think it
makes sense to provide support for JPX.
It is more than a suffix issue, as (for example) the "file" program knows
the different between Part 1 and Part 2 versions of JPEG2000 files.
Further, the tool I access to create Part 2 images from (ordinary) JPEGs
creates considerably smaller images than the tools I have to create Part 1
images (with no apparent loss of quality). I do not know enough about the
differences to comment on the likelihood that a viewer will handle Part 1
but not Part 2, but I can say I haven't seen such a thing yet.
(In about a year and a half of using Part 2 images in a monthly newsletter
I edit, I have only had one person complain once about not being able to
see the images; this person is known to have ancient software on his
computer, and he only mentioned it once, which makes me think he used a
different program to look at the newsletter one month.)
Cheers.
Jim
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2025-01-11 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 0:47 [NTG-context] " Jim
2025-01-11 10:48 ` [NTG-context] " Hans Hagen
2025-01-11 14:54 ` Jim [this message]
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=Z4KGHpnrNhkOmYGQ@x360.localdomain \
--to=zlists+context@jdvb.ca \
--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).