From: Scot Becker <scot.becker@gmail.com>
To: David Bremner <bremner@unb.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: pretty export of tags
Date: Mon, 31 May 2010 17:28:56 +0100 [thread overview]
Message-ID: <AANLkTin6lQq0sRet51SsrF2VxzBB4Vk4FTNy16_LQQKZ@mail.gmail.com> (raw)
In-Reply-To: <87mxvgdsrp.fsf@convex-new.cs.unb.ca>
On Mon, May 31, 2010 at 3:56 PM, David Bremner <bremner@unb.ca> wrote:
>
> I would like some more control over how tags are exported to PDF. I
> tried both latex and docbook based methods, and as far as I can tell, in
> both cases the treatment is hard-coded (at least in the docbook case it
> does mark them as being different from the headline). Is there some
> existing trick I should know about? I'd like the tags e.g. right
> justified, or on the next line in a box. The HTML treatment is almost
> OK.
David,
I could have sworn I was looking at the relevant variable this
morning, but I can't find it. (I was looking at
org-export-latex-todo-keyword-markup, but that's of course for TODO
words). It looks to me like tag markup is hard-coded for LaTeX
export, as a simple substitution in the function
'org-export-latex-keywords-maybe.
I, too, would be glad to do some tricks on tags for LaTeX output.
Would it add to the complexity too much to expand the capabilities of
org-export-latex-classes, so that in the lines where you define the
header markup for each class, you can also define tag markup?
So in the following, %s is just the text of the header and %t is a
(comma-separated, for possible use as LaTeX arguements?) tag list:
'(("mynewclass"
"\\documentclass[11pt, a4paper]{article}"
("\\section{%s}\n\taglist{%t}" . "\\section*{%s}\n\taglist{%t}")
("\\subsection{%s}\n\taglist{%t}" . "\\subsection*{%s}\n\taglist{%t}")
... and so on.
The above example would produce LaTeX code like this:
\section{This is a Title Here}
\taglist{tag1,tag2,tag3}
Section text goes here.
I would then define \taglist{} in my header as a custom latex command
which does the formatting I want on the tags.
Presumably I could also add whatever formatting I want around %t ---at
least whatever formatting LaTeX supports. David, you might want to
assure yourself that LaTeX is capable of producing the results you
want. I'm weak on the specifics, but there is some trouble putting
certain kinds of commands in LaTeX header lines.
It may be that in time, org-export-generic will grow into a tool that
can be made to produce a decent LaTeX exporter, (and might now for
certain well-structured and not-too-demanding kinds of documents), but
I suspect that time quite yet.
I'd be glad to hear of any other solutions or hacks.
Scot
next prev parent reply other threads:[~2010-05-31 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 14:56 pretty export of tags David Bremner
2010-05-31 16:28 ` Scot Becker [this message]
2010-06-04 11:22 ` Carsten Dominik
2010-09-14 10:00 ` Scot Becker
2010-09-14 12:43 ` Carsten Dominik
2010-09-15 22:04 ` Scot Becker
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=AANLkTin6lQq0sRet51SsrF2VxzBB4Vk4FTNy16_LQQKZ@mail.gmail.com \
--to=scot.becker@gmail.com \
--cc=bremner@unb.ca \
--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).