From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Peter_Dyballa@Freenet.DE, 7786@debbugs.gnu.org
Subject: bug#7786: 23.2; Encoding of PostScript files
Date: Wed, 13 Oct 2021 19:43:17 +0300 [thread overview]
Message-ID: <83sfx4nae2.fsf@gnu.org> (raw)
In-Reply-To: <87o87s5225.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 13 Oct 2021 18:20:34 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Peter_Dyballa@Freenet.DE, 7786@debbugs.gnu.org
> Date: Wed, 13 Oct 2021 18:20:34 +0200
>
> > https://en.wikipedia.org/wiki/PostScript_Latin_1_Encoding
> >
> > It shows the Unicode codepoint for each character in the codepage. Or
> > what am I missing?
>
> Yes, that's what I suggested using as the source -- somebody would have
> to transcribe that into a machine readable file.
Will the below do?
# Generated from https://en.wikipedia.org/wiki/PostScript_Latin_1_Encoding
0x00-0x5F 0x0000
0x60 0x2018
0x61-0x7E 0x0061
0x90 0x0131
0x91 0x0050
0x92 0x00B4
0x93 0x02C5
0x94 0x02DC
0x95 0x02C9
0x96-0x97 0x02D8
0x98 0x00A8
0x9A 0x02DA
0x9B 0x00B8
0x9D 0x02DD
0x9E 0x02DB
0x9F 0x02C7
0xA0-0xFF 0x00A0
next prev parent reply other threads:[~2021-10-13 16:43 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 [this message]
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
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=83sfx4nae2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7786@debbugs.gnu.org \
--cc=Peter_Dyballa@Freenet.DE \
--cc=larsi@gnus.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 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).