emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: CM <mail@christianmoe.com>
To: Steinar Bang <sb@dod.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: odt export of subtree: set/suppress the date in the export
Date: Sun, 09 Nov 2014 08:28:29 +0100	[thread overview]
Message-ID: <m2wq747s0z.fsf@christianmoe.com> (raw)
In-Reply-To: <upzcoash3d1g.fsf@dod.no>


I cannot reproduce either problem, though I seem to remember some
difficulty with changing date fields in the past. What Org version are
you using?

You can turn the use of date fields in LibreOffice on or off with
org-odt-use-date-fields. With date fields set to t:

- Setting :EXPORT_DATE: in the subtree and exporting the subtree results
  in an ODT export with that date in the header, not today's date.

- Inspecting the date field shows that the date is "fixed". (In
  LibreOffice, right-click the date and select "Fields" from the popup
  menu.)

- Indeed, the date remains unchanged when I do "Update all" or export
  to PDF from LibreOffice does indeed keep the same date.

Yours,
Christian

Steinar Bang writes:

>>>>>> Christian Moe <mail@christianmoe.com>:
>
>> Does setting the subtree's :EXPORT_DATE: property to the date of the
>> meeting do what you're looking for?
>
> Nope.  Still outputs the date of the export.
>
> And since writing the posting I've discovered another annoying property
> of the date: it will switch to the current date at any time of saving of
> the odt document (eg. when doing a "Save as PDF").
>
> So I think what I want is to zap that date stamp alltogether, to save me
> from having to delete it in the odt file before creating a PDF from it.

next prev parent reply	other threads:[~2014-11-09  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 20:35 odt export of subtree: set/suppress the date in the export Steinar Bang
2014-11-03 21:26 ` Christian Moe
2014-11-08 15:52   ` Steinar Bang
2014-11-09  7:28     ` CM [this message]
2014-11-09 19:04       ` Steinar Bang

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=m2wq747s0z.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sb@dod.no \
    /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

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).