From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "François Pinard" <pinard@iro.umontreal.ca>,
"Org Mode Mailing List" <emacs-orgmode@gnu.org>
Subject: Re: Export to Texinfo
Date: Fri, 20 Jul 2012 09:34:37 -0400 [thread overview]
Message-ID: <CAEWDx5dA1J07x2f4QhcT75hm0CJZ43hucMBO6_EaQ1yf9Pk+1g@mail.gmail.com> (raw)
In-Reply-To: <87y5meaib9.fsf@gmail.com>
>
>> - The largest issue perhaps: There is no method to create @kbd{} and
>> @key{} commands on export. If anyone has any suggestions how these
>> might be achieved (perhaps looking for a prefix in =code=?) I would
>> greatly appreciate it.
>
> You can probably use export-snippets:
>
> An important key: @@e-info:@kbd{C-c C-c}@@.
Can I define the export-snippet using:
(add-to-list 'org-export-snippet-translation-alist
'("e-info" . "e-texinfo"))
Or should that be left up to the discretion of the user?
>> There are a few limitations to what will successfully be exported:
>> - Headlines cannot contain any of the following symbols: periods,
>> commas, colons or parentheses. This is a limitation of texinfo and
>> will result in errors when running makeinfo. Semi-colons will
>> export however.
>
> Can't you protect these chars?
Unfortunately you can't currently. I'm using the Headlines both as
section heading and Node heading. The Nodes cannot contain those
characters. This also means that you cannot have duplicate headline
names in the document.
See http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Node-Line-Requirements.html
I should be able to get around this by allowing for a :NODE: property
for use in the menus however, if there is some benefit in doing so.
>
>
> Regards,
>
> --
> Nicolas Goaziou
Regards,
Jon
next prev parent reply other threads:[~2012-07-20 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 0:29 Export to Texinfo Jonathan Leech-Pepin
2012-07-20 9:32 ` Nicolas Goaziou
2012-07-20 13:34 ` Jonathan Leech-Pepin [this message]
2012-07-20 13:42 ` Nicolas Goaziou
2012-07-31 21:03 ` Jonathan Leech-Pepin
2012-07-31 21:18 ` Nicolas Goaziou
2012-07-31 22:35 ` Jonathan Leech-Pepin
2012-07-31 23:45 ` Jonathan Leech-Pepin
2012-08-02 15:34 ` Bastien
[not found] ` <CAHRqSkQTzE-OYmTFs+BRjrER=jgS3=2BE5Yi4A6v8ipaZ1kWQA@mail.gmail.com>
2012-08-02 22:24 ` Fwd: " Jonathan Leech-Pepin
2012-08-03 7:29 ` Bastien
2012-08-03 8:41 ` Nicolas Goaziou
2012-08-03 13:30 ` Jonathan Leech-Pepin
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=CAEWDx5dA1J07x2f4QhcT75hm0CJZ43hucMBO6_EaQ1yf9Pk+1g@mail.gmail.com \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--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).