From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue attaching remote files
Date: Mon, 4 Nov 2019 19:02:25 +0100 [thread overview]
Message-ID: <13e7dc87-1648-fbc8-a011-c785256c5b06@xs4all.nl> (raw)
In-Reply-To: <055ce527-ca94-1e0d-ce40-2f21ea321dce@gmx.es>
On 11/4/2019 6:26 PM, Pablo Rodriguez wrote:
> Hi Hans,
>
> I have the following sample:
>
> \setupinteraction[state=start]
> \starttext
> \startTEXpage[offset=1em]
> \attachment
> [file={https://eur-lex.europa.eu/legal-content/%
> ES/TXT/PDF/?uri=CELEX:02010L0040-20180109},
> name=one.pdf,
> color=orange]
> \attachment
> [file={https://eur-lex.europa.eu/legal-content/%
> ES/TXT/PDF/?uri=CELEX:52011DC0144R(02)},
> name=two.pdf,
> color=magenta]
> \stopTEXpage
> \stoptext
>
> Because of the parentheses in the file address, the second file isn’t
> attached, due to the use of parentheses (sorry, but I cannot avoid this
> in their address).
>
> curl is also unable to download the second file unless an output name is
> specified (with --output or -o).
>
> Would it be possible that ConTeXt could handle the second address with
> parentheses to attach the file to a PDF document?
hm i see both files in the cache (under trees)
i also see both embedded
btw these are weird files (1) pdf 1.4 which afaik doesn't permit tags,
(2) imo invalid object references are used, (3) the files are pretty
inefficient, and let's not talk about how bad they look (ok, that is of
course subjective, but still ... a kind of braindead job for tex to
generate such files)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-04 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:26 Pablo Rodriguez
2019-11-04 18:02 ` Hans Hagen [this message]
2019-11-05 7:16 ` Pablo Rodriguez
2019-11-05 8:42 ` Hans Hagen
2019-11-05 13:42 ` Pablo Rodriguez
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=13e7dc87-1648-fbc8-a011-c785256c5b06@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).