unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: editing a PDF [Re: emacs 30.5.0 editing epub]
Date: Thu, 23 Mar 2023 21:07:13 +0100	[thread overview]
Message-ID: <87fs9vkz9q.fsf@dataswamp.org> (raw)
In-Reply-To: CAP_d_8XT-Z-FHvvPap-Ngy384GEbSi_qUcpABOwaZDzsKJODSw@mail.gmail.com

Yuri Khan wrote:

>>> You don’t normally edit executable programs, you compile
>>> them from source. In the same vein, to get a modified PDF,
>>> you find the source document from which it was produced,
>>> modify that, and re-export.
>>
>> Still, they are editable at/from the PDF level as well, for
>> example with xournal.
>
> That’s not really editing. You can scrawl over the existing
> text, you can carefully overpaint existing text with your
> own, but you cannot replace one word with a different word
> and hope the rest of the text is repositioned to accommodate
> the change.

Well, obviously it's not the same as editing the LaTeX source
and compiling the original document. Actually not only is it
"not the same", it's completely different.

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2023-03-23 20:07 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fs9vkz9q.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).