Re: new coding system (was: Re: prettify symbols question)

[Alfred M. Szmidt]

   > 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 ...)