emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcel van der Boom <marcel@hsdev.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add author and title to exported PDF properties
Date: Wed, 14 May 2014 17:48:36 +0200	[thread overview]
Message-ID: <20140514174836.3825cfb2@hsdev.com> (raw)
In-Reply-To: <87y4y4le64.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]



On wo 14-mei-2014 14:48
Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> [...]
>> How do they differ from, say 'subject'?  
> 
> "subject", which refers to :description property, only contains a
> single string, no Org syntax. OTOH, TITLE and AUTHOR keywords have
> their contents parsed and, as such, can contain parsed objects. E.g.,
> 
>   | keyword     | value       | property value             |
>   |-------------+-------------+----------------------------|
>   | DESCRIPTION | some *text* | "some *text*"              |
>   | TITLE       | some *text* | ("some" (bold ... "text")) |
> 
> See also `org-element-document-properties'.
>

Thanks, this section made the click for me. 

I think I sort of assumed that 'LateX codes' in author and title were
just going to be dropped by the hyperref package itself to produce the
properties.

I'm not sure I can find the time to produce a better patch, this is
uncharted territory for me, so it will take some learning effort.

Thanks again,

marcel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-05-14 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 21:40 [PATCH] Add author and title to exported PDF properties Marcel van der Boom
2014-05-14  7:05 ` Nicolas Goaziou
2014-05-14 12:24   ` Marcel van der Boom
2014-05-14 12:48     ` Nicolas Goaziou
2014-05-14 15:48       ` Marcel van der Boom [this message]
2014-05-15 12:14         ` Sebastien Vauban

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=20140514174836.3825cfb2@hsdev.com \
    --to=marcel@hsdev.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).