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, 20 Oct 2021 08:18:47 +0200 [thread overview]
Message-ID: <87bl3k9q2g.fsf@gnus.org> (raw)
In-Reply-To: <87fssw9rlk.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 20 Oct 2021 07:45:43 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> None of the .ps files we've found have been in ISOLatin1Encoding, so I'm
> not sure I understand what you mean?
Er. My analysis of these .ps files is wrong -- ` is indeed interpreted
as quoteright instead of grave.
/ISO-8859-1Encoding [
[...]
/space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quoteright
Which is what this bug report was originally about. However, none of
them adhere to the encoding found on the Wikipedia page (which claims to
document ISOLatin1Encoding) in the 0x9x area:
/x /y /z /braceleft /bar /braceright /asciitilde /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
/space /exclamdown /cent /sterling /currency /yen /brokenbar /section
Like iso-8859-1, the 0x9x area is blank instead of having dotless i and
all the diacritics.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-20 6:18 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
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 [this message]
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=87bl3k9q2g.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).