unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: undecided vs utf-8
Date: Fri, 5 Nov 2010 13:28:29 +0100	[thread overview]
Message-ID: <AANLkTimTee_feX69bSsr_dYHRFmntQJG-1sVpR9Z6mCx@mail.gmail.com> (raw)
In-Reply-To: <83sjzg42d5.fsf@gnu.org>

2010/11/5 Eli Zaretskii <eliz@gnu.org>:
>> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
>> Date: Fri, 05 Nov 2010 03:32:02 +0100
>>
>> The use case that made me look into this -- erc -- is somewhat special.
>> The irc protocol does no charset tagging, and some clients send some
>> charsets, and some send others, which is why erc uses `undecided' as the
>> default coding system.  Typically on a channel you'll see somebody using
>> a local (iso-8859-* is popular) charset, and others using utf-8.
>
> How do other erc clients solve this problem?
>
>

rcirc uses utf-8 for both encoding and decoding by default, letting
the user override these settings for specific channels using
rcirc-coding-system-alist.

-- 
Deniz Dogan



  reply	other threads:[~2010-11-05 12:28 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 [this message]
2010-11-05 12:50       ` Lars Magne Ingebrigtsen
2010-11-05  7:56 ` 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=AANLkTimTee_feX69bSsr_dYHRFmntQJG-1sVpR9Z6mCx@mail.gmail.com \
    --to=deniz.a.m.dogan@gmail.com \
    --cc=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 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).