Re: git: 68df49bce28c - main - =?utf-8?Q?www/forgejo: Update 7.0.12 =E2=86=92 7.0.13 (fixes security vulnerabiliti=Q?www/forgejo: Update 7.0.12 =E2=86=92 7.0.13 (fixes security vulnerabiliti=
Date: Tue, 11 Feb 2025 16:09:19 UTC
On Mon, 10 Feb 2025 11:01:45 -0800 Yuri <yuri@FreeBSD.org> wrote: > On 2/10/25 10:16, Cy Schubert wrote: > > This makes sense as a) the inbox in older mail clients show strange > > 7-bit ASCII subject lines plus depending on one's locale commit > > logs contain various escape and other sequences that may only > > display correctly in the selected locale. i.e., > > > UNICODE/UTF has been around for decades now. > > If some mail clients are so outdated that they still don't understand > UTF8, the primary concern would be the likely lack of security fixes > in such clients. > Such clients should be deprecated immediately for this reason alone. > All modern software understands or should understand UTF8. Besides accepting that UTF-8 is here to stay and regardless of what I think about using it unnecessarily, there are already about 9000 commits containing "→" in the ports repo alone - the first ones from 2022 - and more and more tooling seems to auto-convert ASCII to UTF-8 (smileys, arrows, etc.) - so there is no point to panic about it. Like I wrote in my first response to this thread, there is already a fix for the mail hook in QA that will hopefully be deployed soon. -m -- Michael Gmelin