|
@@ -23,7 +23,7 @@
|
|
$PREFIX MSG_
|
|
$PREFIX MSG_
|
|
$NAMESPACE isc::log
|
|
$NAMESPACE isc::log
|
|
|
|
|
|
-% DUPMSGID duplicate message ID (%s) in compiled code
|
|
|
|
|
|
+% DUPMSGID duplicate message ID (%1) in compiled code
|
|
Indicative of a programming error, when it started up, BIND10 detected that
|
|
Indicative of a programming error, when it started up, BIND10 detected that
|
|
the given message ID had been registered by one or more modules. (All message
|
|
the given message ID had been registered by one or more modules. (All message
|
|
IDs should be unique throughout BIND10.) This has no impact on the operation
|
|
IDs should be unique throughout BIND10.) This has no impact on the operation
|
|
@@ -34,12 +34,12 @@ particular message, the text supplied by the module that added the original
|
|
ID will be output - something that may bear no relation to the condition being
|
|
ID will be output - something that may bear no relation to the condition being
|
|
logged.
|
|
logged.
|
|
|
|
|
|
-% DUPLNS line %s: duplicate $NAMESPACE directive found
|
|
|
|
|
|
+% DUPLNS line %1: duplicate $NAMESPACE directive found
|
|
When reading a message file, more than one $NAMESPACE directive was found. In
|
|
When reading a message file, more than one $NAMESPACE directive was found. In
|
|
this version of the code, such a condition is regarded as an error and the
|
|
this version of the code, such a condition is regarded as an error and the
|
|
read will be abandoned.
|
|
read will be abandoned.
|
|
|
|
|
|
-% IDNOTFND could not replace message text for '%s': no such message
|
|
|
|
|
|
+% IDNOTFND could not replace message text for '%1': no such message
|
|
During start-up a local message file was read. A line with the listed
|
|
During start-up a local message file was read. A line with the listed
|
|
message identification was found in the file, but the identification is not
|
|
message identification was found in the file, but the identification is not
|
|
one contained in the compiled-in message dictionary. Either the message
|
|
one contained in the compiled-in message dictionary. Either the message
|
|
@@ -50,70 +50,70 @@ identification has been removed.
|
|
This message may appear a number of times in the file, once for every such
|
|
This message may appear a number of times in the file, once for every such
|
|
unknown message identification.
|
|
unknown message identification.
|
|
|
|
|
|
-% INVMSGID line %s: invalid message identification '%s'
|
|
|
|
|
|
+% INVMSGID line %1: invalid message identification '%2'
|
|
The concatenation of the prefix and the message identification is used as
|
|
The concatenation of the prefix and the message identification is used as
|
|
a symbol in the C++ module; as such it may only contain
|
|
a symbol in the C++ module; as such it may only contain
|
|
|
|
|
|
-% NOMSGID line %s: message definition line found without a message ID
|
|
|
|
|
|
+% NOMSGID line %1: message definition line found without a message ID
|
|
Message definition lines are lines starting with a "%". The rest of the line
|
|
Message definition lines are lines starting with a "%". The rest of the line
|
|
should comprise the message ID and text describing the message. This error
|
|
should comprise the message ID and text describing the message. This error
|
|
indicates the message compiler found a line in the message file comprising
|
|
indicates the message compiler found a line in the message file comprising
|
|
just the "%" and nothing else.
|
|
just the "%" and nothing else.
|
|
|
|
|
|
-% NOMSGTXT line %s: line found containing a message ID ('%s') and no text
|
|
|
|
|
|
+% NOMSGTXT line %1: line found containing a message ID ('%2') and no text
|
|
Message definition lines are lines starting with a "%". The rest of the line
|
|
Message definition lines are lines starting with a "%". The rest of the line
|
|
should comprise the message ID and text describing the message. This error
|
|
should comprise the message ID and text describing the message. This error
|
|
is generated when a line is found in the message file that contains the
|
|
is generated when a line is found in the message file that contains the
|
|
leading "%" and the message identification but no text.
|
|
leading "%" and the message identification but no text.
|
|
|
|
|
|
-% NSEXTRARG line %s: $NAMESPACE directive has too many arguments
|
|
|
|
|
|
+% NSEXTRARG line %1: $NAMESPACE directive has too many arguments
|
|
The $NAMESPACE directive takes a single argument, a namespace in which all the
|
|
The $NAMESPACE directive takes a single argument, a namespace in which all the
|
|
generated symbol names are placed. This error is generated when the
|
|
generated symbol names are placed. This error is generated when the
|
|
compiler finds a $NAMESPACE directive with more than one argument.
|
|
compiler finds a $NAMESPACE directive with more than one argument.
|
|
|
|
|
|
-% NSINVARG line %s: $NAMESPACE directive has an invalid argument ('%s')
|
|
|
|
|
|
+% NSINVARG line %1: $NAMESPACE directive has an invalid argument ('%2')
|
|
The $NAMESPACE argument should be a valid C++ namespace. The reader does a
|
|
The $NAMESPACE argument should be a valid C++ namespace. The reader does a
|
|
cursory check on its validity, checking that the characters in the namespace
|
|
cursory check on its validity, checking that the characters in the namespace
|
|
are correct. The error is generated when the reader finds an invalid
|
|
are correct. The error is generated when the reader finds an invalid
|
|
character. (Valid are alphanumeric characters, underscores and colons.)
|
|
character. (Valid are alphanumeric characters, underscores and colons.)
|
|
|
|
|
|
-% NSNOARG line %s: no arguments were given to the $NAMESPACE directive
|
|
|
|
|
|
+% NSNOARG line %1: no arguments were given to the $NAMESPACE directive
|
|
The $NAMESPACE directive takes a single argument, a namespace in which all the
|
|
The $NAMESPACE directive takes a single argument, a namespace in which all the
|
|
generated symbol names are placed. This error is generated when the
|
|
generated symbol names are placed. This error is generated when the
|
|
compiler finds a $NAMESPACE directive with no arguments.
|
|
compiler finds a $NAMESPACE directive with no arguments.
|
|
|
|
|
|
-% OPENIN unable to open message file %s for input: %s
|
|
|
|
|
|
+% OPENIN unable to open message file %1 for input: %2
|
|
The program was not able to open the specified input message file for the
|
|
The program was not able to open the specified input message file for the
|
|
reason given.
|
|
reason given.
|
|
|
|
|
|
-% OPENOUT unable to open %s for output: %s
|
|
|
|
|
|
+% OPENOUT unable to open %1 for output: %2
|
|
The program was not able to open the specified output file for the reason
|
|
The program was not able to open the specified output file for the reason
|
|
given.
|
|
given.
|
|
|
|
|
|
-% PRFEXTRARG line %s: $PREFIX directive has too many arguments
|
|
|
|
|
|
+% PRFEXTRARG line %1: $PREFIX directive has too many arguments
|
|
The $PREFIX directive takes a single argument, a prefix to be added to the
|
|
The $PREFIX directive takes a single argument, a prefix to be added to the
|
|
symbol names when a C++ .h file is created. This error is generated when the
|
|
symbol names when a C++ .h file is created. This error is generated when the
|
|
compiler finds a $PREFIX directive with more than one argument.
|
|
compiler finds a $PREFIX directive with more than one argument.
|
|
|
|
|
|
-% PRFINVARG line %s: $PREFIX directive has an invalid argument ('%s')
|
|
|
|
|
|
+% PRFINVARG line %1: $PREFIX directive has an invalid argument ('%2')
|
|
The $PREFIX argument is used in a symbol name in a C++ header file. As such,
|
|
The $PREFIX argument is used in a symbol name in a C++ header file. As such,
|
|
it must adhere to restrictions on C++ symbol names (e.g. may only contain
|
|
it must adhere to restrictions on C++ symbol names (e.g. may only contain
|
|
alphanumeric characters or underscores, and may nor start with a digit).
|
|
alphanumeric characters or underscores, and may nor start with a digit).
|
|
A $PREFIX directive was found with an argument (given in the message) that
|
|
A $PREFIX directive was found with an argument (given in the message) that
|
|
violates those restictions.
|
|
violates those restictions.
|
|
|
|
|
|
-% RDLOCMES reading local message file %s
|
|
|
|
|
|
+% RDLOCMES reading local message file %1
|
|
This is an informational message output by BIND10 when it starts to read a
|
|
This is an informational message output by BIND10 when it starts to read a
|
|
local message file. (A local message file may replace the text of one of more
|
|
local message file. (A local message file may replace the text of one of more
|
|
messages; the ID of the message will not be changed though.)
|
|
messages; the ID of the message will not be changed though.)
|
|
|
|
|
|
-% READERR error reading from message file %s: %s
|
|
|
|
|
|
+% READERR error reading from message file %1: %2
|
|
The specified error was encountered reading from the named message file.
|
|
The specified error was encountered reading from the named message file.
|
|
|
|
|
|
-% WRITERR error writing to %s: %s
|
|
|
|
|
|
+% WRITERR error writing to %1: %2
|
|
The specified error was encountered by the message compiler when writing to
|
|
The specified error was encountered by the message compiler when writing to
|
|
the named output file.
|
|
the named output file.
|
|
|
|
|
|
-% UNRECDIR line %s: unrecognised directive '%s'
|
|
|
|
|
|
+% UNRECDIR line %1: unrecognised directive '%2'
|
|
A line starting with a dollar symbol was found, but the first word on the line
|
|
A line starting with a dollar symbol was found, but the first word on the line
|
|
(shown in the message) was not a recognised message compiler directive.
|
|
(shown in the message) was not a recognised message compiler directive.
|