• anewfox@lemmy.zip
    link
    fedilink
    arrow-up
    5
    ·
    1 hour ago

    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.

  • rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    11
    ·
    7 hours ago

    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.

  • ceiphas@piefed.social
    link
    fedilink
    English
    arrow-up
    49
    arrow-down
    1
    ·
    9 hours ago

    Because PDF is literally that, a compressed print. it is not for editing, forms or anything it is a representation of a print.

  • lime!@feddit.nu
    link
    fedilink
    arrow-up
    123
    arrow-down
    8
    ·
    14 hours ago

    pdf is a print and typesetting format for printers. what’s crazy is that we’re using it for something other than that.

    • BillionaireStew@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      6 hours ago

      Almost as crazy as Adobe continuing to exist decades after purchasing Macromedia when it could not compete with Macromedia’s software on merit.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      30
      ·
      12 hours ago

      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 > …

      • tetris11@feddit.uk
        link
        fedilink
        English
        arrow-up
        9
        ·
        10 hours ago

        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…

    • Hundun@beehaw.org
      link
      fedilink
      arrow-up
      16
      arrow-down
      3
      ·
      11 hours ago

      Personally, I think in dealing with text documents, we should only respect:

      • Markdown
      • Org
      • Wikidot
      • LaTeX
      • Typst if you are a progressive zoomer

      Everything else is mental illness.

      • Laser@feddit.org
        link
        fedilink
        arrow-up
        4
        ·
        7 hours ago

        Typst if you are a progressive zoomer

        I’m a millenial (maybe even an older one but I won’t admit to that) and I just love typst.

        Markdown is just content, but as soon as you want actual layouting, you’re in for trouble; sure you can post-process in pandoc and apply the result to some template, but you’re probably creating an abomination in the process. Oh, and I hate creating slightly bigger tables there. One of your columns got larger? Better adjust all your horizontal lines (at least for grid tables), which might be a pandoc markdown only feature. Yeah, there isn’t one single markdown, but multiple flavors: https://www.glukhov.org/documentation-tools/markdown/gfm-vs-commonmark-vs-pandoc-markdown/

        LaTeX? Probably still the king of exact typesetting, but it has a lot of issues:

        • compile times are really bad (especially with something like lualatex)
        • TeX which is the foundation of LaTeX maybe isn’t how you’d design such a language today
          • this includes error messages that aren’t helpful if you didn’t study CS and typesetting
        • tables (though BIG THANKS to that brave soul who wrote tabularray, it saved my sanity in my last LaTeX project)

        Though at least nowadays, you have options for creating accessible PDFs (I’m not a big fan of the idea myself, but there are environments where that support is mandatory, e.g. government contracting)

        typst? I wrote my first bigger project in typst that did much more than I could ever do in LaTeX (generation of documentation from OpenAPI spec files) and I had way fewer issues than for LaTeX projects of lower complexity. Yeah there are still some areas that need improvement, but all in all it’s a breeze. With tinymist, writing stuff is just so nice, no waiting for your document to compile for 40 seconds, no, you get an instant preview, or a helpful error message.

        I was a bit of a LaTeX guy but I haven’t touched it since I learned typst.

        • crater2150@feddit.org
          link
          fedilink
          arrow-up
          1
          ·
          1 hour ago

          this includes error messages that aren’t helpful if you didn’t study CS and typesetting

          As someone who did study CS, read a lot about typesetting, and even created several LaTeX libraries: the error messages still aren’t helpful most of the time.

          I only used typst once and I really liked it. I’m just sad it wasn’t yet available when I still regularly had things to layout.

        • Hundun@beehaw.org
          link
          fedilink
          arrow-up
          2
          ·
          7 hours ago

          Typst is awesome, I myself maintain my CV in it. Haven’t done anything larger yet. Cool to see it’s getting more adoption!

      • I love markdown. I take all my work notes in markdown on vim and my coworkers look at me like I have 3 heads.

        I then view them in a markdown viewer and I get to interact with the checklists I made 😼

      • Hundun@beehaw.org
        link
        fedilink
        arrow-up
        13
        ·
        11 hours ago

        One could say that PDFs allow unique copy protection features, which is true. However, one mustn’t forget that copy protection is yet to deserve it’s right to exist at all.

      • AmyAye@nord.pub
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 hours ago

        I want to be able to make a document without page breaks.

        No one prints shit, I just want an endless scroll in Word Docs.

    • floquant@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      47
      arrow-down
      2
      ·
      14 hours ago

      It’s not? The p stands for portable, which implies a digital format for software use. Maybe you’re thinking of postscript?

          • mogoh@lemmy.ml
            link
            fedilink
            arrow-up
            39
            arrow-down
            4
            ·
            13 hours ago

            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).

          • lime!@feddit.nu
            link
            fedilink
            arrow-up
            6
            ·
            13 hours ago

            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.

            • Cypher@aussie.zone
              link
              fedilink
              arrow-up
              8
              ·
              8 hours ago

              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]

              https://en.wikipedia.org/wiki/History_of_PDF

              • TrickDacy@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                8 hours ago

                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.

    • Neverclear@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      9 hours ago

      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

      • lime!@feddit.nu
        link
        fedilink
        arrow-up
        3
        ·
        8 hours ago

        that’s what happens when any file with a valid pdf header in it anywhere is a valid pdf…

  • dan@upvote.au
    link
    fedilink
    arrow-up
    52
    arrow-down
    1
    ·
    edit-2
    14 hours ago

    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.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        1
        ·
        6 hours ago

        I forgot to mention that PDF added new features on top of PostScript, including 3D models.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      12 hours ago

      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.

      • cruseo@piefed.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        12 hours ago

        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.

    • Beanson@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      13 hours ago

      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.

  • dragnucs@lemmy.ml
    link
    fedilink
    arrow-up
    22
    ·
    14 hours ago

    Because you are using the wrong tool. Libreoffice has a dedicated export to PDF button. Other tools do too.

    • Johanno@feddit.org
      link
      fedilink
      arrow-up
      4
      ·
      12 hours ago

      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…