Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: More problems with lcc-win Date: Fri, 17 Mar 2017 17:01:44 -0700 Organization: None to speak of Lines: 60 Message-ID: References: <20d9275b-7502-4ad0-b343-5cecf8c6ea90@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="953e254308ea5d79b385d87825e2e8df"; logging-data="15061"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19e6Dl41lTt93N9nIcQnuQg" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:VbfaBX2i+eV4t9wGDCHJWos9r3E= sha1:Vtzz7fYbzPx5SSlU92ukbrmjmkk= Xref: csiph.com comp.lang.c:106414 jacobnavia writes: > Le 18/03/2017 à 00:23, jacobnavia a écrit : >> Look I am sending you the message from >> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) >> Gecko/20100101 Thunderbird/45.8.0 >> >> Why should I use a windows charset? >> >> Because Thunderbird defaults in the news server to encoding in >> "Occidental". You have along list of languages (arab, chines whatever) >> and then "Occidental", what was the default. >> >> And look what? >> >> "Occidental" means in thunderbird "windows"!!! >> >> Mystery solved. I changed the encoding to UTF8, and maybe it will be >> better. >> > > No that was the wrong explanation. I have other message sent here > using utf8. Apparently, when I answer in a thread where somebody used > windows charset, thunderbird will default to the charset I am replying > to. > > Looking at this thread I noticed that Richard Heathfield has this header: > Content-Type: text/plain; charset=windows-1252; format=flowed > > Then thunderbird passes into windows charset, so you should explain > this stuff to Richard... Your message that I'm currently replying to uses UTF-8. Some other messages used windows-1252. Maybe it's inherited from earlier messages somehow? Yes, I've noticed that (at least some of) Richard's messages also use windows-1252. It hasn't caused an issue for me because his messages tend not to have non-ASCII accented letters, and yours, quite understandably, do. (The problem is that Gnus complains when I post a followup that contains non-ASCII characters -- but it doesn't seem to happen consistently. In fact I think I've seen it happen and not happen when posting followups to the same article. Weird.) Is it possible that your message actually had charset=windows-1252 when it left your newsreader, even though it appeared on your end to have charset=utf-8? It has charset=windows-1252 when I read it on aioe.org. (In my newsreader that header isn't generated until I post.) If I run into the problem again, there's a Gnus configuration setting I can try. I'll report if it works. If not, there's probably no need to take up more bandwidth with this. Thanks. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"