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: Wed, 13 Oct 2021 15:51:48 +0200 [thread overview]
Message-ID: <87ee8p58y3.fsf@gnus.org> (raw)
In-Reply-To: <F265AF4E-C402-4C84-9B50-9D8061FE896B@Freenet.DE> (Peter Dyballa's message of "Wed, 5 Jan 2011 01:18:19 +0100")
Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:
> This is incorrect, because, as PRML, The PostScript® Language
> Reference manual, explains in a footnote near the end, on encodings:
>
> 3. The ISOLatin1Encoding encoding vector deviates from the ISO
> 8859-1 standard in one
> respect: the character at position 140 is quoteleft,
> whereas the ISO standard specifies
> grave. A PostScript program needing to conform exactly to
> the ISO standard should
> create a modified encoding vector with this entry changed.
This seems to be incorrect.
https://en.wikipedia.org/wiki/PostScript_Latin_1_Encoding
https://en.wikipedia.org/wiki/ISO/IEC_8859-1
differ in a whole bunch of places. In addition, ISOLatin1Encoding is
not the same as stdenc (which is what adobe-standard-encoding uses):
https://unicode.org/Public/MAPPINGS/VENDORS/ADOBE/stdenc.txt
Emacs doesn't seem to have any support for ISOLatin1Encoding:
"In 1995, IBM assigned code page 1277 (CCSID 1277) to this character set."
Unless we have it under some other name.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-13 13:51 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 [this message]
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
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=87ee8p58y3.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).