From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: New exporter, beamer confusion Date: Wed, 06 Feb 2013 20:57:09 +0100 Message-ID: <87ehgtmd0q.fsf@gmail.com> References: <20130204063905.GA23614@kuru.dyndns-at-home.com> <87wqun5037.fsf@gmail.com> <6207.1360048864@alphaville> <87fw1ashw5.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3B7Z-0006Py-3D for emacs-orgmode@gnu.org; Wed, 06 Feb 2013 14:57:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3B7X-0004Fb-PN for emacs-orgmode@gnu.org; Wed, 06 Feb 2013 14:57:29 -0500 Received: from mail-wg0-f52.google.com ([74.125.82.52]:34159) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3B7X-0004FF-K2 for emacs-orgmode@gnu.org; Wed, 06 Feb 2013 14:57:27 -0500 Received: by mail-wg0-f52.google.com with SMTP id 12so1400198wgh.19 for ; Wed, 06 Feb 2013 11:57:26 -0800 (PST) In-Reply-To: (James Harkins's message of "Wed, 6 Feb 2013 10:12:05 +0800") 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: jamshark70@dewdrop-world.net Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org James Harkins writes: > Btw, *who* preferred \alert? (Orwell, Politics and the English Language: > "Never use the passive [voice] where you can use the active.") Obviously, me, as the author of the back-end. Org offers only one slot for "strong emphasis". I had to choose between bold and alert, and so I did. > Although I'm not happy about manual intervention to convert my prior work, > this is a good step toward consistency. It was odd, in the old framework, > to use headlines for bullet lists and org's numbered lists for numbered > lists. "An org list becomes an output list" is an easier rule to > explain. As explained in this thread, the H:num options item defines a limit between regular headlines and "low-level" headlines. Low level headlines are usually turned into lists during export. But, in the Beamer exporter, it is a better idea to turn them into blocks. Better as in "closer, by its properties, to an headline". > Still, I wonder if there is a way to make the new backend less unfriendly > toward lists. It's an interesting philosophical question: In what cases is > it better for the tool to adapt to the users' wishes, versus cases where > the tool should encourage (Are blocks in the result actually better than > lists? Who says so, and why should I take his or her word for it?) Nobody is saying that blocks are better than lists in the output. It's a matter of taste, isn't it? There are also ways to adapt the tool to your wishes (through hooks, filters, script, macros). > "Reasonably" for me would mean tweaking some configuration options and > perhaps changing a few minor details of the markup. If you have to change > the org document's structure (e.g., converting headlines to lists), it > isn't backward compatible. Then, by this definition, it isn't, indeed. > For comparison: Lilypond updates frequently break some details of backward > compatibility. So, they ship a "convert-ly" script to handle many of those > changes automatically. Even though the required change in our case are rather minimal, they mostly depend on the user configuration. Hence, I will not attempt to provide such a script. But I will provide instructions on how to make the transition, if they are needed. Regards, -- Nicolas Goaziou