From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 12082@debbugs.gnu.org
Subject: bug#12082: 24.1.50; Wrong character showed by "C-h c"
Date: Mon, 30 Jul 2012 11:17:06 +0200 [thread overview]
Message-ID: <CAH8Pv0jet1oS50u6srAs6=ssw_acxgMyMUccJ1Qf-rwPT1kaZQ@mail.gmail.com> (raw)
In-Reply-To: <834nophqbw.fsf@gnu.org>
> Interesting. How did you two type M-ç?
In the spanish keyboard (the one I have) there is a key for each of
those two characters ("M" and "ç"), so M-ç is simply hold down the "M"
(alt) key and then press the "ç" key.
> And what are your values of
> keyboard and terminal coding-systems, and also what does
> w32-get-console-codepage return?
In a GUI session of my trunk build (started with -Q):
(keyboard-coding-system) => iso-latin-1-unix
(terminal-coding-system) => cp1252
(w32-get-console-codepage) => 850
> And Dani, if you go to the *Messages* buffer and type "C-u C-x =" with
> the cursor on the ‡ character, what does Emacs say?
It says this:
position: 78 of 91 (85%), column: 2
character: ‡ (displayed as ‡) (codepoint 8225, #o20041, #x2021)
preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x2021
syntax: _ which means: symbol
category: .:Base, h:Korean, j:Japanese
to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
buffer code: #xE2 #x80 #xA1
file code: not encodable by coding system iso-latin-1-dos
display: by this font (glyph code)
uniscribe:-outline-Courier
New-normal-normal-normal-mono-13-*-*-*-c-*-iso10646-1 (#xC1)
Character code properties: customize what to show
name: DOUBLE DAGGER
general-category: Po (Punctuation, Other)
decomposition: (8225) ('‡')
--
Dani Moncayo
next prev parent reply other threads:[~2012-07-30 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 17:50 bug#12082: 24.1.50; Wrong character showed by "C-h c" Dani Moncayo
2012-07-29 18:31 ` Eli Zaretskii
2012-07-29 21:44 ` Dani Moncayo
2012-07-29 23:04 ` Juanma Barranquero
2012-07-30 3:37 ` Eli Zaretskii
2012-07-30 9:17 ` Dani Moncayo [this message]
[not found] ` <CAAeL0SS+PoA8X_FY6DWO1bqEn9NJJNm23Dn=5mdXZxAcKmVmYQ@mail.gmail.com>
2012-07-30 14:32 ` Eli Zaretskii
2012-07-30 14:49 ` Juanma Barranquero
2012-07-30 14:53 ` Dani Moncayo
2012-07-30 14:56 ` Juanma Barranquero
2012-07-30 15:05 ` Dani Moncayo
2012-07-30 15:58 ` Eli Zaretskii
2012-07-30 16:16 ` Dani Moncayo
2012-07-30 16:43 ` Eli Zaretskii
2012-07-30 17:16 ` Eli Zaretskii
2012-07-30 17:47 ` Dani Moncayo
2012-07-30 18:11 ` Eli Zaretskii
[not found] ` <CAH8Pv0jk4Wv1WGFwtvmh0G76dTH6ae9kzPfmSb4Hgtyo4ry2GQ@mail.gmail.com>
2012-07-30 18:18 ` Dani Moncayo
2012-07-30 19:12 ` Eli Zaretskii
2012-07-30 14:22 ` Dani Moncayo
2012-07-30 14:32 ` Juanma Barranquero
2012-07-30 14:37 ` 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='CAH8Pv0jet1oS50u6srAs6=ssw_acxgMyMUccJ1Qf-rwPT1kaZQ@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=12082@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
/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).