From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Steffen Wolfrum via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: never add a hyphen to break a URL
Date: Tue, 25 Oct 2022 18:15:05 +0200 [thread overview]
Message-ID: <c58cf641-ea02-5c7c-ffd4-df1ed8cda6d5@gmx.es> (raw)
In-Reply-To: <B5CCD490-C48C-4882-85D1-D13C632B591E@st.estfiles.de>
On 10/25/22 12:11, Steffen Wolfrum via ntg-context wrote:
> [...]
> …. strange, on my machine your example doesn't open the link.
>
> Please have a look here: only the last one («works …») opens the link. Why?
URIs only accept letters belonging to the US-ASCII
(https://datatracker.ietf.org/doc/html/rfc3986#section-2.3).
Other ones (such as "ö") have to be escaped. This is why only the sample
containing the escaped "ö" (as "%C3%B6" [which TeX needs to escape
again]) worked for you.
It seems that depending on the PDF viewer (and I guess the browser),
unescaped chars in URIs are a must or not.
I’m using Evince and SumatraPDF (with Wine). Firefox opens the links
fine (even using its internal viewer).
Maybe Acrobat is more picky when passing unescaped chars in URIs.
I hope it might help,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-10-25 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:54 Steffen Wolfrum via ntg-context
2022-10-24 18:04 ` Pablo Rodriguez via ntg-context
2022-10-25 9:05 ` Steffen Wolfrum via ntg-context
2022-10-25 9:47 ` Hans Hagen via ntg-context
2022-10-25 10:11 ` Steffen Wolfrum via ntg-context
2022-10-25 16:15 ` Pablo Rodriguez via ntg-context [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=c58cf641-ea02-5c7c-ffd4-df1ed8cda6d5@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).