Library vs. libraries

[Martin Eberhard Schauer <Martin.E.Schauer@gmx.de>]

Hello,
when translating package descriptions again and again I encounter
a nonconsistent use of "library". Mostly, the short description contains
library and the long description contains "libraries". Often the package
list shows a name with different extensions in /usr/lib - a library and
a number of symbolic links. For me it's just a library with multiple names.

A short example:

# http://packages.debian.org/sid/i386/libgck0/filelist
# Filelist of package libgck0 in sid of architecture i386
# /usr/lib/libgck.so.0
# /usr/lib/libgck.so.0.0.0
# /usr/share/doc/libgck0/AUTHORS
# ...

# Source: gnome-keyring
# Package: libgck0
# Versions: libgck0 (3.0.3-2), libgck0 (3.0.0-2), libgck0 (3.0.0-3), 
libgck0 (3.0.2-1)
# This Description is active
# Prioritize: 41
Description: Glib wrapper library for PKCS#11 - runtime
 GCK is a wrapper based on GLib implementing the PKCS#11 (Cryptoki)
 interface.
 .
 This package contains the shared libraries needed to run programs
 built against the GCK library.

###########################################################

I'm too pedantic? I have not noticed anything? Or is it a common mistake?

Cheers,
  Martin