fabien boucher wrote:Well, for a start the three different packages should have three
> Package: libxr
> Description: cross-platform XML-RPC client/server library
As a non-programmer I have to admit I'm a bit out of my depth
dealing with this interface description language stuff. Still, I
gather "cross-platform" means that there's a Windows version; but is
that really this library's only selling point important enough to go
in the short description? Debian already seems to have quite a few
So I suspect you want something along the general lines of:
Description: SSL-capable XML-RPC implementation - shared libraries
Description: SSL-capable XML-RPC implementation - development files
Description: SSL-capable XML-RPC implementation - debug symbols
I didn't quite follow the structure of that sentence, but I see in
> This library supports persistent HTTP/1.1 connections over SSL
> and comes with XML-RPC interface description language and
> client/server code compiler.
the README file "libxr has two parts, library itself and RPC
interface description language compiler (XDL compiler)". That makes
it a bit clearer.
And presumably libxr doesn't support _arbitrary_ persistent HTTP/1.1
connections over SSL, just XMLRPCish ones. I'd tentatively suggest:
This cross-platform XML-RPC library supports persistent HTTP/1.1
connections over SSL, and comes with a client/server XDL compiler.
(Unless I'm completely garbling it, which is possible.)
Then the other packages in the set just differ in their trailing
> This package contains development headers needed to compile programsThat might or might not need an article ("the development headers
> that use libxr.
> This package contains debugging symbols useful for tracking bugs inDo you mean "tracking" or "tracking down", or maybe "tracing"?
> applications with libxr.
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
To UNSUBSCRIBE, email to debian-l10n-english-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com