unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: UTF-8 characters in comments of a program
Date: Sat, 21 Oct 2023 10:48:10 +0000	[thread overview]
Message-ID: <GlBgRtEKvLziOzruz5OuFlcSRzfiN4YVXNlbSW-JdwEBN5y_rPlB8yW3Ky-omwUu2tUMKmuOTLP6vUwD4dXUr-yobkxFE2dUtUNu8NSYyCk=@protonmail.com> (raw)
In-Reply-To: <837cngs9fo.fsf@gnu.org>



------- Original Message -------
On Saturday, October 21st, 2023 at 7:48 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > Date: Fri, 20 Oct 2023 22:53:38 +0000
> > From: Heime heimeborgia@protonmail.com
> > 
> > Is it allowed to have UTF-8 characters in comments of a program (elisp, fortran, C, C++, latex) ?
> 
> 
> There's no such thing as "UTF-8 characters". UTF-8 is an encoding of
> Unicode character set.
> 
> 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. 

Would you know if there is support for languages in Gnu GCC ?

> For Emacs Lisp, the answer is YES, as the default encoding of ELisp files is UTF-8.

My difficulty is how am I going to introduce them to an elisp source file.




  reply	other threads:[~2023-10-21 10:48 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 [this message]
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
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='GlBgRtEKvLziOzruz5OuFlcSRzfiN4YVXNlbSW-JdwEBN5y_rPlB8yW3Ky-omwUu2tUMKmuOTLP6vUwD4dXUr-yobkxFE2dUtUNu8NSYyCk=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=eliz@gnu.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).