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 12:25:13 +0200 [thread overview]
Message-ID: <87bkcsnugm.fsf@dataswamp.org> (raw)
In-Reply-To: ywc0Jk9Q83U1Q27DouURFR-Vx9ZV7Hxc82ytJarprIGDxdhx-2UxR08m4gNlPfMDqrteF30qoLyBCHNk0zFklR28jZy4cBzix8G_1E-iuVE=@protonmail.com
Heime wrote:
> Is it allowed to have UTF-8 characters in comments of
> a program (elisp, fortran, C, C++, latex) ?
It is sometimes allowed depending on what tools are involved
in the build process. But it is safer to stick with ASCII
which is always sufficient, especially for your examples,
which are all either old or very old by now.
Lisp 1958 List Processor/Processing. USA
Fortran 1957 Formula Translation. IBM, John Backus
C 1972 Dennis Ritchie, Bell Labs
C++ 1983 "C with classes", Bjarne Stroustrup
LaTeX 1984 typesetting for PDF. Leslie Lamport, SRI, California
Elisp 1985 Emacs Lisp
https://dataswamp.org/~incal/sth/scripts/hist
https://dataswamp.org/~incal/COMP-HIST
--
underground experts united
https://dataswamp.org/~incal
prev parent reply other threads:[~2023-10-21 10:25 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkcsnugm.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.