Hi Jonathan,
Jonathan Leech-Pepin 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 *a lot* for this! This is long-time wish from many org-ers,
no doubt you will have many tester
On 31 July 2012 18:35, Jonathan Leech-Pepin
wrote:
> On Tue, Jul 31, 2012 at 5:18 PM, Nicolas Goaziou wrote:
>> Hello,
>>
>> Jonathan Leech-Pepin 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
>
On Tue, Jul 31, 2012 at 5:18 PM, Nicolas Goaziou wrote:
> Hello,
>
> Jonathan Leech-Pepin 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 wi
Hello,
Jonathan Leech-Pepin 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 sin
Jonathan Leech-Pepin writes:
> 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?
This is an user-oriented variable (customizable).
Though, y
>
>> - 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
Hello,
Jonathan Leech-Pepin writes:
> Over the last few days I've been working on implementing an Org ->
> Texinfo exporter based on the new e-latex exporter.
Argh. While your idea is nice, starting from `e-latex' exporter is
almost certainly a bad move. Indeed, it is a quite convoluted back-en
