From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Max Chernoff <mseven@telus.net>
Subject: Re: remote images
Date: Mon, 03 Oct 2022 23:35:11 -0600 [thread overview]
Message-ID: <b2008aafef584d215caf03860d12529f0a9686bf.camel@telus.net> (raw)
In-Reply-To: <e9238573-8b4e-fc6e-bc22-fd3f08c940a1@fiee.net>
Hi Hraban,
> fetching images per URI was supported (and is also documented in the
> wiki), but with LMTX 2022.09.11 and one of
>
> \externalfigure[http://tug.org/images/logobw.jpg]
> or
> \externalfigure[https://picsum.photos/300/200]
>
> I only get the usual grey box. No error message.
Neither of those links are valid images themselves, they are both
redirects. The following works though:
\starttext
\externalfigure[https://tug.org/images/logobw.jpg]
\stoptext
I can't seem to get the second one to work since its redirected URL is a
bit odd.
> Do I need any setup, was this discarded in LMTX, or what’s wrong?
I have no idea if ConTeXt would ever follow redirects before, but I
agree that it would be a useful feature.
Thanks,
-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-10-04 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 10:28 Henning Hraban Ramm via ntg-context
2022-10-04 5:35 ` Max Chernoff via ntg-context [this message]
2022-10-04 6:16 ` Henning Hraban Ramm via ntg-context
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=b2008aafef584d215caf03860d12529f0a9686bf.camel@telus.net \
--to=ntg-context@ntg.nl \
--cc=mseven@telus.net \
/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).