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=
- Reply: Michael Gmelin : "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="
- In reply to: Cy Schubert : "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="
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 10 Feb 2025 19:01:45 UTC
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. Yuri