git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: Manlio Perillo <manlio.perillo@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Tue, 26 Jul 2016 07:22:06 -0700	[thread overview]
Message-ID: <50fcb173-8edd-26cd-4828-977d5f1e6b9d@gmail.com> (raw)
In-Reply-To: <CAAToxAFuyzjf1-W4J5v1hpeyn_N4T086nb--+i0dS4QmarW5dQ@mail.gmail.com>



On 7/26/2016 2:15 AM, Manlio Perillo wrote:

> I have noted a problem when reading the PDF with Chromium: the
> anchors/links do not work.

I see what you mean. I was able to replicate the problem with Acrobat
Reader on Windows 10. This seems to happen only with internal links - links
to external URLs work fine.

> I don't know if this is an issue with the conversion to PDF or an
> issue with Chromium.

It's not Chromium.

This is going to be tricky to fix. I'm just using the tool chain
that Scott and Ben set up. I've found other issues too that will
be hard to resolve.

Thanks for the report. I guess for now the best thing to do is
to use the HTML version.

Jon


  reply	other threads:[~2016-07-26 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24  4:07 [ANN] Pro Git Reedited 2nd Edition Jon Forrest
2016-07-24  9:00 ` Jakub Narębski
     [not found]   ` <6f7eea6b-2446-5740-cbec-141d71a33ea1@gmail.com>
2016-07-24 17:19     ` Jakub Narębski
2016-07-24 17:34       ` Jon Forrest
2016-07-24 18:27         ` Jakub Narębski
2016-07-24 18:41           ` Jon Forrest
2016-07-25  7:04             ` Johannes Schindelin
2016-07-24 20:03           ` Jon Forrest
2016-07-26  9:15 ` Manlio Perillo
2016-07-26 14:22   ` Jon Forrest [this message]
2016-08-12 13:11 ` Sitaram Chamarty
2016-08-12 14:37   ` Jon Forrest
2016-08-13  0:30     ` Sitaram Chamarty

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=50fcb173-8edd-26cd-4828-977d5f1e6b9d@gmail.com \
    --to=nobozo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=manlio.perillo@gmail.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://80x24.org/mirrors/git.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).