From: Hajtmar Jaroslav <hajtmar@gyza.cz>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Problem with PNG images in the latest standalone version
Date: Fri, 24 May 2024 11:48:21 +0000 [thread overview]
Message-ID: <DC772021-CB10-4A76-B3EA-7203F8D555D7@gyza.cz> (raw)
In-Reply-To: <94e50fd9-ad95-15af-4a99-bd83f751579b@gmail.com>
Hello, thanx for reply.
PNG and JPG files are available at the URL given, as well as PDF documents with the compilation results. The old ConTeXt seems to be able to embed PNGs from the local disk, but no longer from a remote address.
The new ConTeXt handles both local and remote PNG image in different ways.
Thanx Jaroslav
\setupinteraction[state=start]
\starttext
JPG URL:
\externalfigure[https://hajtmar.cz/temp-ntg/gyzalogo-new.jpg][height=3.5cm]
\par
JPG local:
\externalfigure[gyzalogo-new.jpg][height=3.5cm]
\par
PNG URL:
\externalfigure[https://hajtmar.cz/temp-ntg/gyzalogo-new.png][height=3.5cm]
\par
PNG local file:
\externalfigure[gyzalogo-new.png][height=3.5cm]
\par
Results:
\par
\goto{PDF file by ConTeXt ver: 2024.05.17}[url(https://hajtmar.cz/temp-ntg/minimalexample20240517.pdf)]
\par
\goto{PDF file by ConTeXt ver: 2018.04.04}[url(https://hajtmar.cz/temp-ntg/minimalexample20180404.pdf)]
\stoptext
> 24. 5. 2024 v 9:17, Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
> Thangalin schrieb am 24.05.2024 um 07:56:
>> Hajtmar, please provide a complete, self-contained, minimal working example.
>
> Yes, a example and the problematic images are needed because a simple test with mill.png which is part of ConTeXt shows no problems but image formats are more complex than Hajtmar believes.
>
> \setupexternalfigure[location=default]
>
> \starttext
> \externalfigure[mill]
> \stoptext
>
> Wolfgang
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-05-24 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 22:39 [NTG-context] " Hajtmar Jaroslav
2024-05-24 5:56 ` [NTG-context] " Thangalin
2024-05-24 7:17 ` Wolfgang Schuster
2024-05-24 11:48 ` Hajtmar Jaroslav [this message]
2024-05-24 13:22 ` Wolfgang Schuster
2024-05-24 17:44 ` Hajtmar Jaroslav
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=DC772021-CB10-4A76-B3EA-7203F8D555D7@gyza.cz \
--to=hajtmar@gyza.cz \
--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).