Bug? in texinfo exporter

Bug? in texinfo exporter

[Thomas S. Dye]

Aloha all,

The following text:

  LaTeX math snippets (see [[LaTeX fragments]])

is being exported to texinfo like this:

  @LaTeX{} math snippets (see @ref{@LaTeX{} fragments,})
                                                     ^

I think the marked comma is giving makeinfo a heartache.  Makeinfo tells me:

  /Users/dk/org/orgmanual//orgmanual.texi:11726: Cross reference to
  nonexistent node `@LaTeX{} fragments' (perhaps incorrect sectioning?).

Help?

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: Bug? in texinfo exporter

[Nicolas Goaziou]

Hello,

tsd@tsdye.com (Thomas S. Dye) writes:

> The following text:
>
>   LaTeX math snippets (see [[LaTeX fragments]])
>
> is being exported to texinfo like this:
>
>   @LaTeX{} math snippets (see @ref{@LaTeX{} fragments,})
>                                                      ^
>
> I think the marked comma is giving makeinfo a heartache.  Makeinfo tells me:
>
>   /Users/dk/org/orgmanual//orgmanual.texi:11726: Cross reference to
>   nonexistent node `@LaTeX{} fragments' (perhaps incorrect sectioning?).
>
> Help?

It should be fixed in master. Could you confirm it?

Thank you for reporting this.


Regards,

-- 
Nicolas Goaziou

Fwd: Re: Bug? in texinfo exporter

[Jonathan Leech-Pepin]

[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]

---------- Forwarded message ----------
From: "Jonathan Leech-Pepin" <jonathan.leechpepin@gmail.com>
Date: Feb 9, 2013 8:57 AM
Subject: Re: [O] Bug? in texinfo exporter
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc:
Just realized I hit reply not reply-all

If Nick's fix fixes it do much the better.com but I'm pretty sure the comma
isn't the culprit.

