From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [DISCUSSION] Default description for relative file links in odt export (was: [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]))
Date: Thu, 03 Nov 2022 06:25:36 +0000 [thread overview]
Message-ID: <8735b08sgv.fsf@localhost> (raw)
In-Reply-To: <tju2ve$1650$1@ciao.gmane.io>
In ODT, the ./ is _inside_ the odt archive and the current
directory is "../". Then, the default description for file links is
"../file", which is somewhat confusing.
Should we change it and tweak the default description of relative file
links in odt? This will only matter during odt export of relative file
links without description.
Max Nikulin <manikulin@gmail.com> writes:
>> I also noticed this, but I feel that it is reasonable. In odt,
>> "file-b.org" implies a resource inside the odt archive. "../file-b.org"
>> will highlight that it is an external file.
>>
>> I'd prefer to leave the "../file" description for now and only do
>> something when/if we hear from the ox-odt users.
--------
> On 02/11/2022 12:04, Ihor Radchenko wrote:
>> See the attached new version of the patch.
>
> The patch looks reasonable. I have not tried it in action though.
Applied onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=210630e546bbd746a98ac252316763371b3ccaf1
Regardless of the default description issue, we want this fix.
--
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>
next prev parent reply other threads:[~2022-11-03 6:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 18:39 [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)] Moritz Schäfer
2022-10-18 7:47 ` Ihor Radchenko
2022-10-19 8:00 ` Moritz Schäfer
2022-10-19 10:36 ` Ihor Radchenko
2022-10-20 10:09 ` Max Nikulin
2022-10-21 3:16 ` Ihor Radchenko
2022-10-21 14:46 ` Max Nikulin
2022-10-22 5:03 ` [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]) Ihor Radchenko
2022-10-22 8:04 ` Max Nikulin
2022-10-23 4:29 ` Ihor Radchenko
2022-10-24 11:40 ` Max Nikulin
2022-10-25 10:20 ` Max Nikulin
2022-10-31 6:13 ` Ihor Radchenko
2022-10-31 14:37 ` Max Nikulin
2022-11-01 5:40 ` Ihor Radchenko
2022-11-01 15:04 ` Max Nikulin
2022-11-02 5:04 ` Ihor Radchenko
2022-11-02 15:39 ` Max Nikulin
2022-11-03 6:25 ` Ihor Radchenko [this message]
2022-11-01 5:47 ` org-export: How to handle links to the exported file? (was: [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)])) Ihor Radchenko
2022-11-01 15:18 ` org-export: How to handle links to the exported file? Max Nikulin
2022-11-01 5:48 ` [BUG] ox-odt file: links are not pointing to the real files (was: [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)]) Ihor Radchenko
2022-11-01 15:28 ` export and cross links between files Max Nikulin
2022-11-02 6:38 ` [DISCUSSION] Unified handling of links between Org files on export (was: export and cross links between files) Ihor Radchenko
2022-10-21 12:02 ` [BUG] ox-odt fails for org-id links (e.g., from org-roam v2) [9.5.2 (9.5.2-gfbff08 @ /home/moritz/.emacs.d/elpa/27.2/develop/org-9.5.2/)] Ihor Radchenko
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=8735b08sgv.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).