From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniele Pizzolli Subject: Re: Bug: dates in heading break beamer export Date: Wed, 02 Oct 2013 18:10:57 +0200 Message-ID: <524C4591.9020804@toel.it> References: <524801E3.7040709@toel.it> <87bo3bwug5.fsf@gmail.com> <20130929172751.4644b537@aga-netbook> <5249A0AB.7080408@toel.it> <524BC196.8000700@toel.it> <87d2nnu6pp.fsf@gmail.com> <524C3D97.60705@toel.it> <8761tfu0ov.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRP19-0000zb-73 for emacs-orgmode@gnu.org; Wed, 02 Oct 2013 12:11:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRP0z-0000SU-1d for emacs-orgmode@gnu.org; Wed, 02 Oct 2013 12:11:15 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:50206) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRP0y-0000SJ-Rv for emacs-orgmode@gnu.org; Wed, 02 Oct 2013 12:11:04 -0400 In-Reply-To: <8761tfu0ov.fsf@gmail.com> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org On 10/02/2013 05:55 PM, Nicolas Goaziou wrote: > Daniele Pizzolli writes: > >> Yes, I think is fair to drop the markup. > > OK. > >> I would also think that this is safe default when nested markup is >> bad. > > Do you have an exhaustive list of such cases? No, not really but I try to report them as soon I found them. I do want to replace latex entirely with org, so I will use it extensively in the near future. >> Maybe the exporter can emit a notice/warning. > > That it dropped the markup? Yes, I do not know if there is already a standard in reporting back but I would go for something like "Latex-exporter: Warning: dropped code markup at line XX of originalorgfile.org because it is not supported by this exporter. More info at ..." or even a shorter one can be fine to me. >> Yes, sorry, I mixed two not-so-related problem. The beamer exporter do >> not work with this code: >> >> #+OPTIONS: H:3 >> * title test[fn:1] >> ** section >> *** subsection >> >> [fn:1] text > > Of course, that's a similar problem: footnotes are not allowed in > headlines. Though, in this case, it isn't possible to drop the markup. > What LaTeX code do you suggest? Mmm, I think you are asking to the wrong person. I do not know enough about latex and its error reporting capabilities... I would appreciate if the exporter does not break and/or a notification to the user of the problem in and understandable language, even for newcomers. I know when latex do not know how to resolve some references put some question marks... but I do not really know if this is the case to follow this convention. Regards, Daniele