all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "gebser@mousecar.com" <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: Re: editing a PDF [Re: emacs 30.5.0 editing epub]
Date: Mon, 20 Mar 2023 03:15:25 -0400	[thread overview]
Message-ID: <0e6c9b8a-b70f-d244-c031-68c0c58dca86@mousecar.com> (raw)
In-Reply-To: <87y1nsmgwz.fsf@web.de>

On 3/19/23 7:59 PM, Michael Heerdegen wrote:
> "gebser@mousecar.com" <gebser@mousecar.com> writes:
> 
>> How does one edit a PDF file in emacs?  When I downloaded
>> https://www.gnu.org.ua/software/direvent/manual/direvent.pdf, loaded
>> it into emacs, and tried to edit it, I could see it it and read it,
>> but I couldn't even highlight a part of the text so I could copy
>> it... nor could I make any changes to it.
> 
> I don't think you want to edit pdf in Emacs: the file contents are not
> human readable, and Emacs doesn't provide features to allow graphical
> editing like those pdf editors (at least not built in).
> 
> epub files can contain human readable parts like html, however.
> 
> What I had written:
> 
>>> I managed to copy an pdf-File into an epub Archive.  Opened the
>>> archive and opened the pdf using doc-view.  I was not able to provoke an
>>> error.  Saving worked successfully however I tried.
> 
> was only happening because I was trying around how to provoke the
> reported error.
> 
> Michael.

Yep, of course that was the paragraph I was reading too.

It is kinda weird that, with all the many things that emacs can do, it 
can't take the info from doc-view (which obviously understands all the 
pieces of a pdf-- down to its bits-- and how they all go together to 
make a document) and edit it... it's pretty much implausible to believe 
emacs *can't* do that.  But then, I've always thought reality was 
completely implausible.  :^/




  reply	other threads:[~2023-03-20  7:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 18:35 emacs 30.5.0 editing epub H.-J. Heitländer
2023-03-16  5:05 ` Michael Heerdegen
2023-03-16  6:57   ` H.-J. Heitländer
2023-03-17  0:44     ` Michael Heerdegen
2023-03-17  1:13     ` Michael Heerdegen
2023-03-19 21:23       ` editing a PDF [Re: emacs 30.5.0 editing epub] gebser
2023-03-19 23:59         ` Michael Heerdegen
2023-03-20  7:15           ` gebser [this message]
2023-03-21  0:31             ` Michael Heerdegen
2023-03-21  6:28             ` Yuri Khan
2023-03-21  6:38               ` Emanuel Berg
2023-03-22 16:32                 ` Yuri Khan
2023-03-22 18:48                   ` Bob Newell
2023-03-23  9:36                     ` Jean Louis
2023-03-23 23:00                       ` Bob Newell
2023-03-23  9:13                   ` Jean Louis
2023-03-23 10:37                   ` Michael Heerdegen
2023-03-23 20:13                     ` Emanuel Berg
2023-03-23 20:07                   ` Emanuel Berg
2023-03-21 11:51               ` Ulrich Deiters
2023-03-21 21:57                 ` gebser
2023-03-21 22:55                   ` Ulrich Deiters
2023-03-22  1:56                     ` Michael Heerdegen
2023-03-22  8:26                     ` FOSS replacement for PDF [Re: editing a PDF] gebser
2023-03-22  9:18                       ` Yuri Khan
2023-03-23  9:21                         ` Jean Louis
2023-03-23  9:49                           ` Yuri Khan
2023-03-23 10:53                             ` Gregory Heytings
2023-03-28 11:28                     ` editing a PDF [Re: emacs 30.5.0 editing epub] Michael Heerdegen
2023-03-22  7:03                   ` Jean Louis
2023-03-22 15:20                     ` gebser
2023-03-16  9:22 ` emacs 30.5.0 editing epub Stephen Berman
2023-03-16 13:16   ` H.-J. Heitländer
2023-03-16 15:23     ` Yuri Khan
2023-03-16 16:54       ` H.-J. Heitländer
2023-03-16 18:58         ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-20 21:50           ` emacs 30.5.0 editing epub - finishing remark H.-J. Heitländer

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=0e6c9b8a-b70f-d244-c031-68c0c58dca86@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.