From: Carsten Dominik <dominik@uva.nl>
To: Carsten Dominik <dominik@uva.nl>, org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Cross reference in TeXinfo export
Date: Thu, 1 Aug 2019 15:47:48 +0200 [thread overview]
Message-ID: <CADn3Z2+0vYSwdsBa_ux2W4h+9TR4kjhPsXHYmo7=KOc=CC365w@mail.gmail.com> (raw)
In-Reply-To: <871ryrobgz.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi Nicolas,
thank you for that pointer. I'll see if I can figure out what is going on
and if I can propose a solution.
Carsten
On Mon, Jul 15, 2019 at 12:10 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Carsten Dominik <dominik@uva.nl> writes:
>
> > I noticed that the link in the following line in org-guide.org
> >
> > This document is a much compressed derivative of the
> > [[info:org][comprehensive Org mode manual]].
> >
> >
> > gets turned into this in orgguide.texi
> >
> > @ref{Top,comprehensive Org mode manual,,org,}.
> >
> >
> > The PDF version of the guide then looks like this:
> >
> > This document is a much compressed derivative of the org.
> >
> >
> > So the link description in the PDF version is just "org", the name of the
> > info node. I think the link text should be "comprehensive Org mode
> > manual". Is anyone familiar enough with the texinfo exporter and texinfo
> > to fix this?
>
> Actually, this is not about the Texinfo exporter (ox-texinfo.el), but
> the library responsible for handling info links (ol-info.el).
>
> Maybe we should use
>
> @ref{Top,comprehensive Org mode manual,,org,comprehensive Org mode
> manual}
>
> instead. But what should we do when a section is specified, e.g.,
>
> @ref{Section Name, description,,org,}
>
> ?
>
> Regards,
>
> --
> Nicolas Goaziou
>
>
[-- Attachment #2: Type: text/html, Size: 2029 bytes --]
prev parent reply other threads:[~2019-08-01 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 6:50 Cross reference in TeXinfo export Carsten Dominik
2019-07-15 10:09 ` Nicolas Goaziou
2019-08-01 13:47 ` Carsten Dominik [this message]
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='CADn3Z2+0vYSwdsBa_ux2W4h+9TR4kjhPsXHYmo7=KOc=CC365w@mail.gmail.com' \
--to=dominik@uva.nl \
--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).