emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Brett Viren <bv@bnl.gov>, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Carsten Dominik <dominik@uva.nl>,
	Tim Cross <theophilusx@gmail.com>,
	Org Mode <emacs-orgmode@gnu.org>
Subject: Re: why prepend "file://" to abs paths in html output?
Date: Mon, 10 Jul 2017 19:54:58 +0000	[thread overview]
Message-ID: <CAFyQvY2cUdo23YZKZdb=Am+fJCudjq5VziRSTVCM_ohf9hEVNQ@mail.gmail.com> (raw)
In-Reply-To: <86y3rw2y1y.fsf@hierocles.phy.bnl.gov>

[-- Attachment #1: Type: text/plain, Size: 2944 bytes --]

Hi Nicolas,

I tried out the patch, and my comments are in the MWE below.

On Mon, Jul 10, 2017 at 9:59 AM Brett Viren <bv@bnl.gov> wrote:

> Is this saying "subtract the value of 'html_link_root' from the Org link
> to make its URL"?
>
> If so, I think this would not be general enough to help some cases.  For
> example, with Nikola+orgmode and with Nikola's "pretty URLs" option the
> relative location between either the Org source or its generated HTML
> and an image that they both link will differ.
>

Good point. I overlooked that.

I have this MWE that explains the "would like to have" vs "what this patch
gives us":

=====
#+TITLE: ox-html root dir
#+OPTIONS: toc:nil
#+STARTUP: inlineimages
#+HTML_LINK_ROOT: /tmp/site/static/

An =image.png= exists as =/tmp/site/static/images/image.png=.

* This is how the image links should have worked with the link root already
specified
[[/images/image.png]]
- The =HTML_LINK_ROOT= should to appended to the front of the above link if
that
  concatenated path is a valid one.
- Would also like =C-x C-o=, inline image display, etc. to work.
- So a thought.. should the link root specification be made exporter
agnostic?
* This works after adding support for =HTML_LINK_ROOT= ..
.. but
- The link path becomes too long.
- Need to hard-code the full path to the site/blog root directory before
each of
  such links.
[[file:/tmp/site/static/images/image.png]]
=====



> Some details:
>
> Nikola source wants this layout:
>
>   /path/to/my/nikola/posts/my-blog-post.org
>   /path/to/my/nikola/images/unicorn.jpg
>
> The Org source generates to HTML which will be found at this URL path:
>
>   /mysiteroot/posts/my-blog-post/index.html
>

The organization for Hugo posts is something similar. So hopefully we can
have a solution that works for such blogging platforms in general.

In comparsion, the hugo paths would be:

  /path/to/my/hugo/content/posts/my-blog-post.org
  /path/to/my/hugo/static/images/unicorn.jpg

So, right now, either the Org link to the image must be written to be
> invalid (for Org):
>
>   [[../../images/unicorn.jpg]]
>

 Yeah, this is a problem and can probably be fixed if a support for
something like "#+LINK_ROOT" can be made in Org and not specific to an
exporter backend.

Or, some mechanism needs to turn the valid Org link:
>
>   [[../images/unicorn.jpg]]
>
> into either:
>
>   <img src="/mysiteroot/images/unicorn.jpg" ...>
>
> or:
>
>   <img src="../../images/unicorn.jpg" ...>
>
> I guess I could use html_link_root set to "/path/to/my/nikola" but then
> my Org source loses portability.
>
> I think better would be able to explicitly state the desired URL path
> for the HTML <img> like:
>
>   #+html_url_path: /mysiteroot/images/unicorn.jpg
>   [[../images/unicorn.jpg]]
>

As I mention in my MWE, I am actually looking for a solution so that we do
not need to specify the "mysiteroot" for each link.. may be just one as a
"#+LINK_ROOT".
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 4558 bytes --]

  reply	other threads:[~2017-07-10 19:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08  0:38 why prepend "file://" to abs paths in html output? Matt Price
2017-07-08 10:33 ` Nicolas Goaziou
2017-07-08 12:37   ` Kaushal Modi
2017-07-08 14:08     ` Nicolas Goaziou
2017-07-08 14:19       ` Carsten Dominik
2017-07-08 19:13         ` Nicolas Goaziou
2017-07-08 23:37           ` Tim Cross
2017-07-09 10:45             ` Nicolas Goaziou
2017-07-10 12:53               ` Kaushal Modi
2017-07-10 13:31                 ` Nicolas Goaziou
2017-07-10 13:58               ` Brett Viren
2017-07-10 19:54                 ` Kaushal Modi [this message]
2017-07-10 21:44                   ` Kaushal Modi
2017-07-13 12:39                   ` Nicolas Goaziou
2017-07-13 12:50                     ` Kaushal Modi
2017-07-13 12:55                       ` Nicolas Goaziou
2017-07-13 13:01                         ` Kaushal Modi
2017-07-13 13:14                           ` Nicolas Goaziou
2017-07-13 12:46                 ` Nicolas Goaziou
2017-07-10 22:12               ` Tim Cross

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFyQvY2cUdo23YZKZdb=Am+fJCudjq5VziRSTVCM_ohf9hEVNQ@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=bv@bnl.gov \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=theophilusx@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).