all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carsten Dominik <dominik@uva.nl>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Cross reference in TeXinfo export
Date: Mon, 15 Jul 2019 12:09:48 +0200	[thread overview]
Message-ID: <871ryrobgz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADn3Z2KmGf2MPRjNuf5LvV7yLLVZQZm04prdvMf2apbVLvU1Dw@mail.gmail.com> (Carsten Dominik's message of "Mon, 15 Jul 2019 08:50:49 +0200")

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

  reply	other threads:[~2019-07-15 10:09 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 [this message]
2019-08-01 13:47   ` Carsten Dominik

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871ryrobgz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.