Subject: Re: Re: Re: bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal

From: Juanma Barranquero <[email-masked]>
Date: Thu, 26 Jul 2012 20:29:57 +0200

On Thu, Jul 26, 2012 at 7:18 PM, Eli Zaretskii <[email-masked]> wrote:

> What are the codes of these characters, as "C-u C-x =" sees them?

á and é, as above.

As for í, ó, ú, ñ and ç, in that order:

             position: 194 of 198 (97%), column: 5
            character: ¡ (displayed as ¡) (codepoint 161, #o241, #xa1)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0xA1
               syntax: . 	which means: punctuation
             category: .:Base, h:Korean, j:Japanese, l:Latin
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #xC2 #xA1
            file code: #xC2 #xA1 (encoded by coding system nil)
              display: terminal code #xAD

Character code properties: customize what to show
  name: INVERTED EXCLAMATION MARK
  general-category: Po (Punctuation, Other)
  decomposition: (161) ('¡')

             position: 195 of 198 (98%), column: 6
            character: ¢ (displayed as ¢) (codepoint 162, #o242, #xa2)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0xA2
               syntax: _ 	which means: symbol
             category: .:Base, j:Japanese, l:Latin
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #xC2 #xA2
            file code: #xC2 #xA2 (encoded by coding system nil)
              display: terminal code #xBD

Character code properties: customize what to show
  name: CENT SIGN
  general-category: Sc (Symbol, Currency)
  decomposition: (162) ('¢')

             position: 196 of 198 (98%), column: 7
            character: £ (displayed as £) (codepoint 163, #o243, #xa3)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0xA3
               syntax: _ 	which means: symbol
             category: .:Base, j:Japanese, l:Latin
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #xC2 #xA3
            file code: #xC2 #xA3 (encoded by coding system nil)
              display: terminal code #x9C

Character code properties: customize what to show
  name: POUND SIGN
  general-category: Sc (Symbol, Currency)
  decomposition: (163) ('£')

             position: 197 of 198 (99%), column: 8
            character: ¤ (displayed as ¤) (codepoint 164, #o244, #xa4)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0xA4
               syntax: _ 	which means: symbol
             category:
		       .:Base, b:Arabic, c:Chinese, h:Korean, j:Japanese, l:Latin
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #xC2 #xA4
            file code: #xC2 #xA4 (encoded by coding system nil)
              display: terminal code #xCF

             position: 198 of 198 (99%), column: 9
            character: ‡ (displayed as ‡) (codepoint 135, #o207, #x87)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x87
               syntax: w 	which means: word
             category: l:Latin
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #xC2 #x87
            file code: #xC2 #x87 (encoded by coding system nil)
              display: not encodable for terminal

Character code properties: customize what to show
  name: <control>
  old-name: END OF SELECTED AREA
  general-category: Cc (Other, Control)
  decomposition: (135) ('‡')

> Does the above solve the problem at hand, though?  If it does, we can
> do that at startup in the -nw session.

Yes, if you evaluate that code prior to typing á, é, etc, it works as expected.

    Juanma