unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 7786@debbugs.gnu.org
Subject: bug#7786: 23.2; Encoding of PostScript files
Date: Mon, 18 Oct 2021 09:09:28 +0200	[thread overview]
Message-ID: <8735oyollj.fsf@gnus.org> (raw)
In-Reply-To: <4E68EB60-E30F-4FA8-857A-A9D7BA09BD61@Freenet.DE> (Peter Dyballa's message of "Fri, 15 Oct 2021 17:59:48 +0200")

Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> You could use any text file and convert it into PostScript. It should
> not matter whether you use a2ps or enscript or something else.

Well, the problem is that I can't find anything that actually generates
codes that match the Wikipedia listing.

With a text file like this:

This is a sentence with `foo'.

a2ps gives me

(This is a sentence with `foo'.) p n

Note that the ` is 0x60, not 0x2018, like Wikipedia says it should be.

Perhaps the reason no software out there actually supports this encoding
is that it's not actually used in nature.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-10-18  7:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  0:18 bug#7786: 23.2; Encoding of PostScript files Peter Dyballa
2021-01-20 18:02 ` Lars Ingebrigtsen
2021-06-02  8:39 ` Lars Ingebrigtsen
2021-06-02 16:37   ` Peter Dyballa
2021-10-13 12:49   ` Lars Ingebrigtsen
2021-10-13 13:12     ` Lars Ingebrigtsen
2021-10-13 13:51 ` Lars Ingebrigtsen
2021-10-13 15:41   ` Eli Zaretskii
2021-10-13 16:05     ` Lars Ingebrigtsen
2021-10-13 16:18       ` Eli Zaretskii
2021-10-13 16:20         ` Lars Ingebrigtsen
2021-10-13 16:23           ` Peter Dyballa
2021-10-13 16:28             ` Lars Ingebrigtsen
2021-10-13 16:43               ` Peter Dyballa
2021-10-13 16:45             ` Eli Zaretskii
2021-10-13 17:35               ` Peter Dyballa
2021-10-13 16:43           ` Eli Zaretskii
2021-10-13 18:55             ` Lars Ingebrigtsen
2021-10-13 19:05               ` Eli Zaretskii
2021-10-13 19:07               ` Peter Dyballa
2021-10-13 21:02   ` Peter Dyballa
2021-10-14  6:42     ` Eli Zaretskii
2021-10-15 12:47       ` Lars Ingebrigtsen
2021-10-15 15:59         ` Peter Dyballa
2021-10-18  7:09           ` Lars Ingebrigtsen [this message]
2021-10-18 12:25             ` Eli Zaretskii
2021-10-18 13:17               ` Lars Ingebrigtsen
2021-10-18 15:51               ` Peter Dyballa
2021-10-18 16:00                 ` Eli Zaretskii
2021-10-19  5:49                   ` Peter Dyballa
2021-10-19 11:59                     ` Eli Zaretskii
2021-10-19 13:47                       ` Lars Ingebrigtsen
2021-10-20  5:39                         ` Peter Dyballa
2021-10-20  5:45                           ` Lars Ingebrigtsen
2021-10-20  6:18                             ` Lars Ingebrigtsen
2021-10-20 16:34                             ` Peter Dyballa
2021-10-13 21:55   ` Peter Dyballa

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=8735oyollj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=7786@debbugs.gnu.org \
    --cc=Peter_Dyballa@Freenet.DE \
    /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 public inbox

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

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).