From: Myles English <mylesenglish@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: ox-koma-letter.el: subtree vs buffer, precedence of properties, superscript transcoding
Date: Mon, 22 Jun 2015 22:57:05 +0100 [thread overview]
Message-ID: <87ioafv2ar.fsf@gmail.com> (raw)
Hello,
I have noticed some strange things about koma letter exports (current
git master 329683).
1) subtree scope export results differently than buffer scope export
2) a signature specified in the subtree property does not take
precedence in subtree export
3) superscripts on the dates behave differently in the subject and
date properties, i.e. 20\textsuperscript{th} & 20^{th}
The files included below constitute a Fairly Small Working Example (a
FSWE) that illustrate those things. Using those files, I start emacs
like this:
emacs -Q -l config.el a.org # or b.org
Thanks,
Myles
The Files
---------
1) a.org Export like this: C-c C-e C-s k o ________________________
* Letter
:PROPERTIES:
:EXPORT_LaTeX_CLASS: my-min-letter
:EXPORT_LCO: mylco
:EXPORT_TITLE:
:EXPORT_PLACE: Here
:EXPORT_SUBJECT: The thing that happened on 20\textsuperscript{th} June 2015
:EXPORT_DATE: June 20^{th} 2015
:EXPORT_TO_ADDRESS: Orgsters\\Internet
:EXPORT_OPENING: Dear Mr X,
:EXPORT_AUTHOR: Ronald Reagan
:EXPORT_CLOSING: Yours sincerely,
:EXPORT_SIGNATURE: This is the sig I want
:END:
The thing that happened was completely unacceptable.
SUBTREE EXPORT
2) b.org Export like this: C-c C-e k o ________________________
#+LaTeX_CLASS: my-min-letter
#+LCO: mylco
#+TITLE:
#+PLACE: Here
#+SUBJECT: The thing that happened on 20\textsuperscript{th} June 2015
#+DATE: June 20^{th} 2015
#+TO_ADDRESS: Orgsters\\Internet
#+OPENING: Dear Mr X,
#+AUTHOR: Ronald Reagan
#+CLOSING: Yours sincerely,
#+SIGNATURE: This is the sig I want
* Letter
The thing that happened was completely unacceptable.
WHOLE BUFFER EXPORT
3) config.el ________________________
(add-to-list 'load-path
"~/.emacs.d/plugins/org-mode/lisp")
(add-to-list 'load-path
"~/.emacs.d/plugins/org-mode/contrib/lisp" t)
(require 'ox-latex)
(global-set-key (kbd "C-c C-e") 'org-export-dispatch)
(eval-after-load 'ox '(require 'ox-koma-letter))
(eval-after-load 'ox-koma-letter
'(progn
(add-to-list 'org-latex-classes
'("my-min-letter"
"\\documentclass[foldmarks=false]\{scrlttr2\}
\\usepackage[UKenglish]{babel}
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]"))
(setq org-koma-letter-default-class "my-min-letter")
))
4) mylco.lco ________________________
\setkomavar{fromname}{Name in LCO file}
\setkomavar{fromaddress}{My house\\My street}
\setkomavar{signature}{\usekomavar{fromname}}
next reply other threads:[~2015-06-22 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 21:57 Myles English [this message]
2015-06-23 2:56 ` ox-koma-letter.el: subtree vs buffer, precedence of properties, superscript transcoding Rasmus
2015-06-23 20:13 ` Nicolas Goaziou
2015-06-23 21:24 ` Rasmus
2015-06-23 22:08 ` Myles English
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=87ioafv2ar.fsf@gmail.com \
--to=mylesenglish@gmail.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).