From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Encoding of etc/HELLO Date: Fri, 20 Apr 2018 16:42:02 -0400 Message-ID: References: <83sh7qxb5j.fsf@gnu.org> <87po2t6gdm.fsf@gmx.de> <83muxxyijl.fsf@gnu.org> <83lgdhyeqv.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1524256818 27361 195.159.176.226 (20 Apr 2018 20:40:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Apr 2018 20:40:18 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 20 22:40:14 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f9cpI-0006zU-Oh for ged-emacs-devel@m.gmane.org; Fri, 20 Apr 2018 22:40:12 +0200 Original-Received: from localhost ([::1]:60388 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9crN-0005TF-Qk for ged-emacs-devel@m.gmane.org; Fri, 20 Apr 2018 16:42:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9crE-0005S5-Do for emacs-devel@gnu.org; Fri, 20 Apr 2018 16:42:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f9cr7-0008DH-Kc for emacs-devel@gnu.org; Fri, 20 Apr 2018 16:42:12 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:42774) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9cr7-0008C5-FG; Fri, 20 Apr 2018 16:42:05 -0400 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w3KKg34Q029890; Fri, 20 Apr 2018 16:42:03 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id F12BB6A25A; Fri, 20 Apr 2018 16:42:02 -0400 (EDT) In-Reply-To: <83lgdhyeqv.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Apr 2018 20:22:32 +0300") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6269=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6269> : inlines <6578> : streams <1784605> : uri <2628852> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:224749 Archived-At: > Unicode has language tag characters, but they are deprecated and their > use is discouraged. > > In any case, I don't think Unicode features are relevant here, because > we already have char-script-table, which is all you can do with a > unified codepoint space. Yes, I understand this part of the situation. > The whole point of ISO-2022 is that the same Unicode codepoints can > come from different ISO-2022 charsets, and the ISO-2022 encoding keeps > that information in the bytestream. My question was meant to see if there's a way to encode a similar kind of charset info into the bytestream. From what you say above, there is such a thing but its use is discouraged. Clearly this problem is not specific to Emacs, so what do people do? Hold on to iso-2022 for as long as they can (like we do in Emacs)? Give up on these "details" of rendering for files using a mix of C, J, and K? Rely on higher-level info (XML tags and friends) to carry the charset info? Stefan