From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: dates in heading break beamer export
Date: Tue, 01 Oct 2013 18:01:51 +0200 [thread overview]
Message-ID: <87txh156a8.fsf@gmail.com> (raw)
In-Reply-To: <20130930190538.5397f472@aga-netbook> (Marcin Borkowski's message of "Mon, 30 Sep 2013 19:05:38 +0200")
Hello,
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Daniele Pizzolli <dan@toel.it> napisał(a):
>> Or why not drop \textit?
>
> Sounds good for me. (NB: there's a similar problems with tags, AFAIR.
> And (AFAIR!) it's even worse, since the exporter uses a low-level TeX
> command \hfill.)
Well, there is `org-latex-active-timestamp-format',
`org-latex-inactive-timestamp-format' and even filters can do it.
It is also technically possible to write in ox-latex a section-local
specific export back-end that would translate differently some objects
in a \section{...} command. But that would make the export a bit more
unpredictable.
Of course, in a few cases, `latex' back-end does its best to circumvent
possible problems (i.e. nested footnotes), but this is nowhere near
a general rule. It's usually a lot of work for a tiny corner case.
>> > In general, putting formatting commands in \section title etc.,
>> > even if not erroneous, is considered a bad practice.
>>
>> But org-mode allow this!
>>
>> I think that if something is allowed in org-mode syntax but not by the
>> underlining tools used for export, the exporter should take care to
>> find a suitable workaround.
>
> Definitely agreed. The point is, what is a "suitable workaround"?
I disagree. This is just unrealistic. There are many packages involving
many quirks. We cannot afford to provide a workaround to all (or even
most) of them, assuming one exists.
Also, the OP is making a false assumption. The underlining tool allows
\texit in the section \command, i.e., you can type it in a "tex" file.
You will get a compilation error, exactly as if you do the same mistake
in Org. Why Org should be smarter in this case?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-10-01 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 10:33 Bug: dates in heading break beamer export Daniele Pizzolli
2013-09-29 14:53 ` Nicolas Goaziou
2013-09-29 15:27 ` Marcin Borkowski
2013-09-30 16:02 ` Daniele Pizzolli
2013-09-30 17:05 ` Marcin Borkowski
2013-10-01 16:01 ` Nicolas Goaziou [this message]
2013-10-01 16:33 ` Marcin Borkowski
2013-10-02 6:50 ` Bug: code and footnotes (was Bug: dates in heading break beamer export) Daniele Pizzolli
2013-10-01 8:09 ` Bug: dates in heading break beamer export Eric S Fraga
2013-10-02 6:47 ` Daniele Pizzolli
2013-10-02 13:45 ` Nicolas Goaziou
2013-10-02 15:36 ` Daniele Pizzolli
2013-10-02 15:55 ` Nicolas Goaziou
2013-10-02 16:10 ` Daniele Pizzolli
2013-10-02 20:47 ` Marcin Borkowski
2013-10-03 13:30 ` Nicolas Goaziou
2013-10-03 15:59 ` Daniele Pizzolli
2013-10-04 19:17 ` Nicolas Goaziou
2013-10-02 22:12 ` Suvayu Ali
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=87txh156a8.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).