>
>> - 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

Reply via email to