From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [new exporter][texinfo] Macro definition section
Date: Mon, 12 Nov 2012 09:58:16 -0500 [thread overview]
Message-ID: <CAEWDx5ctQ25GGjTtg-VEZJEd1bdQDJZnPkHB=x31JpwngQNaoQ@mail.gmail.com> (raw)
In-Reply-To: <m1obj399fb.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Hello, (helps if I hit paste before hitting send)
On 11 November 2012 15:22, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha all,
>
> The texinfo source for the Org manual has a number of macro definitions
> for commands and keys between the end of the header (@finalout) and the
> beginning of the Copying section.
>
> The texinfo back-end for the new exporter doesn't have a slot here and
> I'm wondering if it needs one?
>
>
I believe I accounted for most of the special strings that are
directly transcoded in texinfo. There may be some that are missing,
however they can be added directly in the document using the
=@@info:<texinfo command>@@= syntax (inline export snippets).
Are there any particular pieces of synxtax that you believe would be
useful to have added to org-entities that would also be useful in
other backends?
> All the best,
> Tom
> --
> T.S. Dye & Colleagues, Archaeologists
> 735 Bishop St, Suite 315, Honolulu, HI 96813
> Tel: 808-529-0866, Fax: 808-529-0884
> http://www.tsdye.com
>
>
Regards,
--
Jon
[-- Attachment #2: Type: text/html, Size: 1733 bytes --]
next prev parent reply other threads:[~2012-11-12 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 20:22 [new exporter][texinfo] Macro definition section Thomas S. Dye
2012-11-12 14:57 ` Jonathan Leech-Pepin
2012-11-12 14:58 ` Jonathan Leech-Pepin [this message]
2012-11-12 18:03 ` Thomas S. Dye
2012-11-12 18:39 ` Jonathan Leech-Pepin
2012-11-12 22:52 ` François Pinard
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='CAEWDx5ctQ25GGjTtg-VEZJEd1bdQDJZnPkHB=x31JpwngQNaoQ@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).