unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: UTF-8 characters in comments of a program
Date: Sat, 21 Oct 2023 15:49:41 +0200	[thread overview]
Message-ID: <878r7wnkzu.fsf@dataswamp.org> (raw)
In-Reply-To: ZTPP7_LmEWF8GSMl@SDF.ORG

Jonathon McKitrick via Users list for the GNU Emacs text editor wrote:

>> If you want to know whether language compilers and
>> interpreters accept UTF-8 encoded characters, then you will
>> need to consult the documentation of the relevant compiler.
>> AFAIK, C/C++ compilers support this only in recent
>> versions. For Emacs Lisp, the answer is YES, as the default
>> encoding of ELisp files is UTF-8.
>
> A few years ago I found a bug in an input form of our web
> app, and I thoroughly enjoyed writing unit tests to verify
> the fix, including the 'poo' emoji. This was in Scala, BTW.

In certain applications, notably those who deal with
communication between people, those chars sure has their
place, just like support for different human languages, not
just English, obviously should be supported.

For example when I talk about countries in my smartphone
Signal app, I like to add their flags after the country names.
It spices things up and look nice and besides everyone loves
flags, right?

But in computer-computer technology and programming not so
much so IMO. I'm sure modern programming languages that are
designed and implemented today can support them, but what is
the gain, really? Maybe I'm just old-school.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2023-10-21 13:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 22:53 UTF-8 characters in comments of a program Heime
2023-10-21  7:48 ` Eli Zaretskii
2023-10-21 10:48   ` Heime
2023-10-21 11:24     ` Eli Zaretskii
2023-10-21 11:36       ` Heime
2023-10-21 11:46         ` Eli Zaretskii
2023-10-21 11:51           ` Heime
2023-10-23 15:39             ` Leo Butler
2023-10-21 15:54       ` Basile Starynkevitch
2023-10-21 13:19   ` Jonathon McKitrick via Users list for the GNU Emacs text editor
2023-10-21 13:49     ` Emanuel Berg [this message]
2023-10-22 11:04       ` Heime
2023-10-22 11:30         ` Emanuel Berg
2023-10-22 13:44       ` Eric S Fraga
2023-10-23  5:51         ` Emanuel Berg
2023-10-21 10:25 ` Emanuel Berg

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=878r7wnkzu.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@gnu.org \
    /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).