From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] Fix ODT output for scheduled items.
Date: Sat, 28 Nov 2020 10:29:40 -0500 [thread overview]
Message-ID: <87360txzx7.fsf@pierrot.dokosmarshall.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
The ODT exporter uses the org-deadline-string for scheduled items. This
apparently predates the introduction of the "new" exporter in 2013 -
time flies...
It was reported on Emacs SE:
https://emacs.stackexchange.com/questions/61985/org-export-to-odt-incorrectly-use-deadline-for-scheduled
Patch attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Fix ODT output for scheduled items --]
[-- Type: text/x-patch, Size: 935 bytes --]
From 429d3eb816d0673326969f50b478f4d622147432 Mon Sep 17 00:00:00 2001
From: Nick Dokos <ndokos@gmail.com>
Date: Sat, 28 Nov 2020 10:01:02 -0500
Subject: [PATCH] org-odt-planning: Fix scheduled item output
* lis/ox-odt.el (org-odt-planning): Use org-scheduled-string, not
org-deadline-string, for scheduled items.
See <https://emacs.stackexchange.com/questions/61985/org-export-to-odt-incorrectly-use-deadline-for-scheduled> for an ECM.
---
lisp/ox-odt.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el
index 4619f9fcd..ef07acfed 100644
--- a/lisp/ox-odt.el
+++ b/lisp/ox-odt.el
@@ -2946,7 +2946,7 @@ channel."
(when scheduled
(concat
(format "<text:span text:style-name=\"%s\">%s</text:span>"
- "OrgScheduledKeyword" org-deadline-string)
+ "OrgScheduledKeyword" org-scheduled-string)
(org-odt-timestamp scheduled contents info)))))))
--
2.25.4
[-- Attachment #3: Type: text/plain, Size: 12 bytes --]
--
Nick
next reply other threads:[~2020-11-28 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 15:29 Nick Dokos [this message]
2020-11-28 15:38 ` [PATCH] Fix ODT output for scheduled items Nick Dokos
2020-11-28 15:59 ` Kyle Meyer
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=87360txzx7.fsf@pierrot.dokosmarshall.org \
--to=ndokos@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).