From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Unicode and text editors Date: Sun, 08 Dec 2024 17:54:43 +0000 Message-ID: References: <2427ab10a48abba2c811bcb01f4e74ce3832794f.camel@starynkevitch.net> <86frmyf83q.fsf@gnu.org> Reply-To: Heime Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="610"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun Dec 08 18:55:23 2024 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tKLV4-000AYi-5C for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 08 Dec 2024 18:55:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tKLUc-0005In-S0; Sun, 08 Dec 2024 12:54:54 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tKLUa-0005Ic-Sk for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 12:54:53 -0500 Original-Received: from mail-106102.protonmail.ch ([79.135.106.102]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tKLUZ-0001Sg-6X for help-gnu-emacs@gnu.org; Sun, 08 Dec 2024 12:54:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1733680488; x=1733939688; bh=GGfKMrInWb2XyFhqpUauzY4rZcnsqtA1+dvThwsKfvA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=IO1/1IBtPKhwlVS3aKXSZObDkHS8q688vEf0y94yggl9mT7jRCOBK+Zi7X9jW0Veg /7oVXfTt9UaNvgrJ96TVvJOhLvEUw/aJE7zoxiKs6Auk2UfC3eGJt2h8eDm29OvYWL v5vzam5gHJzuPqHlWof/WTQLWYPXfJq5bVJn1FkOjEoMDjuh/T6GccJb4GCNOs5udE RNdcPosKXIsRjVsHOzl2viDDKpoq0CY8L//fkfbZFeqD2Cg9FDPd1tR27cBAb7eDBl g4euwuQrbgl0UtgLNp4P+iLwPi8e+1YKZW9aruMbb9GCfPfg8JEy+CDx1RO4wCVrKj eIeVZw8lsi2HQ== In-Reply-To: <86frmyf83q.fsf@gnu.org> Feedback-ID: 57735886:user:proton X-Pm-Message-ID: 1354ae8910b4fff092c9e1ebe73cbce02c690d23 Received-SPF: pass client-ip=79.135.106.102; envelope-from=heimeborgia@protonmail.com; helo=mail-106102.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:148700 Archived-At: On Monday, December 9th, 2024 at 4:32 AM, Eli Zaretskii wrot= e: > > Date: Sun, 08 Dec 2024 15:15:31 +0000 > > From: "W. Greenhouse" via Users list for the GNU Emacs text editor help= -gnu-emacs@gnu.org > >=20 > > Heime via Users list for the GNU Emacs text editor > > help-gnu-emacs@gnu.org writes: > >=20 > > > Is this becoming the norm? What about emacs? > > >=20 > > > Does emacs encourage use of unicode characters (UTF-8) in code commen= ts > > > and documentation? > >=20 > > UTF-8 represents Emacs' internal text encoding >=20 >=20 > No, the internal encoding is different (it's a superset of UTF-8). >=20 > > and also its default preference for new files. >=20 >=20 > That is only true if the user's locale has UTF-8 as its codeset. >=20 > > When visiting existing files it attempts to > > detect the encoding, and maintain it while editing. >=20 > That is correct. Does this mean that we should not worry when we use UTF-8? Would UTF-* be supported, and detected. With the appropriate symbols showing as they should.