From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#16733: messed up unicode chars in package description Date: Thu, 20 Mar 2014 18:21:45 +0200 Message-ID: <838us496xy.fsf@gnu.org> References: <7tfvnn7phj.fsf@fencepost.gnu.org> <83zjkm865z.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1395332532 19252 80.91.229.3 (20 Mar 2014 16:22:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Mar 2014 16:22:12 +0000 (UTC) Cc: 16733@debbugs.gnu.org To: Juanma Barranquero Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 20 17:22:20 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WQfjW-0005cO-Uf for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Mar 2014 17:22:19 +0100 Original-Received: from localhost ([::1]:48088 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQfjW-0000NW-Gz for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Mar 2014 12:22:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42873) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQfjN-0000D9-TO for bug-gnu-emacs@gnu.org; Thu, 20 Mar 2014 12:22:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQfjG-0005ZT-Td for bug-gnu-emacs@gnu.org; Thu, 20 Mar 2014 12:22:09 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:41311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQfjG-0005ZP-Pb for bug-gnu-emacs@gnu.org; Thu, 20 Mar 2014 12:22:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WQfjG-0002VS-B9 for bug-gnu-emacs@gnu.org; Thu, 20 Mar 2014 12:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 20 Mar 2014 16:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16733 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16733-submit@debbugs.gnu.org id=B16733.13953324979592 (code B ref 16733); Thu, 20 Mar 2014 16:22:02 +0000 Original-Received: (at 16733) by debbugs.gnu.org; 20 Mar 2014 16:21:37 +0000 Original-Received: from localhost ([127.0.0.1]:42493 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WQfiq-0002Ud-GS for submit@debbugs.gnu.org; Thu, 20 Mar 2014 12:21:36 -0400 Original-Received: from mtaout26.012.net.il ([80.179.55.182]:32987) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WQfin-0002UR-MN for 16733@debbugs.gnu.org; Thu, 20 Mar 2014 12:21:34 -0400 Original-Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0N2Q00C00TAFSE00@mtaout26.012.net.il> for 16733@debbugs.gnu.org; Thu, 20 Mar 2014 18:20:43 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N2Q00BJ4TEJUS10@mtaout26.012.net.il>; Thu, 20 Mar 2014 18:20:43 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:87037 Archived-At: > From: Juanma Barranquero > Date: Thu, 20 Mar 2014 06:12:24 +0100 > Cc: Eli Zaretskii , 16733@debbugs.gnu.org > > 1) Leave it as it is now, with > detect-coding-string/decode-coding-string (or perhaps > decode-coding-(inserted-)region). This is suboptimal when the URL already tells its charset. In that case, you should use the information; you should fall back to detect-coding-string only if that information is not available.