From: Rasmus <rasmus@gmx.us>
To: mel@mbacou.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Add #+SUBTITLE
Date: Thu, 26 Mar 2015 11:10:11 +0100 [thread overview]
Message-ID: <87oang9iik.fsf@gmx.us> (raw)
In-Reply-To: <551370B3.1000709@mbacou.com> (Melanie Bacou's message of "Wed, 25 Mar 2015 22:36:35 -0400")
Hi,
Melanie Bacou <mel@mbacou.com> writes:
> I would indeed go further and suggest adding the following once and
> for all as common ox features:
I don't think so. Consider the ultra important ox-ical (it's important
'cause it keep my calendar in sync via org-caldav). How should it handle
these fields? I think markdown also ignores them. I think it's better to
identify a subset of "text exporters" (ox-ascii, ox-html, ox-latex,
ox-odt) that support a larger set of keywords, but not through ox.el.
(Though having it in ox makes the backend code slightly cleaner).
> #+AUTHORS (support multiple)
This one is tough. Recently I had to write a LaTeX title for two authors,
one institutions like
Author 1 Author 2
Institution
AFAIK, the \and does not work for this in LaTeX. It's just very hard to
find a general solution. How would you even write this? How do I
associate authors and institution? Previously we talked about supporting
footnotes in TITLE and AUTHOR which could maybe solve the email issue.
> #+EMAILS (1 per author)
> #+AFFILIATIONS (1 per author)
AFAIK this is supported in beamer, so we could add it there. It's also in
KOMA-Script I believe.
> #+CLASSIFICATION (e.g. "ACM", "JEL", "Dublin Core", "your corporate
> classification", etc.)
I have no clue what this means.
> #+KEYWORDS
> #+DESCRIPTION
> #+REVISION
> #+COPYRIGHT
Are these fields standard? In hyperref these are supported out of the
box:
pdftitle pdfauthor pdfsubject pdfcreator pdfproducer pdfkeywords
pdftrapped
New ones can be added via pdfinfo, though.
You have not specified any details about what is printed. I guess
something like revision is like a subtitle, i.e. you'd want it printed?
> This is not so much about what back-ends currently support (that's
> irrelevant in my view), it's about what minimum meta information is
> needed to publish and maintain meaningful documents.
It also about having good support for our main backends. E.g. we try to
support math equally well in latex and other backends.
> The use of these meta fields encourage good publishing practices, and
> all back-ends should eventually support all or a subset of these. Most
> LaTeX journal classes do.
^^^^^^^
But ox-latex assumes the default doc. classes.
> HTML would support these at least as <meta content=""> tags.
It would be great if you would concretely share examples with us, that
uses all of this stuff in a concrete manner. At the very least more
details is needed. You will also have to confirm whether you truly think
this is an ox.el issue in the light of my comments above (what is
COPYRIGHT to ical?).
> ODT and DOCX can support all using templates.
Org does not export to docx.
—Rasmus
--
. . . The proofs are technical in nature and provides no real understanding
next prev parent reply other threads:[~2015-03-26 10:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 23:23 [ox, patch] Add #+SUBTITLE Rasmus
2015-03-21 2:26 ` Marcin Borkowski
2015-03-21 2:32 ` Melanie Bacou
2015-03-22 14:02 ` Nicolas Goaziou
2015-03-22 15:29 ` Rasmus
2015-03-22 20:47 ` Marcin Borkowski
2015-03-22 21:21 ` Thomas S. Dye
2015-03-22 21:23 ` John Williams
2015-03-22 22:43 ` Rasmus
2015-03-22 23:19 ` Marcin Borkowski
2015-03-23 0:05 ` Rasmus
2015-03-23 8:32 ` Marcin Borkowski
2015-03-23 9:00 ` Sebastien Vauban
2015-03-24 9:05 ` Nicolas Goaziou
2015-03-24 9:37 ` Rasmus
2015-03-28 15:17 ` Nicolas Goaziou
2015-03-26 2:36 ` Melanie Bacou
2015-03-26 2:38 ` Melanie Bacou
2015-03-26 10:10 ` Rasmus [this message]
2015-03-22 14:34 ` Eric Abrahamsen
2015-03-22 15:32 ` Rasmus
2015-03-23 1:17 ` Eric Abrahamsen
2015-03-26 2:47 ` Melanie Bacou
2015-03-26 9:52 ` Rasmus
2015-03-26 10:42 ` Rasmus
2015-03-28 8:26 ` Melanie Bacou
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=87oang9iik.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=mel@mbacou.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).