pdf is a print and typesetting format for printers. what’s crazy is that we’re using it for something other than that.
It’s not? The p stands for portable, which implies a digital format for software use. Maybe you’re thinking of postscript?
pdf is a postscript container format, yes.
Yep, but mainly meant for computer screens rather than paper, no?
No. It is designed for print. It is used for screens (that’s the crazy part). Something like HTML or epub is designed for screens. PDF later got extended with some features, that only make sense on screen but the original design is for print and it shows. For example everything has a fixed layout size (like paper). And most of the time the order of words got lost so you can not select text in a meaningful way (something that would not matter if it is printed).
you’re thinking of display postscript? i think that was an extension of the original language.
https://en.wikipedia.org/wiki/History_of_PDF
PDF was developed to share documents, including text formatting and inline images, among computer users of disparate platforms who may not have access to mutually-compatible application software.[2]
Wait till I tell you what they’re doing with JavaScript.
actually, you’re kinda right! didn’t know this before, but pdf started as a slimmed-down version of postscript that didn’t support all print features.
Confidently incorrect.Edit: apparently I kinda was actually.
This is funny. They’re correct.
Development of PDF began in 1991, when Adobe’s co-founder John Warnock wrote a paper for a project then code-named Camelot, in which he proposed the creation of a simplified version of Adobe’s PostScript format called Interchange PostScript (IPS).[1] Unlike traditional PostScript, which was tightly focused on rendering print jobs to output devices, IPS would be optimized for displaying pages to any screen and any platform.[1]
That’s interesting indeed. I knew it was about portability, being right there in the name, but I thought it was about being as compatible everywhere (any device) as possible, then over time also became the defacto way to share a printable document, then that use case waned in popularity since the mid aughts.
History of PDF is basically: We need a standard format to get print jobs over there > Postscript > let’s add feature X > also feature y > make it do thing too! > uh oh, it’s gotten too powerful, security galore > reboot and slim it down > PDF > let’s add feature X > also feature y > …
Yes. PDF is an embrace - extended - extinguish job done on PostScript.
I feel like websites tried to do the same with seperating CSS from the DOM, but then the web said, actually how about we invent webasm anyway…
Almost as crazy as Adobe continuing to exist decades after purchasing Macromedia when it could not compete with Macromedia’s software on merit.
pocorgtfo has some pretty cool/scary examples of what a pdf is capable of hiding. One issue actually starts with a boot sector that is a playble game of tetris
that’s what happens when any file with a valid pdf header in it anywhere is a valid pdf…
Because PDF is literally that, a compressed print. it is not for editing, forms or anything it is a representation of a print.
File → Export PDF?
What? Libreoffice has had this one since always.
Try that with a JPEG
Do I look like I know hwhat a JPEG is?
I just want a picture of a got-dang hot dog
Do you pronounce that like JPEG or JPEG?
Only a moron pronounces it like JPEG.
I’d assume you have some image processing software that can create image containers, in which case it would most likely support PDF.
But yeah the question would be finding the one.
Same with Word and any of the other Office products.
Seems like a standard feature in any document managing software.
I’ve found that exporting to PDF sometimes has inconsistent results vs passing it thru the systems print dialog. Like sometimes fonts fail to render or locations/margins get messed up when “exported” since that’s the softwares built in interpreter.
Ah but can you do that on a website?
You’re not lying to your computer. A PDF is a print. It’s just on screen instead of on paper.
Not on screen, on storage usually.
Strangely, this kinda makes sense. PDF is based on PostScript, which is a file type (also by Adobe) that gets sent to printers. It’s just skipping the final “send to printer” part and sends it to a file instead.
A fascinating thing (in a scary way) is that PostScript is technically a full programming language with loops, functions, logic, and a built-in font rendering and 2D graphics engine. When a document is printed using PostScript, your computer generates a script to lay out the page, that the printer runs in order to produce the document!
PDF is essentially “the safe parts” of PostScript - the same 2D graphics engine but with all the dynamic parts removed. PDFs are statically laid out when they’re created, rather than having to run arbitrary code to lay them out like PostScript does.
PDF does support JavaScript code, but it’s rarely used and needs to be granted permission to run. It’s not a core part of the format.
For printing, PCL has somewhat taken over and it’s less scary - it just has preset commands rather than allowing arbitrary code in a full programming language. PostScript is still used today for higher-end printers and print jobs though.
You can run doom on a pdf
Ok but that’s a really low bar, you could just list on what Doom can’t run :).
Also if you print doom.pdf, does the printer run it like this
or like this
?A Bringus reference? On my Lemmy?
Oh, til.
I see some cool nerd shit tho, nice.
A fascinating thing (in a scary way) is that PostScript is technically a full programming language with loops, functions, logic, and a built-in font rendering and 2D graphics engine.
It also had a extension to create NextStep UI with it.
It wasn’t really an extension… The nextstep user interface was just written in postscript and objective-C.
This is how the nextstep UI was so smooth and sharp and so well built for design, especially output to print. And how that translated to macOS (although the graphics display subsystem and macOS is based on the more advanced PDF, not postscript). It’s also part of the entire print sub systems, and how it was always so easy to create a PDF in the manner the OP suggests. That functionality was really only added to other operating systems later with plugins.
it is at least theoretically possible to boot from a PDF.
deleted by creator
I’ve seen some pretty feature rich PDFs - before WebGIS got really good, people would often disseminate digital maps and geographic reports via GeospatialPDF which is an extension for PDF. You can do all kinds of stuff in there related to measuring distances, coordinate transformations and zoom/pan around the maps. Some of these files would end up being >500MB. Probably still used quite a lot field work I imagine.
Not just 2d, I’ve received some unholy pdfs with fully imbedded 3d models.
I forgot to mention that PDF added new features on top of PostScript, including 3D models.
Print Dat File
I would miss the little ruse tbh. Keep my computer guessing, it’s trying to know me too much lately.
i mean, yeah. turned out to be a pretty good way to make pdf conversion accessible to a lot of people and make it convenient to convert it and print it all from one spot.
Because you are using the wrong tool. Libreoffice has a dedicated export to PDF button. Other tools do too.
so do Adobe Illustrator and many CAD tools
Is OP still using winrar and notepad++?
Don’t diss Notepad++
I feel attacked.
What is the current meta for a syntax highlighting, regex capable, multi tab text editor that remembers my open files and can follow changes?Zed, over the top of my head. Gedit, gnome-text-editor. Maybe Kate too but I am unsure.
AFAIK gedit doesn’t recover your scribbles unless you save them. Not sure about the others, but I expect the same of them.
Phones are shitty for that.
Some apps can’t save to a folder on your phone.
So you have to share it with an app but the file manager doesn’t support that.
So you share it with the printing app and then you print the pdf to your phone…
I use File | Save As… in Microsoft Office to get PDFs.
To print, these days, you generate PostScript and fire that off to the printer.
PostScript -> PDF is a very light translation.
The biggest slight is not renaming print to Print/PDF and just shortcutting the same exact code.
you’re printing it to disk. this is a trick as old as time. like piping.
The entire tech stack is a tactical mess
Hey, if it works why fix?
Microslop is pretty good at “fixing” shit that isnt broken
I mean why would you build some PDF export stuff when this basic functionality is already available in most browsers.
So if a native application doesn’t support PDF exports, I should open it in a browser?
No, a native (Windows at least) application with print support also has the ability to print to PDF just like the browser does.
All modern printers save documents as a multi-paged image (read: a PDF) in their memory before printing it onto paper. It’s trivial to make the print dialog save a PDF file because you’re telling it to give the file it just made back to the computer instead of giving it to the printer.
