>>> On 4/30/2017 at 12:40 PM, Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote: >> ... >>Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf >> ... >>Now, on a Linux system I can create a link to that particular >>manual so that it becomes JCL_REF.pdf, but this takes a while to >>do for each manual that I'm interested in. But that's me, how >>many are you interested in? >> > A script could process the index.html file to generate all the links. > >>And if one is a Windows user, can one easily do a link? >> > Lately, Windows has a "mklink" command: > o Requires admin authority. WTF!? > o Must specify whether the link is to a document or to a folder. WTF!? > ... or just use Cygwin and a file manager such as Thunar. > > I just use the index.html file in a browser.
These two things, taken together, is what "wget -k" does. If you do a "wget -k -p" on a web page, you'll get all the elements of the page (excluding those defined in javascript), with the HTML modified to point to the local copy. For myself, I download all the Linux and z/VM presentations from the various SHARE conferences I attend. I wrote a shell script to download all the PDF files, and use the various HTML files to create symbolic links to them using the title of the presentation. It works well enough for my needs. On Linux systems the poppler-tools package contains a "pdfinfo" command that can print things like Title and Author from PDF files that contain them. This could aid in creating symbolic links via scripting as well. Mark Post ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
