Home Articles Forums Gallery Marketplace Videos

WoodCentral Forums

Knowledge You Can Build On — Est. 1998

Compare cordless drills on the numbers that matter

OT Changing Webpages to PDF Files

Posts

OT Changing Webpages to PDF Files

#1

Alan Young

OT Changing Webpages to PDF Files

Alan Young

>Can any of the Microsoft Office application change web pages into PDF files? If so can you point the way?

I am trying to consolidate my webpage. Basically I have saved every photo I know I want to keep, and made separate files according to the pages and projects. When I am satisfied I have it all saved separate from the webpage software platform, I am going to delete the entire site and rebuild it from the ground up. I have so many files in the site now with odd titles ie..named by the digital camera number, that I can't easily delete the unwanted files without opening EVERYONE...ugh!

Alan

Re: OT Changing Webpages to PDF Files

#2

Re: OT Changing Webpages to PDF Files

Bill Hammond, Oregon Coast

>If I understand you, this may help. There is a plugin for FireFox that will convert the web page you are looking at to a PDF file.

Bill

Re: OT Changing Webpages to PDF Files

#3

Re: OT Changing Webpages to PDF Files

John E in SC

>Not sure how it would deal with a web page, but google "PDF factory" and check that out. My office uses that to send files between partners, because a few insist on using other word processing programs than Word, and with PDF, anyone can open it.

HTH,

John

Re: OT Changing Webpages to PDF Files

#4

Before you get to far along…

Rod Peterson -- Ormond Beach

>I don't know that a website of PDFs is such a good idea. First, many people despise links that open PDFs. Much of that was due to dial up connections and nowadays with many (not all) people on broadband, that may be less of an issue. Secondly, if you ever have to edit any of your pages you're going to wind up doing exactly what you're complaining about now, searching for files with inexplicable names. If you do it, you're committing yourself to a static site when the web is really designed to be dynamic—if not with the actual on-the-fly page generation, then at least in the ability to add, subtract, or other wise revise your content. Yes, even improve.

As I understand it, your chief problem is unidentifiable images (because of ambiguous or randomly assigned names). Here's a protocol I use with all of my graphics. While I try to always retain an original image, even with its DSC01341.jpg name, I always save a copy of it with a unique and understandable filename (rods-ugly-mug.jpg) and I append a “-org” signifying an original image (or first generation copy of it). The filename would then look like: rods-ugly-mug-org.jpg.

The one good thing to come out of m$ was the abandonment of the 8.3 filename convention. It took me years to quit trying to compress a file name into eight characters. Nowadays, you probably don't even need to avoid spaces, although I'll probably never never get comfortable not connecting every element in the filename with either “-” or “_”.

Once you have filenames that make sense, your stated reason for going PDF goes away. Since you're going to go through every file anyway to do the conversion, why not just rename them as I suggest and stay with HTML? Yes, it's going to be a massive task. I've gone through my complete Norm's Tools website at least four times doing major revisions (introducing CSS, for example). Yes, it's a pain. But the end result makes further work so much easier it's worth biting the bullet.

Rod

Re: OT Changing Webpages to PDF Files

#5

Re: OT Changing Webpages to PDF Files

Dan Donaldson

>Call me the neighborhood dummy, but I am not clear on what you plan to gain to use PDF's or how you plan to use them. I, for one, am one of the people that Rod mentioned that hates PDF's. The only reason that I can usually see to use them is if you have content that you want protected so that no one can change it. (We do that at work for that reason, and password protect them from changes) I would try to map out exactly what you are trying to accomplish and then look at the best alternatives to achieve the goal. Unless I am missing something, I am not convinced that a PDF is the way to do it.

Re: OT Changing Webpages to PDF Files

#6

Re: OT Changing Webpages to PDF Files

Alex Grigoriev

>Even though Front Page is frown upon by "gurus", it's adequate for most sites.

It will show you all "unlinked" files, and you'll be able to delete them. You can also rename any file, and al links to it will be updated automatically. I'm pretty sure competing applications for website editing also have these features.

