From: Manfred Lotz <manfred.lotz@arcor.de>
To: Christian Moe <mail@christianmoe.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: export to odt
Date: Fri, 14 Jun 2013 09:57:37 +0200 [thread overview]
Message-ID: <20130614095737.275a8284@hogwart.bsdlocal.net> (raw)
In-Reply-To: <m238sl6uhd.fsf@christianmoe.com>
On Fri, 14 Jun 2013 09:07:26 +0200
Christian Moe <mail@christianmoe.com> wrote:
>
> Manfred Lotz writes:
>
> > On Thu, 13 Jun 2013 08:37:55 +0100
> > Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> >
> >> Manfred Lotz <manfred.lotz@arcor.de> writes:
> >>
> >> [...]
> >>
> >>
> >> > This is really weird or it is because just my knowledge about
> >> > Libreoffice is limited. At least, I'm happy to be able to use
> >> > LaTeX in most cases instead of an office product.
> >>
> >> I'm with you on this! I use LaTeX almost exclusively. Every now
> >> and again, unfortunately, I have to share an editable document
> >> with others and LibreOffice/MSWord is the only easy way. For
> >> simple dissemination, LaTeX -> PDF is better.
> >>
> >
> >
> > Yep, exactly. I'm grateful that the export to odt was implemented in
> > org-mode so that we have an option to give a finalized document
> > away if needed.
>
> Note, however, that what you've been discussing is a feature, not a
> requirement. LibreOffice allows you to put the title of the document
> in a field code that mirrors the document metadata; it doesn't force
> you to, and I imagine > 95% of users aren't even aware of the option.
>
> As I recall, this was a solution Jambunathan opted for at some late
> point in the development of the org-odt exporter. Before that, the
> exporter just wrote the title in as ordinary, editable text. I sort of
> preferred the old approach, but not enough to bother to ask to have it
> back.
>
Yes I'm aware that this is due to the way how org-mode export to odt is
coded.
> But if many users are baffled why they can't just edit a document
> title on the page itself after exporting to ODT -- and that seems
> likely -- maybe this feature is ripe for a change.
>
Hm, I do not have any requirements to later change title and author
in the odt document as I would change it in the org file directly. Thus
I don't care how the title and author is set in the odt document.
--
Manfred
next prev parent reply other threads:[~2013-06-14 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 14:19 export to odt Manfred Lotz
2013-06-07 20:35 ` Christian Moe
2013-06-10 15:42 ` Manfred Lotz
2013-06-11 10:33 ` Eric S Fraga
2013-06-11 19:52 ` Manfred Lotz
2013-06-12 7:33 ` Eric S Fraga
2013-06-12 17:39 ` Manfred Lotz
2013-06-13 7:37 ` Eric S Fraga
2013-06-13 10:34 ` Manfred Lotz
2013-06-14 7:07 ` Christian Moe
2013-06-14 7:57 ` Manfred Lotz [this message]
2013-06-14 14:51 ` Eric S Fraga
2013-06-12 2:58 ` Manfred Lotz
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 22:26 export to ODT Henri-Paul Indiogine
2011-07-06 22:47 ` Nick Dokos
2011-07-06 23:38 ` Henri-Paul Indiogine
2011-07-07 8:19 ` Jambunathan K
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=20130614095737.275a8284@hogwart.bsdlocal.net \
--to=manfred.lotz@arcor.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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).