all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Deiters <ulrich.deiters@uni-koeln.de>
To: help-gnu-emacs@gnu.org
Subject: Re: editing a PDF [Re: emacs 30.5.0 editing epub]
Date: Tue, 21 Mar 2023 23:55:48 +0100	[thread overview]
Message-ID: <57456f0e-5e5e-42d3-6e33-2cdd10d974c5@uni-koeln.de> (raw)
In-Reply-To: <31dffcc9-bda2-b340-a09c-fe3d3a1b3a40@mousecar.com>

Am 21.03.23 um 22:57 schrieb gebser@mousecar.com:
> Better than that, what FOSS app(s) would be happy replacement for the 
> Acrobat-Industrial Complex?

This depends on what you want. Printing a document takes
(at least) three stages:

(1) One composes the text using a language that contains formatting
commands. The best open-source choice is LaTeX. LaTeX code is human-
readable and can be edited with emacs; in fact, emacs has a LaTeX
mode. There are also free programs that assist writing LaTeX code,
or which let one compose XML code, which is then translated into LaTeX.

(2) One processes the LaTeX code; the results are DVI, PostScript,
or PDF files. Such files basically consist of instructions of the
type "choose font F, go to location (X, Y), and print character C". 
Therefore these files are long and, if converted to a human-readable
format, very boring. You do not want to edit these.

(3) The intermediate code is processed to produce a bitmap, which is
then transferred to the paper.

So you see, the stage at which editing makes sense is Stage (1).

Exceptions are graphics designers and artists, who work with PostScript
or similar languages directly in order to achieve special effects.




  reply	other threads:[~2023-03-21 22:55 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
2023-03-21 11:51               ` Ulrich Deiters
2023-03-21 21:57                 ` gebser
2023-03-21 22:55                   ` Ulrich Deiters [this message]
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=57456f0e-5e5e-42d3-6e33-2cdd10d974c5@uni-koeln.de \
    --to=ulrich.deiters@uni-koeln.de \
    --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.