But converting web stuff to PDF is absolutely unnecessary. There is no advantages in that.

Re: OT Changing Webpages to PDF Files

#7

Alan Young

Rod and Dan....

Alan Young

>Thanks for your comments and design inclinations. I think I am in general agreement. My intention for the PDF files is for a very small select number of pages-basically the "Newsletters" that I send out two or three time a year to my family and client base. Those pages function as archives and I thought a PDF file would work best for those particular pages. It was my understanding that a picture embedded in a PDF file won't show up as a separate jpg file in my web site's main directory. Perhaps I am mistaken on that assumption.

As far as giving specific names to pictures-That is a protocol I failed to establish from the beginning-because I am king of Gratification NOW!.... I failed to give freshly added pictures discrete file names because I was in too much of a hurry and I didn't take the time to set up a logical system of naming projects.

About 6 months ago I did slim down the actual pages and gave them all the same backround and top heading and menue. I also took off a fair number of pictures that appear on any given page. But the base structure still contains too many pictures-most of them are "here's how I drilled a hole in this block of wood" progress shots. such as:

http://www.woodwardwoodworks.com/DCP_6911.JPG

They are helpful for documentation purposes for clients to see things taking shape and to post here as the occasion warrants, but my space allotment is growing full so as new projects come on line I am running out of room-even without the progress shots, and I don't want to spend more $ just to get more space for files I am not using.

So I guess you could say I am putting the webpage on a new digital diet. I need to shed quite a few jpgs and the new ones that do get added will be properly named so I can more easily remove them down the line just by reading their titles....

Alan

Re: OT Changing Webpages to PDF Files

#8

Re: Before you get to far along�

John McGaw

>I have to admit that I still haven't figured out how converting existing pages to PDF would possibly help in creating a new website so I didn't bother to offer an opinion. I'm certainly no pro at it but simply creating a new directory to contain the new website during development, copying those elements, JPGs, graphics, etc. from the preceding version of the website to the new directory and then starting to write HTML and CSS has always worked fine for me. Renaming the JPGs is fine although that might not even be helpful since all manner of description can be placed in the EXIF data included with the image. Typically, the person viewing the site will never have to be bothered with the name so 0001.jpg, 0002.jpg,... would serve just as well for purposes of the HTML and would not deprive them of any required information.

Re: OT Changing Webpages to PDF Files

#9

Re: Rod and Dan....

Rod Peterson -- Ormond Beach

