From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: dates in heading break beamer export Date: Tue, 01 Oct 2013 18:01:51 +0200 Message-ID: <87txh156a8.fsf@gmail.com> References: <524801E3.7040709@toel.it> <87bo3bwug5.fsf@gmail.com> <20130929172751.4644b537@aga-netbook> <5249A0AB.7080408@toel.it> <20130930190538.5397f472@aga-netbook> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40140) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2OP-00026T-QR for emacs-orgmode@gnu.org; Tue, 01 Oct 2013 12:01:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR2OJ-0007D3-Go for emacs-orgmode@gnu.org; Tue, 01 Oct 2013 12:01:45 -0400 Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:40074) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2OJ-0007BG-4t for emacs-orgmode@gnu.org; Tue, 01 Oct 2013 12:01:39 -0400 Received: by mail-we0-f180.google.com with SMTP id u57so7620358wes.11 for ; Tue, 01 Oct 2013 09:01:37 -0700 (PDT) In-Reply-To: <20130930190538.5397f472@aga-netbook> (Marcin Borkowski's message of "Mon, 30 Sep 2013 19:05:38 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcin Borkowski Cc: emacs-orgmode@gnu.org Hello, Marcin Borkowski writes: > Daniele Pizzolli napisa=C5=82(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. >>=20 >> But org-mode allow this! >>=20 >> 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, --=20 Nicolas Goaziou