From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Unicode and text editors
Date: Sun, 08 Dec 2024 14:02:17 +0000 [thread overview]
Message-ID: <z9SMaPjhd1MYl-O-VeHnIoH-VhBnPrpIftjSfb4G4WfrVLNAt1S_ONyxly9qqlf5IIuXpeAxBz2-sQgeTc6dSCiM6EYSWRC1aQSCn5D1DV8=@protonmail.com> (raw)
In-Reply-To: <2427ab10a48abba2c811bcb01f4e74ce3832794f.camel@starynkevitch.net>
Sent with Proton Mail secure email.
On Monday, December 9th, 2024 at 1:31 AM, Basile Starynkevitch <basile@starynkevitch.net> wrote:
> On Sun, 2024-12-08 at 13:16 +0000, Heime via Users list for the GNU
> Emacs text editor wrote:
>
> > I am using unicode characters in emacs. What happens when people
> > load the
> > file in a different text editor? Will the characters be illegible?
>
>
>
> I guess you mean Unicode characters with UTF-8 encoding.
Correct
> I will refer
> to the people mentioned in your question as colleagues (but they could
> be friends or customers or students or authorities or managers). Your
> computer means the computer you are using (probably under Linux) for
> GNU emacs. Their computer or the other computer is the one used by the
> collague.
>
> I see several possible issues.
>
> The other computer don't have the required font to display some
> character (like a cyrillic letter, or § ....)
>
> The other computer (or your colleague) don't know that the file is UTF-
> 8 encoded.
>
> The other computer don't have any editor.
>
> the other computer has an editor which does not understand UTF-8
> encoding.
>
> The other computer has an editor requiring UTF-16 encoding.
Is this becoming the norm? What about emacs?
Does emacs encourage use of unicode characters (UTF-8) in code comments
and documentation?
> The file has been corrupted during transmission.
>
> Regards
>
> NB my open source project is
> https://github.com/RefPerSys/RefPerSys (GPLv3+ inference engine)
>
> --
> Basile STARYNKEVITCH basile@starynkevitch.net
>
> 8 rue de la Faïencerie
> 92340 Bourg-la-Reine, France
> http://starynkevitch.net/Basile & https://github.com/bstarynk
next prev parent reply other threads:[~2024-12-08 14:02 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 [this message]
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
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='z9SMaPjhd1MYl-O-VeHnIoH-VhBnPrpIftjSfb4G4WfrVLNAt1S_ONyxly9qqlf5IIuXpeAxBz2-sQgeTc6dSCiM6EYSWRC1aQSCn5D1DV8=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=basile@starynkevitch.net \
--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).