From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: undecided vs utf-8
Date: Fri, 05 Nov 2010 09:56:58 +0200 [thread overview]
Message-ID: <83wros4305.fsf@gnu.org> (raw)
In-Reply-To: <m3d3qkpvv6.fsf@quimbies.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 04 Nov 2010 23:27:57 +0100
>
> When using erc, it decodes iso-8859-1 fine with the default `undecided'
> into encoding. However, any utf-8 strings are, sort of, just translated
> into the same coding system:
>
> (decode-coding-string "u-te-\303\246ff \303\245tte" 'undecided)
> => "u-te-æff åtte"
>
> (decode-coding-string "u-te-\303\246ff \303\245tte" 'utf-8)
> => "u-te-æff åtte"
Please show the output of "M-x mule-diag RET" on the machine where
this happens.
> Shouldn't `decode-coding-string' prefer utf-8 if it's actually
> valid?
Depending on the user's locale and preferences, this could easily
backfire, especially if the text is insufficiently long to distinguish
between the two.
Using incorrect decoder in a small fraction of cases is a fact of
life; every program out there hits this from time to time. What we
need is good defaults, and ways to customize those in specific
situations. In this case, perhaps erc should use its own defaults, if
UTF-8 is widely (or solely) used there.
prev parent reply other threads:[~2010-11-05 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 22:27 undecided vs utf-8 Lars Magne Ingebrigtsen
2010-11-04 22:40 ` Lars Magne Ingebrigtsen
2010-11-05 0:02 ` Stefan Monnier
2010-11-05 8:01 ` Eli Zaretskii
2010-11-05 2:01 ` Kenichi Handa
2010-11-05 2:32 ` Lars Magne Ingebrigtsen
2010-11-05 4:42 ` Kenichi Handa
2010-11-05 13:02 ` Lars Magne Ingebrigtsen
2010-11-05 8:09 ` Eli Zaretskii
2010-11-05 13:06 ` Lars Magne Ingebrigtsen
2010-11-05 8:10 ` Eli Zaretskii
2010-11-05 12:28 ` Deniz Dogan
2010-11-05 12:50 ` Lars Magne Ingebrigtsen
2010-11-05 7:56 ` Eli Zaretskii [this message]
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=83wros4305.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.