From: Leonard Rosenthol <leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: remove DRM
Date: Tue, 16 May 2023 07:05:13 -0400 [thread overview]
Message-ID: <CALu=v3+1LOQbZFfV4zW3jD0R1OTmpmrzrQ7gJMsGUZ6Lr1MS-g@mail.gmail.com> (raw)
In-Reply-To: <4b2ac7e9-8656-4d21-b9c8-59808739fa54n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
Removing the DRM would be breaking the law in most countries - probably
not something you want to be advertising your desire to do on a public
mailing list.
Leonard
On May 16, 2023 at 7:00:58 AM, Rich Cook <richthewriterguy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I have a PDF with DRM (purchased) so I can only read it in Adobe Digital
> Editions. I'd like to remove the DRM so I can read it in a useful PDF
> reader (Xodo, to be exact).
>
> I searched but am not finding a way to do this with Pandoc other than (as
> yet untried) convert it to epub then back to DRM-free PDF.
>
> Am I overlooking something or has someone tried this already? Any other
> tips?
>
> Thanks,
> Rich
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/4b2ac7e9-8656-4d21-b9c8-59808739fa54n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/4b2ac7e9-8656-4d21-b9c8-59808739fa54n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALu%3Dv3%2B1LOQbZFfV4zW3jD0R1OTmpmrzrQ7gJMsGUZ6Lr1MS-g%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2586 bytes --]
next prev parent reply other threads:[~2023-05-16 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 11:00 Rich Cook
[not found] ` <4b2ac7e9-8656-4d21-b9c8-59808739fa54n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-16 11:02 ` Sukil Etxenike arizaleta
[not found] ` <4120942c-9419-3a39-3dc2-c05a681948f3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-16 12:07 ` Rich Cook
2023-05-16 11:05 ` Leonard Rosenthol [this message]
[not found] ` <CALu=v3+1LOQbZFfV4zW3jD0R1OTmpmrzrQ7gJMsGUZ6Lr1MS-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-16 12:07 ` Rich Cook
[not found] ` <646371e9.050a0220.c7b5.0786-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2023-05-16 13:19 ` Daniel Staal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALu=v3+1LOQbZFfV4zW3jD0R1OTmpmrzrQ7gJMsGUZ6Lr1MS-g@mail.gmail.com' \
--to=leonardr-bm6h3k5um15l57midrcfdg@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).