Marc Haber, on 2024-12-03: > On Tue, Dec 03, 2024 at 08:41:06PM +0100, Étienne Mollier wrote: > > The problem is not the name, but the character set, so perhaps > > --allow-bad-characters will be better perceived. If you want to > > also avoid "bad", maybe try --allow-ambiguous-characters, or > > --allow-extended-character-set? The last one is perhaps a bit > > long winded, but also sounds more accurate than the rest. What > > do you think of these approaches? > > Extended sounds good, maybe even "unicode"? or "international"?
I avoided unicode as it would include ascii and the safe subset documented by posix, and I also considered the unlikely case where something were to replace unicode. "international" would make the name technology agnostic, but there is still the case about also covering the posix-safe subset… Borrowing the idea from the other branch of the thread, --allow-unsafe-characters sounds fine and would carry the idea that certain characters could cause issues, if used in a login name. Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `- on air: Atlas - Hemifran
signature.asc
Description: PGP signature
