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: Tue, 31 Jul 2012 18:35:19 -0400 [thread overview]
Message-ID: <CAHRqSkQK6H86cVEjQ5w67jSJBMNf305qdawePv_WXwBPpnb7-A@mail.gmail.com> (raw)
In-Reply-To: <87zk6fk4tt.fsf@gmail.com>
On Tue, Jul 31, 2012 at 5:18 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
>> I've done some further work on the org-e-texinfo exporter and have
>> gotten it to a point where it should be usable with only a few
>> shortcomings.
>
> Thanks for your work. I hope that you will get feedback on it.
>
>> - Two-column tables are restricted to a single "indicating" command,
>> defined by ~org-e-texinfo-def-table-markup~. I'm not sure how to
>> get around these limitations since they are created from description
>> lists (which do not recognize #+attr lines).
>
> What makes you think they don't? Plain lists accept affiliated
> keywords, items don't.
>
I thought I'd tested them against a plain list when trying to find a
way around that limitation. I'll have to try again tomorrow so that I
can eliminate the limitations still present regarding descriptive
lists.
>> Prior to exporting the following must be evaluated:
>>
>> (add-to-list 'org-export-snippet-translation-alist
>> '("info" . "e-texinfo"))
>
> Again, this is an user-oriented variable. You don't need it to accept
> @@info:...@@ export snippets and you shouldn't require the user to set
> it.
>
Usually no, but the sample (orgguide.org) document uses @@info:...@@
to create @kbd, @key and @samp output, without it the document will
fail to export correctly (especially since @ is used for texinfo
commands).
I suppose I should have clarified that those two commands were
required prior to exporting that specific document (for testing and
demonstration purposes).
>
> Regards,
>
> --
> Nicolas Goaziou
Regards,
Jon
next prev parent reply other threads:[~2012-07-31 22:35 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
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 [this message]
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=CAHRqSkQK6H86cVEjQ5w67jSJBMNf305qdawePv_WXwBPpnb7-A@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).