From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Alfred M. Szmidt" Newsgroups: gmane.emacs.devel Subject: Re: new coding system (was: Re: prettify symbols question) Date: Fri, 13 Nov 2020 12:11:18 -0500 Message-ID: References: <834kluzkma.fsf@gnu.org> <831rgyziu3.fsf@gnu.org> <83zh3my2ls.fsf@gnu.org> <83o8k1yb0x.fsf@gnu.org> <83y2j5wio8.fsf@gnu.org> <83sg9dweps.fsf@gnu.org> <83k0upwber.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38939"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 13 18:12:21 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdccX-000A0z-3A for ged-emacs-devel@m.gmane-mx.org; Fri, 13 Nov 2020 18:12:21 +0100 Original-Received: from localhost ([::1]:60838 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdccW-0004z8-4S for ged-emacs-devel@m.gmane-mx.org; Fri, 13 Nov 2020 12:12:20 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58116) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kdcba-00041X-9b for emacs-devel@gnu.org; Fri, 13 Nov 2020 12:11:22 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35337) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdcbZ-0001Uf-W4 for emacs-devel@gnu.org; Fri, 13 Nov 2020 12:11:22 -0500 Original-Received: from ams by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1kdcbW-00088A-3U; Fri, 13 Nov 2020 12:11:20 -0500 In-Reply-To: <83k0upwber.fsf@gnu.org> (message from Eli Zaretskii on Fri, 13 Nov 2020 16:59:08 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:259150 Archived-At: > So I've created a LISPM charmap, and a LISPM charset map based on > that. Then calling define-charset and define-coding-system, if I now > try to open a Lisp machine file in the lispm coding it seems to be > unable to handle the various characters; e.g., #o210. > > These default coding systems were tried to encode text > in the buffer ‘lispm-char-test.text’: > (lispm-unix (1 . 0) (59 . 1) (117 . 2) (175 . 3) (233 . 4) (291 . 5) > (349 . 6) (407 . 7) (465 . 4194184) (523 . 4194185) (581 . 4194186)) > However, each of them encountered characters it couldn’t encode: > .... What does "M-x describe-character-set RET lispm RET" show? It says: Character set: lispm LISPM Number of contained characters: 256 Map file: LISPM Code space: [0 255] And what was shown where you show the ellipsis? These default coding systems were tried to encode text in the buffer `lispm-char-test.text': (lispm-unix (1 . 0) (59 . 1) (117 . 2) (175 . 3) (233 . 4) (291 . 5) (349 . 6) (407 . 7) (465 . 4194184) (523 . 4194185) (581 . 4194186)) However, each of them encountered characters it couldn't encode: lispm-unix cannot encode these: ^@ ^A ^B ^C ^D ^E ^F ^G \210 \211 ... (where ^@ etc are #o0, #o1, etc and #o210 ...)