From: Gwern Branwen <gwern-v26ZT+9V8bxeoWH0uzbU5w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc as a linkchecker?
Date: Sat, 12 Sep 2020 15:35:05 -0400 [thread overview]
Message-ID: <CAMwO0gyWoK_n5m0OO=-OYyT36MMAfO=XegbeJ17N5PYvNnFe0w@mail.gmail.com> (raw)
In-Reply-To: <f87a3346-3243-0cd4-a101-107e5ffe4902-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Which kinds of links? Pandoc may chase some links in order to inline
them ("linked scripts, stylesheets, images, and videos"), but that's
not most links, and trying to check hyperlinks in full generality is
quite complex and difficult (look at the complexity of what I use for
dead-link finding, https://github.com/linkchecker/linkchecker ), and
not possible in some cases.*
* Consider relative or absolute links on a website: if I link to
'/About' on a gwern.net page, that is a valid link when deployed, but
it will break for every linkchecking tool which doesn't assume that
that is relative to 'https://www.gwern.net'. How does Pandoc know
that?
--
gwern
next prev parent reply other threads:[~2020-09-12 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 19:12 Joseph Reagle
[not found] ` <f87a3346-3243-0cd4-a101-107e5ffe4902-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2020-09-12 19:35 ` Gwern Branwen [this message]
2020-09-12 19:38 ` Daniel Staal
2020-09-12 20:19 ` Albert Krewinkel
2020-09-12 20:31 ` BPJ
[not found] ` <CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-14 13:19 ` Joseph Reagle
[not found] ` <c5259326-1317-e43a-6416-25922630b25e-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2020-09-14 13:23 ` Gwern Branwen
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='CAMwO0gyWoK_n5m0OO=-OYyT36MMAfO=XegbeJ17N5PYvNnFe0w@mail.gmail.com' \
--to=gwern-v26zt+9v8bxeowh0uzbu5w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).