The pdf-as-website is self-correcting; the hit count would plummet. Which, if yours is the company hired for web design etc, is a problem, but is easy enough to explain the general concept: this is not friendly tech; nobody will visit your site if you insist on it. If you want to know why it's not friendly tech, we have to teach you something about programs, documents, and how the internet works; how much time do you have? Of course, doing that in a way that doesn't let the customer know exactly what you think of his level of technical expertise can be problematic.
***
I work in in a department of about 12 people total, including the night crew. Some of them are national e-discovery data managers. I firmly believe I'm the only one who knows what "ftp" stands for, and why googledocs is not "an ftp site" ("that those bastards in IT won't let us use for some stupid security reason.")
It's okay though, the salesguy who gave out the FTP info assured us that this was a really good client who wouldn't even look at the other folders. And besides, this was the only case we had this week, so what difference does it make? (I did pester our people into changing the password later that day.)
***
We have a client who has a blog that they want converted to PDFs to file somewhere. Only, they don't want us to "print to PDF," because, as you might expect, that does wonky things with the layout. They need PDFs that look EXACTLY like the blog. (Or they think they do; I have my doubts, but I am not paid to decide what they need.) So they want screencaps as PDFs. Only, screencaps are too long; they're impossible to print or even really look at. Also, they don't want the comments, just the original blog posts. And the side-link stuff that's on every blog page. And they want the screencaps separated into page-size pieces.
So I screencap the blog posts, photoshop out the comments (and shorten the page down to the end of the actual blog post), chop into three pages (because with the links-and-such on the side, that's how long it is), save those .pngs, insert into Word so they've got margins, and print to PDF.
I am fervently praying they never ask for OCRd versions of the 96 dpi colored-text screencaps.
no subject
***
I work in in a department of about 12 people total, including the night crew. Some of them are national e-discovery data managers. I firmly believe I'm the only one who knows what "ftp" stands for, and why googledocs is not "an ftp site" ("that those bastards in IT won't let us use for some stupid security reason.")
It's okay though, the salesguy who gave out the FTP info assured us that this was a really good client who wouldn't even look at the other folders. And besides, this was the only case we had this week, so what difference does it make? (I did pester our people into changing the password later that day.)
***
We have a client who has a blog that they want converted to PDFs to file somewhere. Only, they don't want us to "print to PDF," because, as you might expect, that does wonky things with the layout. They need PDFs that look EXACTLY like the blog. (Or they think they do; I have my doubts, but I am not paid to decide what they need.) So they want screencaps as PDFs. Only, screencaps are too long; they're impossible to print or even really look at. Also, they don't want the comments, just the original blog posts. And the side-link stuff that's on every blog page. And they want the screencaps separated into page-size pieces.
So I screencap the blog posts, photoshop out the comments (and shorten the page down to the end of the actual blog post), chop into three pages (because with the links-and-such on the side, that's how long it is), save those .pngs, insert into Word so they've got margins, and print to PDF.
I am fervently praying they never ask for OCRd versions of the 96 dpi colored-text screencaps.