emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: How about Org Mode invalid link handling strategy for exporting?
Date: Wed, 02 Jan 2019 08:12:29 +0800	[thread overview]
Message-ID: <87ftubdij6.fsf@gmail.com> (raw)

When I use package "ox-epub" to export current Org buffer to EPUB file,
it is based on "ox-html", I got some issues. One issue is about the
external file resource link which can't add into EPUB, or internal link
but invalid (I use narrow to subtree to debug Org buffer when using
ox-epub, so some internal links to other headlines will be invalid).

I hope Org Mode can enhance this invalid link handling strategy to not
interrupt user exporting process. Just display warning to user. Or add
an option to controlled by user?

Because I'm exporting a big Clojure language reference to EPUB, so
really hard to handling those invalid links.

About the handling strategy, I have some ideas:

- raise warning about invalid links no matter internal links or external
  links.

- don't interrupt process when meet invalid links.

- keep link description part as link part. Replace the original link
  part with an empty link.

Do you any ideas?

--
[ stardiviner ]
       I try to make every word tell the meaning what I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

             reply	other threads:[~2019-01-02  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02  0:12 stardiviner [this message]
2019-01-02 14:16 ` How about Org Mode invalid link handling strategy for exporting? Nicolas Goaziou
2019-01-02 14:34 ` John Kitchin
2019-01-03 12:22   ` [SOLVED] " stardiviner

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=87ftubdij6.fsf@gmail.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.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.
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).