From: Ihor Radchenko <yantar92@posteo.net>
To: Psionic K <psionik@positron.solutions>
Cc: emacs-orgmode@gnu.org
Subject: [TASK] Re: Link translation & relative path export_file_name
Date: Sun, 05 Nov 2023 11:52:07 +0000 [thread overview]
Message-ID: <87jzqw5sew.fsf@localhost> (raw)
In-Reply-To: <CADQMGARMYNkwX23A2y4iDFvNOmcBhsbtYus5JckyCU_f8SiATw@mail.gmail.com>
Psionic K <psionik@positron.solutions> writes:
> When using an +#export_file_name directive, is it possible to have links
> translated to match the directory offset of the target?
> ...
> The links in the org document are correct. The links in the resulting
> markdown are not translated, and break.
You can use a custom filter.
Unfortunately, adding such filter universally is tricky - when
publishing, relative links to files are currently expected to remain
valid as the publishing also moves the referenced files to the publishing
directory. If we update the relative links according to the exported
file location, this behaviour will be broken.
I think that the right approach will be updating the file links during
ordinary export and then handling the updated links specially during
publishing. Patches welcome.
> The manual has a slightly different problem. I need to translate it as if
> it will be exported to the root directory even though it's always in the
> doc directory. The links don't seem useful, and turning them off may be
> more correct. I haven't gotten a lot of experience with drafting texinfo
> yet.
You may consider using ox-publish - it is designed with multiple files
being exported in mind and allows setting target directory where the
necessary files will be copied over.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-11-05 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 2:04 Link translation & relative path export_file_name Psionic K
2023-11-05 11:52 ` Ihor Radchenko [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
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=87jzqw5sew.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=psionik@positron.solutions \
/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).