emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jack Kamm <jackkamm@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>, Jean Luc <jlr_0@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] ox-icalendar does not support custom export snippets (was: Turning all my "all day events" FREE in an ics export)
Date: Tue, 02 Jul 2024 15:53:29 -0700	[thread overview]
Message-ID: <871q4bo17a.fsf@gmail.com> (raw)
In-Reply-To: <87sewrj29n.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> CCing the maintainer.

Thanks Ihor. This issue dovetails nicely with the other recent iCalendar
issue [1] that I am still looking into (sorry for the tardiness)

> In theory, you should be able to do something like
>
> #+ICALENDAR_VCALENDAR: X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
> or an equivalent export snippet, but ox-icalendar does not support such
> thing. I believe that it should be considered a bug - we should provide
> some means to produce text to be exported verbatim from inside Org files.

Yes I agree we should support this functionality. I see two basic ways:
first, as you suggest

#+ICALENDAR_VEVENT: X-MICROSOFT-CDO-INTENDEDSTATUS:FREE

Or alternatively,

#+begin_export icalendar
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
#+end_export

We could follow the example of the latex exporter which supports both
usages.

However I am not sure we can simply export verbatim -- we may need to
add additional checks. In particular various Org properties or special
keywords may also be exported as iCal properties (e.g. SCHEDULED as
DTSTART, or TODO as STATUS:NEEDS-ACTION), and we may want to handle
duplicate behavior -- for example, by default TODO could be exported as
STATUS:NEEDS-ACTION unless explicitly overridden by #ICALENDAR_STATUS
(this is also related to the discussion in [1]).

We could possibly use icalendar.el to parse the icalendar export
blocks/keywords to check for duplicate properties. icalendar.el provides
many useful parsing functions, though some are private methods
(e.g. icalendar--get-event-property) and may need to be copied (or we
could consider asking emacs-devel to make those methods public).

[1] https://list.orgmode.org/87r0cmu7lc.fsf@localhost/T/#t


      reply	other threads:[~2024-07-02 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374731113.85480.1719912621305.ref@mail.yahoo.com>
2024-07-02  9:30 ` Turning all my "all day events" FREE in an ics export Jean Luc
2024-07-02 14:29   ` [BUG] ox-icalendar does not support custom export snippets (was: Turning all my "all day events" FREE in an ics export) Ihor Radchenko
2024-07-02 22:53     ` Jack Kamm [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=871q4bo17a.fsf@gmail.com \
    --to=jackkamm@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jlr_0@yahoo.com \
    --cc=yantar92@posteo.net \
    /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).