From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: tip for paths that work locally and served?
Date: Tue, 1 Jun 2021 11:08:18 -0400 [thread overview]
Message-ID: <70fc8d18-e32d-1468-c860-3ec9005f4a00@reagle.org> (raw)
My webhost was just down for a bit and it broke even local access -- which is what I use 90% of the time -- because I use pandoc's `-c` argument to pass an absolute URL, yielding the following in my HTML.
` <link rel="stylesheet" href="https://reagle.org/joseph/2003/papers.css" />`
This has nagged at me for decades and I saw something about the "rebase_relative_paths
" in the latest pandoc release and thought to investigate. After reading it a few times, I get that's not what I was looking for -- though I can see where it will be useful. And I appreciate this isn't really pandoc's concern.
Nonetheless, I thought to ask, does anyone have a technique for generating HTML with references that work locally *and* when served?
If tilda/`~` was interpreted in both contexts, then I might be able to achieve this as long as my local and webhost file structures were the same, but absent some fancy rewrites in .htaccess, I don't think I can...
next reply other threads:[~2021-06-01 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:08 Joseph Reagle [this message]
[not found] ` <70fc8d18-e32d-1468-c860-3ec9005f4a00-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-01 21:42 ` Joseph Reagle
[not found] ` <f35add93-e541-094c-6c13-feaa5410115e-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-02 11:08 ` BPJ
[not found] ` <CADAJKhAg8V4_++1oeJvja=RQgZfbk3nOX--vwKxRbw0+emYctw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-02 13:45 ` Joseph Reagle
2021-06-02 16:44 ` John MacFarlane
[not found] ` <m2r1hkusgl.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-06-02 18:20 ` Joseph Reagle
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=70fc8d18-e32d-1468-c860-3ec9005f4a00@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).