From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Fran=C3=A7ois_Pinard?= Subject: Re: Language identifiers Date: Mon, 21 May 2012 11:17:27 -0400 Message-ID: <86fwatr2bc.fsf@mercure.progiciels-bpi.ca> References: <86r4uf9d5f.fsf@mercure.progiciels-bpi.ca> <86mx52aezy.fsf@mercure.progiciels-bpi.ca> <4555.1337540206@alphaville> <86pq9xr4vl.fsf@mercure.progiciels-bpi.ca> <22497.1337610879@alphaville> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWUMa-0004vO-3s for emacs-orgmode@gnu.org; Mon, 21 May 2012 11:17:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SWUMU-00019N-1n for emacs-orgmode@gnu.org; Mon, 21 May 2012 11:17:35 -0400 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:53634 helo=mercure.progiciels-bpi.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWUMT-00018x-S2 for emacs-orgmode@gnu.org; Mon, 21 May 2012 11:17:29 -0400 In-Reply-To: <22497.1337610879@alphaville> (Nick Dokos's message of "Mon, 21 May 2012 10:34:39 -0400") 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: emacs-orgmode@gnu.org Nick Dokos writes: >> If the real source of the manual was in Org format, and periodically and >> mechanically turned into a Texinfo file, would the requirement be met? > Yes, but somebody would have to write a good texinfo exporter. Oh! I did not even know that none exist yet. Well, indeed, that's a problem! :-) Ah! If I only had more time, I would dive right away and start writing one. *Still dreaming awake*, that would be a wonderful opportunity for me to learn the new exporter which, according to what I've read on this list, fixes an opinion about what is the proper structural analysis of an Org file. My usual language is Python, which I came to much prefer over Emacs Lisp, years ago. Proof is that I once wrote something so I can extend Emacs with Python instead of Lisp. A good way to study the new exporter's opinion would be for me to write a Python parser which yields exactly the same analysis. That parser could usefully replace many Python scripts here which decipher Org files according to my mental fuzzy approximations of its syntax. Second, writing a Texinfo exporter would be a pleasurable incentive to check its usefulness. :-) Sigh! Fran=C3=A7ois