From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [patch] ox-koma-letter
Date: Tue, 26 Feb 2013 22:14:28 +0100 [thread overview]
Message-ID: <87mwuqg4ln.fsf@pank.iue.private> (raw)
In-Reply-To: <20130226123819.GQ24632@strey.biz> (Michael Strey's message of "Tue, 26 Feb 2013 13:38:19 +0100")
>> I have been working on extending the KOMA letter support in Org. The
>> backend is still rough and I would like to more stuff such as
>> designing firstfood and firsthead with org elements (e.g. I use a
>> tabularx for my firstfood with varioues stuff).
>>
>> I have changed the following objects:
> [...]
>> 3. Added from-bank, invoice and other keywords like that. Still
>> many to go, but some of them would probably need some thought.
>> For instance firstfoot should work differently depending on
>> whether it is given a NAMEd table or a string. Any though?
> [...]
>
> IMO your approach goes into a questionable direction here. Following it
> we will end up defining the complete letterhead and letter layout by
> setting org-mode variables. Wouldn't it be better to use Markus Kohm's
> concept of letter class options to set all the static stuff?
Potentially. What do you mean by "letter class options"? Are you
referring to customized LCO files or do you refer to e.g. customized
org-latex-classes?
One reason for adopting such variables might be that it would, in a
very long run, allow for export into other formats that scrlttr2.
Even when using a dedicated LCO files and or org-latex-classes it
might be appropriate to overwrite variables.
In any case I don't have a strong opinion on this issue and your
approach also makes sense.
>> 2. Added AFTER_CLOSING and AFTER_LETTER keywords for arbitrary code
>> after \closing{.} and \end{letter}, respectively.
>> [...]
>> b. Would it be better to have a dedicated, say, PS and ENCL rather
>> than the generic AFTER_CLOSING?
> I would opt for dedicated variables.
Fine by be.. At the very least these should come in the order that
they are specified in the document, I guess. E.g. I should be able to
place ENCL before PS in the output, if I so desire.
For arbitrary code I find AFTER_CLOSING and AFTER_LETTER nice.
E.g. for pdfpages inclusions.
--
May contains speling mistake
next prev parent reply other threads:[~2013-02-26 21:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:25 [patch] ox-koma-letter Rasmus
2013-02-26 9:50 ` Bastien
2013-02-26 11:53 ` Rasmus
2013-02-26 12:38 ` Michael Strey
2013-02-26 21:14 ` Rasmus [this message]
2013-02-27 10:51 ` Michael Strey
2013-02-27 12:13 ` Rasmus
2013-02-27 13:41 ` Sebastien Vauban
2013-02-27 16:48 ` Rasmus
2013-02-28 15:19 ` Michael Strey
2013-03-02 17:53 ` Rasmus
2013-03-01 13:17 ` Alan Schmitt
2013-03-02 10:26 ` Bastien
2013-03-02 15:50 ` Alan Schmitt
2013-03-02 18:12 ` Bastien
2013-03-02 17:54 ` Rasmus
2013-03-02 17:57 ` Rasmus
2013-03-02 19:21 ` Alan Schmitt
2013-03-02 21:58 ` Rasmus
2013-03-03 16:00 ` Alan Schmitt
2013-03-03 17:25 ` Nicolas Goaziou
2013-03-04 7:19 ` Alan Schmitt
2013-03-04 8:33 ` Nicolas Goaziou
2013-03-04 8:56 ` Alan Schmitt
2013-03-04 10:38 ` Rasmus
2013-03-04 20:38 ` Nicolas Goaziou
2013-03-05 9:08 ` Alan Schmitt
2013-03-05 9:52 ` Nicolas Goaziou
2013-03-05 10:51 ` Michael Strey
2013-03-05 12:23 ` Rasmus
2013-03-05 13:09 ` Michael Strey
2013-03-06 9:03 ` Alan Schmitt
2013-03-06 9:09 ` Nicolas Goaziou
2013-03-04 10:46 ` Michael Strey
2013-03-04 13:48 ` Alan Schmitt
2013-03-04 21:20 ` Rasmus
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=87mwuqg4ln.fsf@pank.iue.private \
--to=rasmus@gmx.us \
--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).