>I don't want to get into a whole rework-Alan-on-line thing (not that it wouldn't be fun…) but when you talk about running out of room and you're using a website for business, you have the wrong host. You need need to get another one with more capacity. I have more space on my host than I could possibly use if I was writing a new site every day. I'm talking tens of gigabytes of storage, and a ton of bandwidth (I'm not CNN or ESPN so I'm sure I'm still under the radar in terms of bandwidth).

The other thing I'm getting a hint of is organization. It sounds (I could have misinterpreted it) as if you have all of your images in the same directory as all of your HTML files. NO, NO, NO. At the very least you should have an “images” subdirectory. In my case, as a website developer, my hard drive and my host site are all organized so that each client has their own subdirectory, each of which has all the HTML and CSS files in it, then each subdirectory has an “images” subdirectory unique to the client.

Sometimes I add another subdirectory off the client main for PDFs (didn't say I didn't use them—they do have applications, occasionally), for isolation (my slide show routines pick their images on the fly, so I have to separate them from the regular images), and possibly other applications I want to keep separate from the foundation files of each site.

You can recover. You are generally going to have to, anyway, because even with the fix you have in mind, things are going to get worse again. Here's the obligatory woodworking reference: it's like cleaning the shop (may the gods of irony not strike me down for using a shop cleanliness simile)—it hurts, and it takes time out of the fun/routine, but you have to do it periodically or you'll be hip deep in detritus and unable to work at all. The website is no different.

Gird your loins, grit your teeth, forget the instant gratification—get in there and start organizing. You'll be the better man for it. You may even thank me, if I haven't been struck down. Buy me a bottle of water…

Rod

Re: OT Changing Webpages to PDF Files

#10

Re: Before you get to far along�

Rod Peterson -- Ormond Beach

>I'm not suggesting the renaming of the images for the user. I'm talking about it for the convenience of the developer (Alan, in this case). And of course the real tool to provide useful info to the user is the TITLE/ALT tags in the IMG code. Rigorous and proper use of those can be all the user enhancement needed.

Yeah, rebuilding in a shadow drive/directory is certainly the way to do it, particularly if one wants to keep the site live while it's being rebuilt.

Rod

Re: OT Changing Webpages to PDF Files

#11

Re: OT Changing Webpages to PDF Files *LINK*

Robby Wright

>Alan - There is a free utility that I like for making PDF files. It is called CutePDF and acts like a printer on your computer. Just download (URL below) and install it. You will probably need to install Ghostscript also - The directions are on the webpage below. CutePDF acts as a printer. You can make anything you can print into a PDF file. Works like a charm.

Robby W.


CutePDF

Re: OT Changing Webpages to PDF Files

#12

Adobe Acrobat Standard/Pro

Mark Goodall - ATL - tooljunkie

>Sorry, haven't had time to read the other responses so I apologize in advance if someone has already said this.

Everyone knows that Adobe Acrobat Reader is free, but all you need to do is find someone who has the Acrobat Std or Pro sfotware and they can do it for you. Taking a whole website and turning it into a PDF is a feature is built right into the software.

Happy Woodworking!

Re: OT Changing Webpages to PDF Files

#13

Tiny bit more

Mark Goodall - ATL - tooljunkie

>The software has a feature where it can take a whole website, you simply give it the URL (www.whatever.com) and it generates a PDF of the whole website in one click. This is different than going to each webpage individually and printing each page to a PDF file.

Happy Woodworking!

Re: OT Changing Webpages to PDF Files

#14

Ellis Walentine

Hmm, I wonder....

Ellis Walentine

>...how big a PDF file WoodCentral would make? I don't think I'm going to try to find out. :-)

Ellis

Re: OT Changing Webpages to PDF Files

#15

Alan Young

Re: Rod and Dan....

Alan Young

>

I don't want to get into a whole rework-Alan-on-line thing (not that it wouldn't be fun�)



You'll have to get in line Rod. Take a number and wait your turn behind my wife. Bring War and Peace to pass the time..:^)



The other thing I'm getting a hint of is organization. It sounds (I could have misinterpreted it) as if you have all of your images in the same directory as all of your HTML files. NO, NO, NO. At the very least you should have an �images� subdirectory. In my case, as a website developer, my hard drive and my host site are all organized so that each client has their own subdirectory, each of which has all the HTML and CSS files in it, then each subdirectory has an �images� subdirectory unique to the client

Rod- I have been using a "Plug and Play" type of provider. I don't write any HTML. The only files I create and specifically store are the picture files.

And yes I have been a bad boy in this regard. Not only are most of them labeled as they came from the camera, they are indeed all in the same directory.



You can recover. You are generally going to have to, anyway, because even with the fix you have in mind, things are going to get worse again. Here's the obligatory woodworking reference: it's like cleaning the shop (may the gods of irony not strike me down for using a shop cleanliness simile)�it hurts, and it takes time out of the fun/routine, but you have to do it periodically or you'll be hip deep in detritus and unable to work at all. The website is no different.


Geez Rod what do you think I am? A retired Government worker with time to spare? Heck I'm an active government worker with time to spare!

Gird your loins, grit your teeth, forget the instant gratification�get in there and start organizing. You'll be the better man for it. You may even thank me, if I haven't been struck down. Buy me a bottle of water�

Rod

Thanks Nurse Rod-please pass the Cod Liver Oil......:^)

Alan

Re: OT Changing Webpages to PDF Files

#16

Maybe I will.....

Mark Goodall - ATL - tooljunkie

>...might be interesting to see.

You can specify how many levels deep it will go, as well as if it will stay within the site domain, or go elsewhere too.

I once did PDF'ed site without setting those properly and it ran for hours and linked to other websites and was simply huge :0

Happy Woodworking!