Andreas Enge <andr...@enge.fr> skribis:
> On Sat, Dec 07, 2013 at 09:24:42PM +0100, Andreas Enge wrote:
>> All very reasonable. Let us go for this (and I should add a section to the
>> packaging guidelines later on).
>
> Months later, here is a proposed patch in British English. Do we have a rule
> on which spelling to use? British is what I learnt at school.
> (I feel like starting a bikeshed discussion ;-).)
I use American English, as the settings at the end of guix.texi enforce
for those using the Right Editor. ;-)
I’d prefer to keep it that way, if that’s OK. WDYT?
> @node Software Freedom
> @@ -2796,8 +2797,8 @@ Both are usually the same and correspond to the
> lowercase conversion of the
> project name chosen upstream. For instance, the GNUnet project is packaged
> as @code{gnunet}. We do not add @code{lib} prefixes for library packages,
> unless these are already part of the official project name. But see
> -@ref{Python Modules} for special rules concerning modules for
> -the Python language.
> +@ref{Python Modules} and @ref{Perl Modules} for special rules concerning
> +modules for the Python and Perl languages.
Should be @pxref{Python Modules} and @ref{Perl Modules} (info "(texinfo) @ref").
> +For perl packages containing a single class, we use the lowercase class name,
“Perl”, capitalized.
Also, two spaces after end-of-sentence periods.
Thanks, that’s a useful addition.
Ludo’.
