The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I wouldn't expect the people who initiated the campaign to even think of something like Q&A , and I don't expect them hiring pros to do that job thoroughly . I suspect the first one who did so much as express an ability to create a PDF got the job, and if (s)he got something like a specification, it probably was hand-knitted into a sweater, with love.
view it on your phone.
Actually, that is something I hadn't thought of, as I never check mails on my phone...
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
You'd expect this got sent to a couple of people for review
The PDF probably started out perfect. Then it got sent to 'the boss' for review.
Now, the boss being the boss has to ensure that they find a fault - otherwise they might not be a good boss anymore. So they say, "Hey, it's almost perfect, just change a few random letters to use this awesome font that I found the other day while pretending to do real work".
Of course, it won't be the boss to blame for the mistake, and will likely get raised as a reason not to give you that pay rise you ask for at your next review: "Hey, remember that time you used that stupid font and put the reputation of the whole company into disrepute..."
I thought the whole idea of PDF's was that they look the same on every computer?
I guess that is the idea. Reality may be different from the ideas
When PDF was first released, my office computer had a 40 Mbyte disk drive (my new home PC had an enormous size 200 Mbyte SCSI disk!). 5.25" floppies (720 kbytes) were still a common storage format. Font files were no smaller in those days than they are today. If you had a thousand tiny PDF documents on your disk, having a thousand copies of the stanard Times Roman font would be a terrible waste of space. (This was before people went crazy with two hundred fonts in every document, so chances were much higher that they all used Times Roman or one of the other half-dozen "standard" fonts that was available everywhere. I've got a book on typography from those days, recommending that you limit yourself to two, at most three, diffent typefaces in any document, and at most three point sizes of each typeface.)
So PDF was designed with the option to embed into the document either the complete font definition (especially for documents intended to be edited in PDF format), or only information about characters actually uses (for read-only documents) or none at all, for a font that is assumed to be universally available. This choice is made on a font-by-font basis - you can leave out the standard fonts, but embed special fonts.
Today, with multi-terabyte disks and optical fiber communication, we don't see any reason for not embedding a fifty megabyte unicode font file with a half-page PDF document. 50 meg is nothing... Even a thousand such documents is just 50 gig of font information...
Fortunately, most font files are much smaller; few are above even one megabyte. But there are still space conserving people out there - or the standard settings of the document production system was made in the time when there were space conserving people around, and none has touched the settings since.
Bottom line: You are not guaranteed that a PDF document looks identical everywhere. It might depend on fonts not embedded.
Similar story, this week; got to choose a christmaspresent, and wanted the box with food. When I logged in, that option was already gone, so I selected another one. Got an email bit later saying they were out of those also.
The order-email is in Dutch, but filled with English tags like "spacer" to indicate which cells in the table should be blanc (and thus, aren't), and "label header", "label side" tags.
With a required field for the telephone (which is not relevant to getting the gift, but may be sold to others) and an emailfield that you have to supply twice. At least they made sure that both the emailadresses should be the same
Sander Rossel wrote:
How did this ever get through QA or how did the person creating this not notice it?
QA prolly being a one-person team, called "the manager", who nods once and simply assumes that the "spacer" tags will be replaced in the final version.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
and simply assumes that the "spacer" tags will be replaced in the final version
That's how it goes though.
Everyone assumed someone else will find the bugs.
It happened to my house, seven parties (builder, government, some instances whose sole job it is to check the figures...) messed up and my house had to be broken down and built back up.
I'm just happy that they found out during the building and not when I already lived there
Yeah, the piles were too short, meaning my house sunk in the sand.
They tried to somehow make the piles longer by drilling holes underneath the house, kind of like the quick and dirty bug fix, but that plan didn't work even though it was approved by nine(!) different parties.
Ultimately, they replaced the whole team, tore down the houses, and started from scratch with piles that were three times longer than the original ones.
All of the buyers were happy with the new houses because we lost faith in the original ones.
Everyone was reimbursed for damages (having to rent longer, having to delay your wedding because these people can't live together before they marry because somehow God has a problem with that so it was all exactly planned, etc.).
I don't think the building company made any profits on these houses
You might argue that I'm missing a font or some such, but this is PDF!
Someone else might have mentioned it, brain is sluggish this week and didn't read all the replies, but if you don't embed the font in the PDF when you save it will still rely on the client's font library for custom fonts. Or if you were viewing it in a browser, there might be some security settings causing issues when loading the font from a remote server (http/https conflicts).
Sander Rossel wrote:
"Less meat □□re life"
Guessing "Less meat more life" but they could be golfers, "Less meat fore life". Or maybe they are geologists? "Less meat core life"... racing enthusiasts? "Tire life"