From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Encoding of etc/HELLO Date: Sat, 19 May 2018 21:39:42 +0300 Message-ID: <83h8n3h4lt.fsf@gnu.org> References: <83sh7qxb5j.fsf@gnu.org> <87po2t6gdm.fsf@gmx.de> <83muxxyijl.fsf@gnu.org> <83lgdhyeqv.fsf@gnu.org> <83k1t1xcjp.fsf@gnu.org> <87fu3owqqa.fsf@md5i.com> <83k1rzhdoo.fsf@gnu.org> <69662556-2fb0-356f-dad8-5b94d6833ce5@cs.ucla.edu> <83in7jh6ab.fsf@gnu.org> <013a179a-660a-f436-d9d4-af3466f8ff03@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1526755074 5917 195.159.176.226 (19 May 2018 18:37:54 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 19 May 2018 18:37:54 +0000 (UTC) Cc: mwd@md5i.com, handa@gnu.org, michael.albinus@gmx.de, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 19 20:37:50 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 1fK6jh-0001ME-7q for ged-emacs-devel@m.gmane.org; Sat, 19 May 2018 20:37:45 +0200 Original-Received: from localhost ([::1]:44001 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fK6lo-00049E-1n for ged-emacs-devel@m.gmane.org; Sat, 19 May 2018 14:39:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35613) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fK6lh-00048I-BL for emacs-devel@gnu.org; Sat, 19 May 2018 14:39:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fK6lg-0001on-Gm for emacs-devel@gnu.org; Sat, 19 May 2018 14:39:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48853) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fK6lb-0001jh-Pa; Sat, 19 May 2018 14:39:43 -0400 Original-Received: from [176.228.60.248] (port=3093 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fK6lb-0000v0-6l; Sat, 19 May 2018 14:39:43 -0400 In-reply-to: <013a179a-660a-f436-d9d4-af3466f8ff03@cs.ucla.edu> (message from Paul Eggert on Sat, 19 May 2018 11:23:01 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:225451 Archived-At: > Cc: mwd@md5i.com, michael.albinus@gmx.de, handa@gnu.org, emacs-devel@gnu.org > From: Paul Eggert > Date: Sat, 19 May 2018 11:23:01 -0700 > > Eli Zaretskii wrote: > > > What do you mean by "unified" here? > > What I meant was that, as far as I know, in Emacs this font selection currently > does not depend on whether the charset is latin-iso8859-1 or latin-iso8859-3, > because in UTF-8 text those two charsets are always displayed the same way that > text sans charsets is displayed. The codepoints are unified, of course, but that's not the whole story as far as font selection goes. See the documentation of set-fontset-font, where it says that you can define a certain font to be used for a specific charset: the charset information comes from the text property. > And given the way the world has moved, it's hard to imagine any > future version of Emacs caring whether the charset is > latin-iso8859-1 or latin-iso8859-3 in UTF-8 text. Emacs doesn't care, but users might. I agree that it is unlikely in European cultures, but it isn't impossible. And what do we lose by leaving the information in the file? > > The 'charset' property just tells Emacs to which "culture", so-called, > > or, if you want, to which language the greeting belongs > > RFC 1896 specifies the 'lang' command to specify languages. Shouldn't etc/HELLO > do that instead of using 'charset'? That would seem to match the intent of > text/enriched better. We need to have the corresponding property in Emacs first, and we need to have infrastructure for letting 'lang' affect what we want it to affect, at least font selection. Only after that we can implement this in enriched.el. I stuck with 'charset' because all the necessary infrastructure is already in place. Yes, 'charset' is ISO-2022 legacy, but it doesn't mean it's necessarily useless in modern Emacs.