PostScript versus PDF as an output format

前端 未结 4 1678
猫巷女王i
猫巷女王i 2021-02-07 07:57

I\'m currently writing a typesetting application and I\'m using PSG as the backend for producing postscript files. I\'m now wondering whether that choice makes sense. It seems t

4条回答
  •  孤城傲影
    2021-02-07 08:40

    Avoid PDF like the plague. Adobe invented PDF and pushed PDF to the consumers to make more money from suckers who believed all the hype about PDF that Adobe told its users. PDF is a bloated format that requires a slow and non-free reader to read and process correctly. Most free readers do not support 100% of Adobe features and likely support a subset of features that is are found in Postscript. For instance reportlab does not support 100% of PDF features.

    Historical fake technical arguments to use PDF have been

    • No loops in PDF which stops helps processing, False as other formats such as XML without loops have memory and processing issues.
    • More fully feature, False argument as Postscript is more powerful and can do what PDF can do with less features.
    • Postscript has to load all of the pages as it is a language. This is of course not true as C,C++, Java and many other language can load code at runtime.
    • Postscript is missing feature X, True but mostly because of
      Adobe inventing a new format to make money not because feature X cannot be added to Postscript.

    The real reason to use PDF instead of Postscript is that PDF readers are more common than Postscript readers.

提交回复
热议问题