On Sat, Jul 02, 2022 at 10:44:46AM +0200, Niels Thykier wrote: > Adding my cents to this. I do not feel that wrap-and-sort should touch > `Description` at all. It is a free form field and we cannot say when > there is legitimate use-case for multiple spaces in a row.
I'm sure you can remember better than me, but ISTR Description is
defined in a way that lines starting with a space (so, two spaces from
the start of the line including the space used to define multine fields)
is considered "verbatim", whereas everything else is considered a
regular paragraph, and the rendering is up to the program reading the
Description field, no promises given.
As such, I think that lines that do not start with the 2 spaces should
be safe to strip of double spaces.
But, there is another point: some stylistic guides instruct people to
write two spaces after a full stop. I'm not even sure how, but even I
picked up on that style, despite pretty much everybody else in the
world saying that only one space is correct :D
So.. well... yes, let's not touch that indeed. I can also kind of argue
that trimming spaces within a description line is not really the goal of
wrap-and-sort.
> On the flip side, the dependency field that pabs mentioned would be fine
> to fix.
Yes.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
