Hello,
On 05/25/2013 03:57 PM, Rasmus wrote:
> Alan Schmitt <alan.schm...@polytechnique.org> writes:
> 
>> Hello,
>>
>> Viktor Rosenfeld writes:
>>
>>> Hi Robert,
>>>
>>> Robert Klein wrote:
>>>
>>>> Hi,
>>>>
>>>> FWIW, from a users view it would be nice if:
>>>>
>>>> - Use Author/Email information from org file
>>>> - If not present use information from LCO file
>>>> - if neither org file nor LCO file has any information use
>>>>   user-full-name and user-email-address
>>>>
>>>> Could this be solved by having several e.g. `setkomavar{fromname}'
>>>> and so on in the tex file, so is created as follows:
> 
> I'd go with 'no'.  It's not aesthetically pleasing and I don't want my
> output to look like LyX.  When feasible we should go for beautiful
> output.  This isn't always the case at the moment, but still.
>  
>>>> if no #+AUTHOR in org-file and user-full-name is set:
>>>>     add user-full-name
>>>> if #+LCO(s) in org-file:
>>>>     add LCO file(s)
>>>> if #+AUTHOR in org-file:
>>>>     add \setkomavar{fromname}{#+AUTHOR}
>>>> ....  same for email
> 
> Currently the ordering is: #+AUTHOR > #+LCO and AUTHOR default to
> (user-full-name).

hmm, sorry, I did not express myself in a good way.

what I meant is, if #+AUTHOR defaults to (user-full-name), could the
\setkomavar commands be placed /before/ \LoadLetterOption in the TeX
file,  and after \LoadLetterOptions if #+AUTHOR is set in the .org file?

So you'd still get only one set of \setkomavar in the TeX file, but get
a (for me) more useful order of #+AUTHOR != (user-full-name) > #+LCO >
#+AUTHOR == (user-full-name)


Best regards
Robert


Reply via email to