[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#871791: lintian: spelling-error-in-{binary,manpage} "CAs Case" annoying for cryptographic software



Package: lintian
Version: 2.5.52
Tags: patch

Maybe it's just the kind of software that i maintain, but i've been
seeing a lot of "spelling-error-in-binary" and
"spelling-error-in-manpage" lintiain informational statuses that
suggest "CAs" should be "Case".

This isn't the case (ha ha) for cryptographic tools which deal with
Certificate Authorities, which are often known as CAs.

The crude fix is to just remove this check entirely, but that would be
a shame because i'm sure "case" is actually sometimes misspelled as
"cas".

The more subtle fix would be to accept that this particular
capitalization ("CAs") is OK, but any other capitalization is not, and
is likely supposed to be "case".  However, i don't understand the
lintian check_spelling code well enough to know how to implement that
fix.

So my proposed middlebrow fix (see patch below) is to consider any
case of "cas" other than "CAs" to be a misspelling of "CAs", rather
than a misspelling of "case".  If someone cleverer than me can propose
a more nuanced fix, i'd be even happier.

            --dkg

diff --git a/data/spelling/corrections b/data/spelling/corrections
index e7baaa908..d23dad91e 100644
--- a/data/spelling/corrections
+++ b/data/spelling/corrections
@@ -598,7 +598,6 @@ captial||capital
 carefull||careful
 carefuly||carefully
 cariage||carriage
-cas||case
 casue||cause
 casued||caused
 casues||causes
diff --git a/data/spelling/corrections-case b/data/spelling/corrections-case
index 193f059bc..a391e6462 100644
--- a/data/spelling/corrections-case
+++ b/data/spelling/corrections-case
@@ -14,6 +14,7 @@ api||API
 Api||API
 arabic||Arabic
 british||British
+cas||CAs
 chinese||Chinese
 cyrillic||Cyrillic
 czech||Czech


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils                          2.28-6
ii  bzip2                             1.0.6-8.1
ii  diffstat                          1.61-1+b1
ii  dpkg                              1.18.24
ii  file                              1:5.30-1
ii  gettext                           0.19.8.1-2+b1
ii  intltool-debian                   0.35.0+20060710.4
ii  libapt-pkg-perl                   0.1.32+b2
ii  libarchive-zip-perl               1.59-1
ii  libclass-accessor-perl            0.34-1
ii  libclone-perl                     0.38-2+b2
ii  libdpkg-perl                      1.18.24
ii  libemail-valid-perl               1.202-1
ii  libfile-basedir-perl              0.07-1
ii  libipc-run-perl                   0.96-1
ii  liblist-moreutils-perl            0.416-1+b3
ii  libparse-debianchangelog-perl     1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-7
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl          0.13-1
ii  libtimedate-perl                  2.3000-2
ii  liburi-perl                       1.71-1
ii  libxml-simple-perl                2.24-1
ii  libyaml-libyaml-perl              0.63-2+b2
ii  man-db                            2.7.6.1-2
ii  patchutils                        0.3.4-2
ii  perl                              5.26.0-5
ii  t1utils                           1.40-2
ii  xz-utils                          5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  <none>

Versions of packages lintian suggests:
pn  binutils-multiarch     <none>
ii  dpkg-dev               1.18.24
ii  libhtml-parser-perl    3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information


Reply to: