From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs 21/22: french =?iso-8859-1?q?=E7?= and =?utf-8?b?xZM=?= Date: Tue, 28 Oct 2008 10:27:36 -0400 Message-ID: References: <87ljwa6zjj.fsf@mat.ucm.es> <87bpx65fjj.fsf@mat.ucm.es> <87hc6w7v9j.fsf@mat.ucm.es> <871vy0yi9a.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1225204102 15622 80.91.229.12 (28 Oct 2008 14:28:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 28 Oct 2008 14:28:22 +0000 (UTC) Cc: Uwe Brauer , emacs-devel@gnu.org To: Paul R Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 28 15:29:14 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KupZA-0006aK-1g for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 15:29:04 +0100 Original-Received: from localhost ([127.0.0.1]:49153 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KupY4-00062M-3W for ged-emacs-devel@m.gmane.org; Tue, 28 Oct 2008 10:27:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KupXq-0005xa-Ba for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:27:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KupXo-0005wq-Tx for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:27:42 -0400 Original-Received: from [199.232.76.173] (port=57672 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KupXo-0005wj-JD for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:27:40 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:14578 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KupXo-0006zQ-9G for emacs-devel@gnu.org; Tue, 28 Oct 2008 10:27:40 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhAFABO+BklMCqyo/2dsb2JhbACBdsghg0+BDQ X-IronPort-AV: E=Sophos;i="4.33,499,1220241600"; d="scan'208";a="28958159" Original-Received: from 76-10-172-168.dsl.teksavvy.com (HELO pastel.home) ([76.10.172.168]) by ironport2-out.teksavvy.com with ESMTP; 28 Oct 2008 10:27:39 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 7ED4A8E6F; Tue, 28 Oct 2008 10:27:36 -0400 (EDT) In-Reply-To: <871vy0yi9a.fsf@gmail.com> (Paul R.'s message of "Tue, 28 Oct 2008 14:13:53 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:105073 Archived-At: Uwe> I am not sure whether in french oe always should be represented Uwe> by the symbol =C5=93? > No, it is not. The word =C2=AB coefficient =C2=BB is an exemple, it just = can't > be written =C2=AB c=C5=93fficient =C2=BB. Indeed, kind of like the "ue -> =C3=BC" in German, where zuerst can't be written z=C3=BCrst, but it's really one of a fairly few exceptions. I don't know if that means that ("oe" ?=C5=93) would be desirable or annoying, tho. > For what it's worth, also, writing =C2=AB coeur =C2=BB is incorrect, it c= an only > be written =C2=AB c=C5=93ur =C2=BB. Never heard of that one, so maybe the French Academy made such a decision at some point, but it hasn't seen much use. Especially since =C5=93 didn't even make it into latin-1 and was hence "unavailable" for many years. > IOW, '=C5=93' really is a first class caracter in French and isn't > equivalent to 'oe'. The "Robert" dictionary sorts "=C5=93" as if it were "oe", so it's pretty close to equivalent. > A simple diff against the old file is ok? Or are some parameters needed > for the diff? Preferably -u (or failing that -c). > Where shall I send this "patch" Right here. Stefan