From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois_Pinard?= <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Language identifiers
Date: Sun, 20 May 2012 14:56:46 -0400 [thread overview]
Message-ID: <4555.1337540206@alphaville> (raw)
In-Reply-To: Message from =?utf-8?Q?Fran=C3=A7ois_Pinard?= <pinard@iro.umontreal.ca> of "Sun\, 20 May 2012 14\:23\:13 EDT." <86mx52aezy.fsf@mercure.progiciels-bpi.ca>
François Pinard <pinard@iro.umontreal.ca> wrote:
> If I had to do this, I would search around to see if there is an Org to
> Texinfo exporter, and then blindly / fully rely on it to do various
> wonders automatically! ;-) I did not check, but presume that the current
> manual original is directly written in Texinfo?
>
That's correct: that's a requirement for being an official emacs package
I believe.
> More seriously, I did not write Texinfo in a lot of years, and do not
> even remember how we do tables with it. Tables might have been added
> after my time, I'm not sure. What I would likely do, given the problem,
> is merely to format the table myself in fixed font, and use @example /
> @end example around it (if I remember well, @example generates <pre>).
> Would that be acceptable?
>
> I could offer that simple formatting if it could help, I presume it is
> likely a simple job for anybody. The problem for me is rather to know
> what contents should go in there. Write to me privately if you think I
> could be more of an help than a burden. :-)
>
You don't really need to know texinfo: just look at relevant place(s)
in doc/org.texi, and munge it until it does what you want :-)
Nick
next prev parent reply other threads:[~2012-05-20 18:56 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 [this message]
2012-05-21 14:22 ` François Pinard
2012-05-21 14:34 ` Nick Dokos
2012-05-21 15:17 ` François Pinard
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4555.1337540206@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).