Comment by jimjimjim
8 days ago
I feel your pain. PDF applications have the same problem. The thousand page PDF spec isn't actually the spec, Acrobat is the spec.
8 days ago
I feel your pain. PDF applications have the same problem. The thousand page PDF spec isn't actually the spec, Acrobat is the spec.
Acrobat at least hasn't been relevant for over a decade outside of niche concerns (like javascript-enabled pdfs, which I have seen exactly twice in the wild... these should be illegal by the way). You can't say the same about microsoft.
This is not true IME, because PDF and PostScript are so tightly coupled. If your PDF renderer doesn't tightly align with Acrobat, it's highly likely to not print correctly, hence Acrobat __is__ the spec.
I feel the pain having had to build a browser based pdf editor with features not found anywhere else. React was hammered into working and turned out pretty good. But my god, it was quite a journey. As with all enterprise projects, this one was shelved because business changed their minds. Two years of figuring it out just wasted …
do people still use acrobat? since pds becoming prolific in browsers and word and stuff i mean
IE was used well until EOL and is still being used in some places. I have no doubt Adobe Acrobat is the same way. Likely few if any new users but old ones will keep using what they're familiar with.