From: Eli Zaretskii <eliz@gnu.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: new coding system (was: Re: prettify symbols question)
Date: Sat, 14 Nov 2020 18:19:46 +0200 [thread overview]
Message-ID: <83d00fvrkt.fsf@gnu.org> (raw)
In-Reply-To: <E1kdxUJ-0000NX-Bf@fencepost.gnu.org> (ams@gnu.org)
> From: "Alfred M. Szmidt" <ams@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 14 Nov 2020 10:29:15 -0500
>
> Is this the encoding on Unix systems? If so, maybe try without
> mapping characters below ASCII 128, I'm not sure this is supported in
> an ASCII-compatible encoding.
>
> I am not sure I understand. On unix #o0 maps to the MIDDLE DOT, #o1
> to DOWNWARDS ARROW, etc.
If the low codes aren't identical to ASCII, then I think
ascii-compatible should be nil, and I think the relevant example to
follow is that of EBCDIC. I'd suggest to construct a map file by
hand, using EBCDIC maps as example, and see if that works.
If it doesn't work, we might need to bring Kenichi Handa on board of
the discussion.
> As I understood it, the charmap/charset is a mapping from UCS-4
> Unicode to whatever is on the target?
Not UCS-4, but Unicode codepoints (which is the same thing in
practice, but just so we get our terminology right.)
next prev parent reply other threads:[~2020-11-14 16:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:01 prettify symbols question Alfred M. Szmidt
2020-11-12 14:59 ` Eli Zaretskii
2020-11-12 15:17 ` Alfred M. Szmidt
2020-11-12 15:38 ` Eli Zaretskii
2020-11-12 16:14 ` Eli Zaretskii
2020-11-12 20:53 ` Alfred M. Szmidt
2020-11-12 21:12 ` Basil L. Contovounesios
2020-11-12 21:25 ` Drew Adams
2020-11-13 7:44 ` Eli Zaretskii
2020-11-13 7:24 ` Eli Zaretskii
2020-11-13 10:15 ` Alfred M. Szmidt
2020-11-13 11:17 ` Alfred M. Szmidt
2020-11-13 12:22 ` Eli Zaretskii
2020-11-13 13:31 ` Alfred M. Szmidt
2020-11-13 13:47 ` Eli Zaretskii
2020-11-13 14:47 ` new coding system (was: Re: prettify symbols question) Alfred M. Szmidt
2020-11-13 14:59 ` Eli Zaretskii
2020-11-13 17:11 ` Alfred M. Szmidt
2020-11-14 14:24 ` Eli Zaretskii
2020-11-14 15:29 ` Alfred M. Szmidt
2020-11-14 16:19 ` Eli Zaretskii [this message]
2020-11-23 20:40 ` Alfred M. Szmidt
2020-11-23 20:49 ` Eli Zaretskii
2020-11-28 17:27 ` Alfred M. Szmidt
2020-11-13 17:11 ` Alfred M. Szmidt
2020-11-13 17:32 ` new coding system Andreas Schwab
2020-11-13 17:36 ` Alfred M. Szmidt
2020-11-13 8:27 ` prettify symbols question Alfred M. Szmidt
2020-11-13 8:40 ` Eli Zaretskii
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=83d00fvrkt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ams@gnu.org \
--cc=emacs-devel@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 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).