Regards,
> Hello Tom,
>
> On Feb 8, 2013 10:11 PM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
> >
> > Aloha all,
> >
> > The following text:
> >
> >   LaTeX math snippets (see [[LaTeX fragments]])
> >
> > is being exported to texinfo like this:
> >
> >   @LaTeX{} math snippets (see @ref{@LaTeX{} fragments,})
> >                                                      ^
> >
> > I think the marked comma is giving makeinfo a heartache.  Makeinfo
tells me:
> >
>
> The issue is more likely that it is escaping LaTeX within the reference
while the headline had it literally.
>
> I'm not at a computer right now but I should be able to look into it and
hopefully fix it this week.
>
> >   /Users/dk/org/orgmanual//orgmanual.texi:11726: Cross reference to
> >   nonexistent node `@LaTeX{} fragments' (perhaps incorrect sectioning?).
> >
> > Help?
> >
> > All the best,
> > Tom
> >
>
> Regards,
>
> Jon
>
> > --
> > T.S. Dye & Colleagues, Archaeologists
> > 735 Bishop St, Suite 315, Honolulu, HI 96813
> > Tel: 808-529-0866, Fax: 808-529-0884
> > http://www.tsdye.com
> >

[-- Attachment #2: Type: text/html, Size: 2207 bytes --]

Re: Fwd: Re: Bug? in texinfo exporter

[Thomas S. Dye]

Aloha Jon,

Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:

> ---------- Forwarded message ----------
> From: "Jonathan Leech-Pepin" <jonathan.leechpepin@gmail.com>
> Date: Feb 9, 2013 8:57 AM
> Subject: Re: [O] Bug? in texinfo exporter
> To: "Thomas S. Dye" <tsd@tsdye.com>
> Cc:
> Just realized I hit reply not reply-all
>
> If Nick's fix fixes it do much the better.com but I'm pretty sure the comma
> isn't the culprit.

Yes, I believe you are right.  The commas are not the culprits.
Apologies for the red herring.

Perhaps Nicolas should revert the commit?  Could you check if this is
the right thing to do?

I *have* found a bug/limitation of the texinfo exporter.  If a link is
split between two lines the exporter doesn't handle it correctly.  A
split link is exported like @ref{A-split-link}, when it should be @ref{A
split link}, I think.

If this is a limitation, please let me know so I can put all the links
on one line.  

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Fwd: Re: Bug? in texinfo exporter

[Nicolas Goaziou]

tsd@tsdye.com (Thomas S. Dye) writes:

> Aloha Jon,

[...]

> Yes, I believe you are right.  The commas are not the culprits.
> Apologies for the red herring.
>
> Perhaps Nicolas should revert the commit?  Could you check if this is
> the right thing to do?

My fix isn't about the comma. Didn't it work?

> I *have* found a bug/limitation of the texinfo exporter.  If a link is
> split between two lines the exporter doesn't handle it correctly.  A
> split link is exported like @ref{A-split-link}, when it should be @ref{A
> split link}, I think.
>
> If this is a limitation, please let me know so I can put all the links
> on one line.

There's no such limitation. Could you provide an ECM for that?


Regards,

-- 
Nicolas Goaziou

Re: Fwd: Re: Bug? in texinfo exporter

[Jonathan Leech-Pepin]

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

On Feb 11, 2013 1:59 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
> > Aloha Jon,
>
> [...]
>
> > Yes, I believe you are right.  The commas are not the culprits.
> > Apologies for the red herring.
> >
> > Perhaps Nicolas should revert the commit?  Could you check if this is
> > the right thing to do?
>
> My fix isn't about the comma. Didn't it work?
>

Your fix seems to have worked from what I can see (it was what I was
thinking of fixing at least). The comma was Tom's initial guess.

> > I *have* found a bug/limitation of the texinfo exporter.  If a link is
> > split between two lines the exporter doesn't handle it correctly.  A
> > split link is exported like @ref{A-split-link}, when it should be @ref{A
> > split link}, I think.
> >
> > If this is a limitation, please let me know so I can put all the links
> > on one line.
>
> There's no such limitation. Could you provide an ECM for that?
>
I think Tom might be referring to when a line is hard wrapped with M-q. It
seems to affect the description of the org link to escape the spaces. I'm
not sure what effect this has on export. From what Tom is saying it isn't
unescaping the text.

Regards,
Jon
>
> Regards,
>
> --
> Nicolas Goaziou

[-- Attachment #2: Type: text/html, Size: 1742 bytes --]

Re: Fwd: Re: Bug? in texinfo exporter

[Nicolas Goaziou]

Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:

> On Feb 11, 2013 1:59 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
>>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>> > Aloha Jon,
>>
>> [...]
>>
>> > Yes, I believe you are right.  The commas are not the culprits.
>> > Apologies for the red herring.
>> >
>> > Perhaps Nicolas should revert the commit?  Could you check if this is
>> > the right thing to do?
>>
>> My fix isn't about the comma. Didn't it work?
>>
>
> Your fix seems to have worked from what I can see (it was what I was
> thinking of fixing at least). The comma was Tom's initial guess.

Actually, an `org-export-solidify-link-text' may be needed (along with
the receiver part of the link), in case one of the properties that were
previously transcoded contains a forbidden character. I let you decide
about it.


Regards,

-- 
Nicolas Goaziou

Re: Fwd: Re: Bug? in texinfo exporter

[Thomas S. Dye]

Aloha Nicolas and Jon,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha Jon,
>
> [...]
>
>> Yes, I believe you are right.  The commas are not the culprits.
>> Apologies for the red herring.
>>
>> Perhaps Nicolas should revert the commit?  Could you check if this is
>> the right thing to do?
>
> My fix isn't about the comma. Didn't it work?

The particular link I used in the example now works. Thanks. I wasn't
sure what was done and worried that my red herring had made it into the
code.  Glad to know that it didn't.

>
>> I *have* found a bug/limitation of the texinfo exporter.  If a link is
>> split between two lines the exporter doesn't handle it correctly.  A
>> split link is exported like @ref{A-split-link}, when it should be @ref{A
>> split link}, I think.

