Talk:PDF

message: Maybe this needs to be clarified. E.g. open format? PDF-3200-2008:yes, PDF-3200-2008:no, or reference should be provided which should explain that a format can be considered open even if the maintainer requires paying for licensing usage of the spec.
In Open_format the first reference free_file_format states: "Thus, open format should refer to any format that is published for anyone to read and study but which may or may not be encumbered by patents, copyrights or other restrictions on use."
I don't think current PDF-2.0 meets the abbove requirement: "..published for anyone to read and study.."
My opinion is that current version of PDF is not an open format.  
Furthermore in the absense of a document granting royalty-free rights to implementors (e.g. like in the old spec: ISO32000-1PublicPatentLicense ), 
specific mention on whether the format is free should be made in the article.
— Preceding unsigned comment added by Wikipiuser (talk • contribs) 08:37, 4 October 2018 (UTC)
thread_title:  How is pdf considered an open format since you need to pay for the spec ? 

message: Somehow this external link 
* PDF Reference and Adobe Extensions to the PDF Specification
to be found in the external links section points to something else than the PDF reference. At the moment this page is forwarded to a documentation called DC Developer Resources, no sight of PDF reference. I am confused, since also other pages use this link as, e.g., de.wikipedia.org. Did something get broken along time?
As far as I understand PDF Reference refers to the PDF Reference Manual, i.e.,  PDF Reference, Third Edition - Adobe or is this document also deprecated.
Fabiangabel (talk) 10:41, 1 April 2021 (UTC)
thread_title:  Link to PDF Reference Manual 

message: The previous author seems to not have understood the word „tokenized”, and not read the PostScript language reference. Being a programming language, of course PS is tokenized and parsed by the interpreter too, before/during interpretation.
PDF is simply “unrolled” PS so that it is purely declarative, and packaged with its dependencies.
Professor Brailsford of Nottingham university explained this quite well in some Computerphile videos. And he knows/knew the people who developed PDF personally.
I improved the whole section. I also made it a bit more neutral; as it seems much knowledge about PS (especially about the extend of its use case, compared to PDF being just about documents) is almost lost nowadays, leading to a natural underestimation and bias from people who don’t know they don’t know enough to make that decision. I know because I thought like that too until I looked into it. (The language reference is quite nice to read.)
E.g. the fact that PS is based on Forth and Lisp (and frankly nicer than both). Or that SVG is basically the XML version of the PS in PDF. … All information that is almost lost, and would quickly get deleted by such people who don’t know they don’t know … for not being up to the standard … of confirming their beliefs that are based on sources that already lacked those forgotten details about the big picture and ideas back then.
— 109.42.178.164 (talk) 00:19, 28 December 2023 (UTC)
thread_title:  I fixed the misrepresentation of the relationship between PS and PDF.