Hi Stefan, On 2/17/23 15:05, Stefan Puiu wrote: [...] >>>> diff --git a/man2/add_key.2 b/man2/add_key.2 >>>> index 56fc6d198d21..215de20baeae 100644 >>>> --- a/man2/add_key.2 >>>> +++ b/man2/add_key.2 >>>> @@ -167,7 +167,7 @@ The size of the string (including the terminating null byte) specified in >>>> .I type >>>> or >>>> .I description >>>> -exceeded the limit (32 bytes and 4096 bytes respectively). >>>> +exceeded the limit (32 bytes and 4Ki bytes respectively). >>> >>> For what it's worth, I find 4096 much clearer over 4Ki (what is Ki >>> anyway?). Ditto for 32768 / 32Ki etc. What are we trying to achieve? >> >> In this case, we should rather use 4\ KiB, which is standard. > > Maybe it is standard, but why is 4 KiB better / more suitable than 4096? 4 KiB is not that much better than 4096, since 4096 is easy to read. For higher numbers such as 33554432, it becomes more important to use 32 KiB. For consistency, using 4 KiB seems reasonable. Cheers, Alex -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
