From: Maxime Devos <maximedevos@telenet.be>
To: "tomas@tuxteam.de" <tomas@tuxteam.de>
Cc: Andrew Tropin <andrew@trop.in>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: RE: [PATCH 1/3] Make string-length documentation more correct
Date: Wed, 26 Jun 2024 14:09:16 +0200 [thread overview]
Message-ID: <20240626140916.gC9F2C00G3K6y2F01C9FPu@xavier.telenet-ops.be> (raw)
In-Reply-To: <ZnwElegWMBkVmXFR@tuxteam.de>
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
>ISTR that "Unicode character" is actually synonymous the same than "Unicode
code point" -- but the common meaning of "character" is more fuzzy. Perhaps
it's wise to avoid that word when trying to be precise.
My second point was that it is to late for that, unless you intend to rename procedures like character? etc..
[-- Attachment #2: Type: text/html, Size: 1490 bytes --]
next prev parent reply other threads:[~2024-06-26 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 11:20 [PATCH 0/3] Documentation improvements Andrew Tropin
2024-06-25 11:20 ` [PATCH 1/3] Make string-length documentation more correct Andrew Tropin
2024-06-25 11:27 ` Maxime Devos
2024-06-26 11:18 ` Andrew Tropin
2024-06-26 11:46 ` Maxime Devos
2024-06-26 12:07 ` tomas
2024-06-26 12:09 ` Maxime Devos [this message]
2024-06-26 12:18 ` Jean Abou Samra
2024-06-26 12:26 ` Maxime Devos
2024-06-26 14:47 ` Damien Mattei
2024-06-28 13:42 ` Andrew Tropin
2024-06-28 13:38 ` Andrew Tropin
2024-06-25 11:20 ` [PATCH 2/3] Change make-dynamic-state mentions to current-dynamic-state Andrew Tropin
2024-06-25 11:20 ` [PATCH 3/3] Fix spelling Andrew Tropin
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240626140916.gC9F2C00G3K6y2F01C9FPu@xavier.telenet-ops.be \
--to=maximedevos@telenet.be \
--cc=andrew@trop.in \
--cc=guile-devel@gnu.org \
--cc=tomas@tuxteam.de \
/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).