From: Richmond <p1299721@protonmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Default character encoding
Date: Sun, 30 Jul 2017 17:26:52 +0100 [thread overview]
Message-ID: <86lgn5ao1f.fsf@example.com> (raw)
In-Reply-To: <861soypw6q.fsf@zoho.com>
Emanuel Berg <moasen@zoho.com> writes:
> Richmond wrote:
>
>> I think you can use C-U C-X =
>
> `C-x =' is `what-cursor-position' and with C-u
> it brings up DETAILs instead of just a short
> message in the echo area.
>
> The information with C-u is identical to what
> you get with `describe-char'.
>
>> Put the curser over a character in the
>> article whose encoding you would like to
>> know. If you are using gmane (or maybe even
>> if you are not) try it on these:
>>
>> 𐅻
>
> The Linux VT can't display it other than as
> a diamond but the encoding is utf-8-emacs.
>
>> “
>
> Displayable, utf-8-emacs.
What's the linux VT? The virtual console? I am using xfce4-terminal and
that can display it with xos4-terminus font. I think you would have to
change the font on the console to one which supported unicode.
Well I guess it told you the encoding anyway, which is what you wanted
to know.
--
~
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2017-07-30 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 17:16 Richmond
2017-07-23 17:36 ` Emanuel Berg
2017-07-23 17:52 ` Richmond
2017-07-23 18:47 ` Emanuel Berg
2017-07-24 4:44 ` Teemu Likonen
2017-07-24 15:04 ` Richmond
2017-07-24 16:50 ` Emanuel Berg
2017-07-28 16:30 ` Richmond
2017-07-30 1:09 ` Emanuel Berg
2017-07-30 16:26 ` Richmond [this message]
2017-07-30 21:37 ` Emanuel Berg
2017-07-24 11:33 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-07-24 12:23 ` Richmond
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86lgn5ao1f.fsf@example.com \
--to=p1299721@protonmail.com \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).