emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Differences in headline exports [was: Umlauts in LaTeX export]
Date: Wed, 03 Nov 2010 21:19:24 -0700	[thread overview]
Message-ID: <87d3qlbu0j.fsf_-_@berkeley.edu> (raw)
In-Reply-To: 21363.1288842714@gamaville.dokosmarshall.org

Nick Dokos <nicholas.dokos@hp.com> writes:

> Nevertheless that does not absolve org from dealing with \" properly. In
> fact, it deals with it correctly in a heading but not in the text:
>
> * G\"odel
>
> G\"odel
>
> gives:
>
> ...
> \section{G\"odel}
> \label{sec-1}
>
>
> G\''odel
>
>
> However, surrounding the o with braces breaks things in both places.
>
> I think part of the problem is that headings and text go through
> different processing: e.g. text goes through org-export-latex-content,
> whereas headings don't. So fixing a problem like this in one place is
> not enough.

I was recently crawling through the LaTeX export code, because I was
getting different results for how a heading was exported depending on
whether it was simply a section title or whether it was the title for
the whole document. (See: [1]) It was quite a chore for me to understand
the different code paths that a headline can go through.

I still don't fully understand why things are this way; shouldn't all
text that's exported to LaTeX be processed in the same way, regardless
of where it appears (with the exception, of course, of text between
delimiters that mark it as literal LaTeX input)?

I sent a patch [2] that basically dealt with my problem by sending
headlines that become document titles down the same code path that
headlines and content are sent through (namely,
org-export-preprocess-string), but I haven't received any response.  Is
that because there's some important reason to treat these contexts
differently?  Am I missing something?

Best,
Richard

[1] http://article.gmane.org/gmane.emacs.orgmode/32281/
[2] http://article.gmane.org/gmane.emacs.orgmode/32540/

  reply	other threads:[~2010-11-04  4:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 15:50 Umlauts in LaTeX export Richard Lawrence
2010-11-03 16:56 ` Sunny Srivastava
2010-11-03 17:35 ` Stefan Vollmar
2010-11-03 17:51   ` Jean-Marie Gaillourdet
2010-11-03 18:45     ` Stefan Vollmar
2010-11-03 20:08     ` Eric S Fraga
2010-11-03 20:15       ` Stefan Vollmar
2010-11-04  3:14         ` Richard Lawrence
2010-11-04  7:10           ` Stefan Vollmar
2010-11-04  3:51     ` Nick Dokos
2010-11-04  4:19       ` Richard Lawrence [this message]
2010-11-04 11:16       ` Eric S Fraga
2010-11-04 12:01         ` Nick Dokos
2010-11-05  5:15     ` german-postfix and speedkeys (was: Umlauts in LaTeX export) Memnon Anon
2010-11-05 11:10       ` german-postfix and speedkeys Jean-Marie Gaillourdet
2010-11-07 12:00         ` Memnon Anon
2010-11-03 17:54   ` Umlauts in LaTeX export Magnus Henoch

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=87d3qlbu0j.fsf_-_@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --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).