From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Language identifiers
Date: Mon, 21 May 2012 11:17:27 -0400 [thread overview]
Message-ID: <86fwatr2bc.fsf@mercure.progiciels-bpi.ca> (raw)
In-Reply-To: <22497.1337610879@alphaville> (Nick Dokos's message of "Mon, 21 May 2012 10:34:39 -0400")
Nick Dokos <nicholas.dokos@hp.com> 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çois
next prev parent reply other threads:[~2012-05-21 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 13:48 Language identifiers François Pinard
2012-05-20 17:31 ` Thomas S. Dye
2012-05-20 18:23 ` François Pinard
2012-05-20 18:56 ` Nick Dokos
2012-05-21 14:22 ` François Pinard
2012-05-21 14:34 ` Nick Dokos
2012-05-21 15:17 ` François Pinard [this message]
2012-05-22 23:04 ` Bastien
2012-05-21 9:02 ` Sebastien Vauban
2012-05-21 12:54 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86fwatr2bc.fsf@mercure.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.