From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Date: Fri, 2 Apr 2021 09:39:11 +0530 [thread overview]
Message-ID: <TY2PR0101MB3693C878446FF4826BC5FD5EDA7A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <87k0pmhw6a.fsf@nicolasgoaziou.fr>
On 01/04/21 8:46 pm, Nicolas Goaziou wrote:
> Hello,
>
> Ramesh Nedunchezian <rameshnedunchezian@outlook.com> writes:
>
>> When I export the following snippet to TexInfo format the export fails.
>>
>>
>> ** To add a package: (submission, submit)
>>
>> Adding a basic package is very simple. There are thorough
>
> This should now be fixed. Thank you.
This fixes the issue I reported. Thanks.
FWIW, TexInfo manual has a bunch of gotchas here:
(info "(texinfo) Node Line Requirements")
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Node-Line-Requirements.html
The following are the lines that seem relevant to the problem at hand.
* Unfortunately, you cannot reliably use periods, commas, or colons
within a node name; these can confuse the Info reader.
Also, if you insist on using these characters in node names
(accepting the resulting substandard Info output), in order not to
confuse the Texinfo processors you must still escape those
characters, by using either special insertions (*note Inserting a
Comma::) or '@asis' (*note @asis::). For example:
@node foo@asis{::}bar
As an example of avoiding the special characters, the following is
a section title in this manual:
@section @code{@@unnumbered}, @code{@@appendix}: ...
But the corresponding node name lacks the commas and the subtitle:
@node @unnumbered @appendix
next prev parent reply other threads:[~2021-04-02 4:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 8:17 Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)] Ramesh Nedunchezian
2021-04-01 15:16 ` Nicolas Goaziou
2021-04-02 4:09 ` Ramesh Nedunchezian [this message]
2021-04-02 14:50 ` Nicolas Goaziou
2021-04-02 4:33 ` Ramesh Nedunchezian
2021-04-02 14:59 ` Nicolas Goaziou
2021-04-03 4:44 ` Ramesh Nedunchezian
2021-04-03 9:26 ` Nicolas Goaziou
2021-04-03 11:41 ` Ramesh Nedunchezian
2021-04-03 14:40 ` Ramesh Nedunchezian
2021-04-03 14:50 ` Ramesh Nedunchezian
2021-04-03 19:50 ` Nicolas Goaziou
2021-04-04 4:26 ` Ramesh Nedunchezian
2021-04-07 17:59 ` Nicolas Goaziou
2021-04-08 14:00 ` Ramesh Nedunchezian
2021-04-19 9:30 ` Nicolas Goaziou
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=TY2PR0101MB3693C878446FF4826BC5FD5EDA7A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \
--to=rameshnedunchezian@outlook.com \
--cc=emacs-orgmode@gnu.org \
/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).