emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Internal links in LaTeX export
Date: Thu, 28 Oct 2010 10:44:53 -1000	[thread overview]
Message-ID: <8439CC4F-8895-43F1-BE6A-D8E5A491A908@tsdye.com> (raw)
In-Reply-To: <80y69i5avh.fsf@mundaneum.com>


On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote:

> Hi Thomas,
>
> "Thomas S. Dye" wrote:
>> The manual is silent about what happens to external links on export  
>> to
>> LaTeX. I'm finding that internal links export to HTML and work as  
>> expected
>> there. In the pdf file via LaTeX the internal links are colored,  
>> but aren't
>> active. Is this the expected behavior or am I possibly doing  
>> something that
>> disables the links on their way to pdf?
>
> Internal links always worked for me in PDF, though they more  
> tend(ed) to go
> to the page rather than really placing me on the section (like what  
> you have
> in your browser).
>
> Questions:
>
> - Which PDF reader do you use?  That could influence...
>
> - Do you want me to test some example file?  If yes, send it here, or
>  privately to me -- attention for delays due to spammotel, though.
>
> Best regards,
>  Seb

Thanks Seb,

It doesn't appear to be a reader problem.  The links fail in skim and  
acrobat.

I'm getting this in the LaTeX output:
\href{sec-2_5}{package loading part}

If I read the hyperref documentation correctly, then I think it should  
be:
\hyperref[sec-2_5]{package loading part}

If I'm right about what the link should look like in LaTeX, and there  
is no obvious reason why I'm not getting it in the LaTeX export, then  
I'll work on finding a minimal example.

All the best,
Tom

  reply	other threads:[~2010-10-28 20:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 20:06 Internal links in LaTeX export Thomas S. Dye
2010-10-28 20:18 ` Sébastien Vauban
2010-10-28 20:44   ` Thomas S. Dye [this message]
2010-10-28 21:01     ` Jambunathan K
2010-10-28 21:19       ` Thomas S. Dye
2010-10-28 22:35         ` Nick Dokos
2010-10-29  0:20           ` Thomas S. Dye
2010-10-29  1:30             ` Jambunathan K
2010-10-29  2:04               ` Thomas S. Dye
2010-10-29  3:22                 ` [SOLVED] " Jambunathan K
2010-10-29  3:58                   ` Carsten Dominik
2010-10-29  5:01                     ` Noorul Islam K M
2010-10-29  6:38                       ` Tom Dye
2010-10-29  7:20                       ` Nick Dokos
2010-10-29  7:51                         ` Noorul Islam
2010-10-29  8:34                           ` Nick Dokos
2010-11-13  5:55                       ` [Accepted] " Carsten Dominik
2010-10-29  3:28             ` Nick Dokos
2010-10-29  5:46               ` Nick Dokos
2010-10-29 10:17                 ` Jambunathan K
2010-10-30 19:56                   ` suvayu ali
2010-11-02  7:35                     ` Jambunathan K

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=8439CC4F-8895-43F1-BE6A-D8E5A491A908@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /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).