Re: [Exporter] Why is :author a list in the communication channel?

[Thorsten Jolitz <tjolitz@gmail.com>]

Hello,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Aaron Ecay <aaronecay@gmail.com> writes:
>>
>> Hi Aaron,
>>
>>> I would have expected multiple author lines to have this effect, so that
>>> your desired list of two authors would be generated by:
>>> ,----
>>> | #+author: Thorsten Jolitz
>>> | #+author: Thomas Mueller
>>> `----
>>>
>>> But it seems that only the last #+author line is used; previous ones are
>>> discarded.  Maybe the :author plist entry should just be converted into
>>> a string.  But if it remains a list to somehow support multiply-authored
>>> documents, I think the most natural way to specify the entries is with
>>> multiple lines as above.
>>
>> I can confirm that behaviour ... I'm not sure if I really get the idea
>> of a 'typeless secondary' string as mentioned by Nicolas, but in daily
>> practice 
>>
>> ,-----------------------
>> | (plist-get info :author)
>> `-----------------------
>>
>> returns a list with one string in it for me ...
>
> Try
>
>   #+AUTHOR: This is *Me*!
>
> The point is that you can have Org objects within AUTHOR (or TITLE, or
> DATE). See "secondary string" definition in org-element.el header.
>
> This is orthogonal to the fact that multiple lines are not allowed. For
> that, see BEHAVIOUR item in `org-export-options-alist'. In particular,
> you can compare "TITLE" and "AUTHOR" entries.

Ok, I understand, so this is all working fine just as intended. For
multiple authors one could use a workaround/convention like 

 ,------------------------------------------
 | #+author: Thorsten_Jolitz Thomas_Mueller
 `------------------------------------------

and then split the string two times (first blanks, then underscores). 

-- 
cheers,
Thorsten