From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unicode and text editors
Date: Sun, 08 Dec 2024 17:54:43 +0000 [thread overview]
Message-ID: <VpTsRgeCxJL-JNeghs40Qt5cLBHbFykIIGYBA6zMT8AkgKUGc_RobIkWbXrtJnf4MVOF_oHrD4iCYJk1jS92lbFA2SjCpB_1htjcPAV0gv0=@protonmail.com> (raw)
In-Reply-To: <86frmyf83q.fsf@gnu.org>
On Monday, December 9th, 2024 at 4:32 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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
> >
> > Heime via Users list for the GNU Emacs text editor
> > help-gnu-emacs@gnu.org writes:
> >
> > > Is this becoming the norm? What about emacs?
> > >
> > > Does emacs encourage use of unicode characters (UTF-8) in code comments
> > > and documentation?
> >
> > UTF-8 represents Emacs' internal text encoding
>
>
> No, the internal encoding is different (it's a superset of UTF-8).
>
> > and also its default preference for new files.
>
>
> That is only true if the user's locale has UTF-8 as its codeset.
>
> > When visiting existing files it attempts to
> > detect the encoding, and maintain it while editing.
>
> 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.
next prev parent reply other threads:[~2024-12-08 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 13:16 Unicode and text editors Heime via Users list for the GNU Emacs text editor
2024-12-08 13:29 ` Jean Louis
2024-12-08 13:31 ` Basile Starynkevitch
2024-12-08 14:02 ` Heime via Users list for the GNU Emacs text editor
2024-12-08 15:15 ` W. Greenhouse via Users list for the GNU Emacs text editor
2024-12-08 16:32 ` Eli Zaretskii
2024-12-08 17:54 ` Heime via Users list for the GNU Emacs text editor [this message]
2024-12-08 18:44 ` Eli Zaretskii
2024-12-08 18:55 ` Heime via Users list for the GNU Emacs text editor
2024-12-08 19:07 ` Eli Zaretskii
2024-12-08 19:39 ` Heime via Users list for the GNU Emacs text editor
2024-12-08 20:43 ` Eli Zaretskii
2024-12-08 20:48 ` Heime via Users list for the GNU Emacs text editor
2024-12-09 3:24 ` Eli Zaretskii
2024-12-09 3:35 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:06 ` Stefan Monnier via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='VpTsRgeCxJL-JNeghs40Qt5cLBHbFykIIGYBA6zMT8AkgKUGc_RobIkWbXrtJnf4MVOF_oHrD4iCYJk1jS92lbFA2SjCpB_1htjcPAV0gv0=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).