From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Have Emacs guess the charset?
Date: Mon, 20 Aug 2001 11:34:40 +0200 [thread overview]
Message-ID: <vafsnenyszz.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m33d6njfy0.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 20 Aug 2001 10:25:43 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Daniel Pittman <daniel@rimspace.net> writes:
>
>> You could supply a list of the various far-east encodings to that, which
>> /should/ prefer those to the western encodings. Not that the function is
>> likely to do much for the western encodings anyway.
>
> But we don't know what encodings there are in the buffer.
Well, as a first step it is enough for me to be able to say: "I think
this is Chinese, what does it say?" This is better than having to ask
"Show it to me in GB -- does it make sense?"
One little problem is that I don't speak or read Chinese and both
showing it in GB and showing it in Big5 leads to apparently meaningful
Chinese characters -- just different ones. So unless you know what
characters to look for, it's not easy to say which one of the two is
right.
But on the other hand, if a human can't tell, maybe Emacs can't tell,
either. And on the third hand, Emacs might know more Chinese than I
do...
kai
--
Symbol's function definition is void: signature
next prev parent reply other threads:[~2001-08-20 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 14:01 Kai Großjohann
2001-08-19 20:41 ` Lars Magne Ingebrigtsen
2001-08-19 23:46 ` Daniel Pittman
2001-08-20 0:36 ` Lars Magne Ingebrigtsen
2001-08-20 1:26 ` Daniel Pittman
2001-08-20 6:35 ` Lars Magne Ingebrigtsen
2001-08-20 7:26 ` Daniel Pittman
2001-08-20 8:25 ` Lars Magne Ingebrigtsen
2001-08-20 9:13 ` Daniel Pittman
2001-08-20 10:02 ` Lars Magne Ingebrigtsen
2001-08-20 9:34 ` Kai Großjohann [this message]
2001-08-20 10:02 ` Lars Magne Ingebrigtsen
2001-09-01 16:32 ` Dave Love
2001-08-21 0:07 ` ShengHuo ZHU
2001-08-21 21:58 ` Lars Magne Ingebrigtsen
2001-09-01 16:32 ` Dave Love
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=vafsnenyszz.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).