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 18:55:52 +0000 [thread overview]
Message-ID: <p6vv68VE9KE4Y8ML-nAfy75EPmsnsFPaRGtZglz_qmAeKRH62jOOy9XqbeinPnf0-5GkV3BhYTB2gR6QAV_YA85x5teM-wfdi5SXLgsW4W4=@protonmail.com> (raw)
In-Reply-To: <861pyif205.fsf@gnu.org>
Sent with Proton Mail secure email.
On Monday, December 9th, 2024 at 6:44 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 08 Dec 2024 17:54:43 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: help-gnu-emacs@gnu.org
> >
> > > > 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.
>
>
> I was talking about Emacs. Your original question was about other
> editors. I'm not familiar with other modern editors enough to tell
> whether you should or should not worry. In particular, I don't know
> how they recognize UTF-8, and am not sure that Emacs coding cookies
> are supported by them.
Is it reasonable to expect that UTF-* characters are recognised and supported?
What is your school of thought regarding emacs?
next prev parent reply other threads:[~2024-12-08 18:55 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
2024-12-08 18:44 ` Eli Zaretskii
2024-12-08 18:55 ` Heime via Users list for the GNU Emacs text editor [this message]
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='p6vv68VE9KE4Y8ML-nAfy75EPmsnsFPaRGtZglz_qmAeKRH62jOOy9XqbeinPnf0-5GkV3BhYTB2gR6QAV_YA85x5teM-wfdi5SXLgsW4W4=@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).