From: "Tim Lewis" <tim.lewis@insyde.com>
To: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
<devel@edk2.groups.io>
Subject: Re: [edk2-devel] EDK2 Specs PDF links don't work.
Date: Wed, 19 Aug 2020 13:58:40 -0700 [thread overview]
Message-ID: <04a901d6766b$9d77a310$d866e930$@insyde.com> (raw)
In-Reply-To: <MN2PR11MB44613FD1420A65BA6C4867FCD25D0@MN2PR11MB4461.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Mike –
I miss the ability to search easily off-line. What really confused me is that all of the links for PDF still exist.
Tim
From: Kinney, Michael D <michael.d.kinney@intel.com>
Sent: Wednesday, August 19, 2020 1:08 PM
To: devel@edk2.groups.io; tim.lewis@insyde.com; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: RE: [edk2-devel] EDK2 Specs PDF links don't work.
Hi Tim,
We lost the PDF feature when we moved to the new GitBook and the old one was retired.
If offline PDFs are a must have feature, we have additional work we can do to re-enable.
Mike
From: devel@edk2.groups.io <mailto:devel@edk2.groups.io> <devel@edk2.groups.io <mailto:devel@edk2.groups.io> > On Behalf Of Tim Lewis
Sent: Wednesday, August 19, 2020 11:59 AM
To: devel@edk2.groups.io <mailto:devel@edk2.groups.io>
Subject: [edk2-devel] EDK2 Specs PDF links don't work.
Sorry, I’m new to GitBook, but the PDF links for the specs are not working. It just brings me into the middle of the GitBook HTML pages. I like to have an off-line reference and PDFs worked well in the past. I see the link points to a PDF URL, but the result is still not PDF. I’d prefer not to have to become
Any help is appreciated.
Thanks,
Tim
[-- Attachment #2: Type: text/html, Size: 4097 bytes --]
next prev parent reply other threads:[~2020-08-19 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 18:59 EDK2 Specs PDF links don't work Tim Lewis
2020-08-19 20:07 ` [edk2-devel] " Michael D Kinney
2020-08-19 20:43 ` Kirkendall, Garrett
2020-08-19 20:58 ` Tim Lewis [this message]
2020-08-19 21:26 ` Michael D Kinney
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-list 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='04a901d6766b$9d77a310$d866e930$@insyde.com' \
--to=devel@edk2.groups.io \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox