Yeah I think in general “export” is used for cases where you’re saving to an application’s non-native file type, whilst save as is more often for “save as a new file somewhere else”, tho I’ve seen a lot of apps allow you to use “save as” to save to a uneditable format.
The reason for PDF „export“ is it’s origin. PDF in its early days had to be “printed” or “distilled” in a separate application because the process behind the format is the same as sending your file to be printed on a printer. This step changes the (editable) human readable file into (locked) printer readable code in the form of “post script”. PDF is in short nothing but a container that wraps around a bunch of post script code and makes it human readable again.
Okay yeah that makes more sense.
“Save As” by a different name I guess.
Except maybe it was because it’s not an editable format by the application? That was always silly… Why Adobe has a near monopoly on editing PDFs.
But the real tarrifs would be on importing them…
Yeah I think in general “export” is used for cases where you’re saving to an application’s non-native file type, whilst save as is more often for “save as a new file somewhere else”, tho I’ve seen a lot of apps allow you to use “save as” to save to a uneditable format.
The reason for PDF „export“ is it’s origin. PDF in its early days had to be “printed” or “distilled” in a separate application because the process behind the format is the same as sending your file to be printed on a printer. This step changes the (editable) human readable file into (locked) printer readable code in the form of “post script”. PDF is in short nothing but a container that wraps around a bunch of post script code and makes it human readable again.
@[email protected]
That makes a lot of sense. Thanks!
Probably what Microsoft ripped off for the XPS printer lol.