From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
Attila Lendvai <attila@lendvai.name>
Cc: 54893@debbugs.gnu.org
Subject: bug#54893: guix-daemon, locale, LANG, and unicode in git tag names
Date: Wed, 13 Apr 2022 12:57:07 +0200 [thread overview]
Message-ID: <7fef2514b5495e71eb8fa720a8964d938ad6a443.camel@telenet.be> (raw)
In-Reply-To: <a4af2f36b5db04876d351d4f929bc0210a70b78e.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
Liliana Marie Prikler schreef op wo 13-04-2022 om 12:40 [+0200]:
> You are first encoding a non-ASCII byte to ASCII, which has no glyph
> for "I have no idea what this is", so a question mark (#\?) is used.
> When converting from invalid ASCII to UTF-8 on the other hand, you do
> have #\� as the WTF character, so that is used instead. This is
> entirely consistent :)
Right, makes sense.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-13 10:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 19:47 bug#54893: guix-daemon, locale, LANG, and unicode in git tag names Attila Lendvai
2022-04-12 20:40 ` Maxime Devos
2022-04-13 7:51 ` Attila Lendvai
2022-04-13 8:03 ` Maxime Devos
2022-04-13 8:45 ` Attila Lendvai
2022-04-19 11:38 ` Attila Lendvai
2022-04-19 15:45 ` Maxime Devos
2022-04-19 16:07 ` Maxime Devos
2022-04-13 8:22 ` Maxime Devos
2022-04-13 10:40 ` Liliana Marie Prikler
2022-04-13 10:57 ` Maxime Devos [this message]
2022-04-13 8:29 ` Maxime Devos
2022-04-19 18:09 ` bug#54893: [PATCH] guix: git-download: Set locale to deal with Unicode in git metadata Attila Lendvai
2022-04-20 20:12 ` bug#54893: guix-daemon, locale, LANG, and unicode in git tag names Ludovic Courtès
2022-04-20 22:15 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fef2514b5495e71eb8fa720a8964d938ad6a443.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54893@debbugs.gnu.org \
--cc=attila@lendvai.name \
--cc=liliana.prikler@ist.tugraz.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).