Anatom, we help identify problems like these by being users of a 100% free
software distro. A user of an OS that hacks around these problems by
compromising with unnecessary, externally-imposed demands for proprietary
software would never realize that the problem exists. I understand that your
#1 priority is to get your own work done, as with any person using a
computer, and nobody here will judge you for doing that (or if they do,
that's their issue, not yours).
However, OnPon is suggesting that as well as going through whatever work
around is required to get though this application, you document that
workaround, and offer this documentation to the person who supplied you with
the DRM-crippled PDF. The problem cannot possibly be fixed until there is
awareness that the problem exists. By describing the problem, in a technical,
non-judgemental way, you make sure that the people in a position to fix the
problem at least become aware of the problem.
Now, who knows, they might immediately apologise, and set to work changing
their processes so its works with only free code software. If they don't,
that's when you have to decide whether or not you want to take on a fight for
software freedom. You don't have to do that. But many tiny, soft drops of
water, hitting the same spot persistently enough, can dissolve even the
hardest stone. If they get the same feedback from enough free code software
users, they may decide to change their process. If not, when someone
eventually decides to take on the fight to get the process changed, at least
if won't be the first time the organisation has heard about the problem.