> There's no such limitation. Could you provide an ECM for that?

Yes, here is an ECM.

--------- Begin ECM ----------

* A long headline that typically breaks across lines with M-q

Blah.

* Concise  headline

The problem comes with links that are split across lines, e.g. [[A
long headline that typically breaks across lines with M-q]]. They work
in the Org mode buffer, but not when exported to texinfo.

* Editing setup
#+name: setup-editing
#+header: :results silent
#+header: :eval no-export
#+begin_src emacs-lisp
(require 'ox-texinfo)
(define-key org-mode-map (kbd "C-c e") 'org-export-dispatch)
(setq org-pretty-entities nil)
(setq org-src-preserve-indentation t)
(setq org-confirm-babel-evaluate nil)
(org-babel-do-load-languages
 'org-babel-load-languages
 '((emacs-lisp . t)
   (sh . t)))
(add-to-list 'org-export-snippet-translation-alist
             '("info" . "e-texinfo"))
#+end_src

---------- End ECM -----------

Here is the makeinfo output:

poto:orgmanual dk$ makeinfo --force org-texi-link.texi
/Users/dk/org/orgmanual//org-texi-link.texi:55: Cross reference to nonexistent node `A-long-headline-that-typically-breaks-across-lines-with-M-q' (perhaps incorrect sectioning?).

Note the hyphens between the words of the headline/link.

All the best,
Tom
-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: Fwd: Re: Bug? in texinfo exporter

[Nicolas Goaziou]

tsd@tsdye.com (Thomas S. Dye) writes:

> --------- Begin ECM ----------
>
> * A long headline that typically breaks across lines with M-q
>
> Blah.
>
> * Concise  headline
>
> The problem comes with links that are split across lines, e.g. [[A
> long headline that typically breaks across lines with M-q]]. They work
> in the Org mode buffer, but not when exported to texinfo.
>
> * Editing setup
> #+name: setup-editing
> #+header: :results silent
> #+header: :eval no-export
> #+begin_src emacs-lisp
> (require 'ox-texinfo)
> (define-key org-mode-map (kbd "C-c e") 'org-export-dispatch)
> (setq org-pretty-entities nil)
> (setq org-src-preserve-indentation t)
> (setq org-confirm-babel-evaluate nil)
> (org-babel-do-load-languages
>  'org-babel-load-languages
>  '((emacs-lisp . t)
>    (sh . t)))

> (add-to-list 'org-export-snippet-translation-alist
>              '("info" . "e-texinfo"))

Note: this should be '("info" . "texinfo") as the back-end has been
renamed.

> #+end_src
>
> ---------- End ECM -----------
>
> Here is the makeinfo output:
>
> poto:orgmanual dk$ makeinfo --force org-texi-link.texi
> /Users/dk/org/orgmanual//org-texi-link.texi:55: Cross reference to nonexistent node `A-long-headline-that-typically-breaks-across-lines-with-M-q' (perhaps incorrect sectioning?).
>
> Note the hyphens between the words of the headline/link.

The bug should be fixed now. Could you confirm it?

Thank you very much for the ECM.


Regards,

-- 
Nicolas Goaziou

Re: Fwd: Re: Bug? in texinfo exporter

[Thomas S. Dye]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

>> (add-to-list 'org-export-snippet-translation-alist
>>              '("info" . "e-texinfo"))
>
> Note: this should be '("info" . "texinfo") as the back-end has been
> renamed.

Good eye.  Thanks.

>> Here is the makeinfo output:
>>
>> poto:orgmanual dk$ makeinfo --force org-texi-link.texi
>> /Users/dk/org/orgmanual//org-texi-link.texi:55: Cross reference to
>> nonexistent node
>> A-long-headline-that-typically-breaks-across-lines-with-M-q'
>> (perhaps incorrect sectioning?).
>>
>> Note the hyphens between the words of the headline/link.
>
> The bug should be fixed now. Could you confirm it?

Fixed.  Thanks.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com