From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Is it possible to keep /all/ the heading properties in one place? Date: Mon, 29 Feb 2016 11:05:53 +0100 Message-ID: <87egbvesqm.fsf@nicolasgoaziou.fr> References: <87fuwht5s3.fsf@gmail.com> <87lh683o7c.fsf@nicolasgoaziou.fr> <878u28ucl8.fsf@gmail.com> <878u283n15.fsf@nicolasgoaziou.fr> <87oab4sw70.fsf@gmail.com> <87h9gw20mi.fsf@nicolasgoaziou.fr> <87a8mooazg.fsf@gmail.com> <87a8mo1r69.fsf@nicolasgoaziou.fr> <87h9gvrijp.fsf@gmail.com> <87ziulb48b.fsf@nicolasgoaziou.fr> <87vb59ni5w.fsf@oremacs.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaKgB-00040N-8i for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 05:03:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaKgA-0001Jy-AT for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 05:03:51 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:49294) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaKgA-0001In-3y for emacs-orgmode@gnu.org; Mon, 29 Feb 2016 05:03:50 -0500 In-Reply-To: (Thomas S. Dye's message of "Sun, 28 Feb 2016 06:34:31 -1000") 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: "Thomas S. Dye" Cc: emacs-orgmode@gnu.org, Oleh Krehel , Oleh Krehel Hello, Thomas S. Dye writes: > I worked on a project to port the Org manual to Org about three years > ago. At the time, I thought the Texinfo exporter supported the project > quite well. > > The project had a mixed reception and ultimately wasn't adopted, but I > don't remember Texinfo exporter deficiencies figuring into the > decision. AFAIR, the problem is that Emacs developers fix spelling issues right into the ".texi" document, so we would need to backport each of their changes into the Org source. Duplicated efforts. However, I still think it would be nice to have the document somewhere in the Org tree, perhaps in contrib/ as a start, then possibly one day in doc/. As a side note, another interesting project would be an "info" export back-end. Currently, producing an info file is very slow because we go through the "texinfo" format first. Regards, -- Nicolas Goaziou