Commit 8f7643f4 authored by Guillem Jover's avatar Guillem Jover

Switch some words to their american spelling

parent 3d98111b
......@@ -178,7 +178,7 @@ was not configured, just as if the package was being configured for
the first time.
Trigger processing should be idempotent. The list of triggers being
processed is provided to the postinst only so that it can optimise
processed is provided to the postinst only so that it can optimize
away redundant processing.
In that case, where an interested package has more than one trigger
......@@ -222,7 +222,7 @@ triggering packages *will* await their configuration (which implies
completion of any necessary trigger processing) or removal.
It is not defined in what order triggers will run. dpkg will make
some effort to minimise redundant work in the case where many packages
some effort to minimize redundant work in the case where many packages
have postinst trigger processing activating another package's triggers
(for example, by processing triggers in fifo order during a single
dpkg run). Cycles in the triggering graph are prohibited and will
......@@ -306,8 +306,8 @@ in any unsupported trigger kinds cannot be configured (since such a
package cannot be guaranteed to have these triggers properly activated
by dpkg). Therefore no package can be interested in any unsupported
trigger kinds and they can be freely activated (both by ‘activate’ and
by dpkg-trigger). dpkg-deb will be changed to warn about unrecognised
trigger names syntaxes and unrecognised trigger control directives.
by dpkg-trigger). dpkg-deb will be changed to warn about unrecognized
trigger names syntaxes and unrecognized trigger control directives.
New command line interfaces to dpkg tools
......@@ -728,7 +728,7 @@ await the trigger.
system. Processes hang onto this lock only briefly: dpkg-trigger
to add new activations, or dpkg to incorporate activations (and
perhaps when it updates interests). Therefore this lock is always
acquired with F_GETLKW so as to serialise rather than fail on
acquired with F_GETLKW so as to serialize rather than fail on
contention.
......
......@@ -175,7 +175,7 @@ Package information can be included by inserting
variable references to package fields using the syntax
\(lq\fB${\fP\fIfield\fR[\fB;\fP\fIwidth\fR]\fB}\fP\(rq. Fields are
printed right-aligned unless the width is negative in which case left
alignment will be used. The following \fIfield\fRs are recognised but
alignment will be used. The following \fIfield\fRs are recognized but
they are not necessarily available in the status file (only internal
fields or fields stored in the binary package end up in it):
......
......@@ -151,7 +151,7 @@ is
.BR Depends .
If the same dependency entry (or set of alternatives) appears in more
than one of the recognised dependency field names
than one of the recognized dependency field names
.BR Pre\-Depends ", " Depends ", " Recommends ", " Enhances " or " Suggests
then
.B dpkg\-shlibdeps
......
......@@ -36,7 +36,7 @@ triggers control file directive, are insufficiently rich. It can also
be used for testing and by system administrators (but note that the
triggers won't actually be run by \fBdpkg\-trigger\fP).
.PP
Unrecognised trigger name syntaxes are an error for \fBdpkg\-trigger\fP.
Unrecognized trigger name syntaxes are an error for \fBdpkg\-trigger\fP.
.
.SH COMMANDS
.TP
......
......@@ -87,7 +87,7 @@ is usually called from the
.B prerm
(install) scripts in Debian packages.
.PP
It is often useful for a number of alternatives to be synchronised,
It is often useful for a number of alternatives to be synchronized,
so that they are changed as a group; for example, when several versions
of the
.BR vi (1)
......
......@@ -166,7 +166,7 @@ sub parse {
}
push @blanklines, $_;
} else {
$self->parse_error($file, $., _g("unrecognised line"), "$_");
$self->parse_error($file, $., _g("unrecognized line"), "$_");
unless ($expect eq START_CHANGES or $expect eq CHANGES_OR_TRAILER) {
# lets assume change data if we expected it
$entry->extend_part("changes", [ @blanklines, $_]);
......
......@@ -101,7 +101,7 @@ foreach (@ARGV) {
} elsif (m/^-d(.*)$/) {
$dependencyfield = field_capitalize($1);
defined($depstrength{$dependencyfield}) ||
warning(_g("unrecognised dependency field \`%s'"), $dependencyfield);
warning(_g("unrecognized dependency field '%s'"), $dependencyfield);
} elsif (m/^-e(.*)$/) {
if (exists $exec{$1}) {
# Affect the binary to the most important field
......@@ -572,7 +572,7 @@ sub usage {
-?, --help show this help message.
--version show the version.")
. "\n\n" . _g(
"Dependency fields recognised are:
"Dependency fields recognized are:
%s
"), $progname, join("/",@depfields);
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment