|
@@ -23,7 +23,7 @@ $NAMESPACE isc::log
|
|
|
# chicken-and-egg situation where we need the files to build the message
|
|
|
# compiler, yet we need the compiler to build the files.
|
|
|
|
|
|
-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
|
|
|
+ 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
|
|
@@ -44,7 +44,7 @@ DUPLPRFX duplicate $PREFIX directive found
|
|
|
+ this version of the code, such a condition is regarded as an error and the
|
|
|
+ read will be abandoned.
|
|
|
|
|
|
-IDNOTFND could not replace message for '%s': no such message identification
|
|
|
+IDNOTFND could not replace message for '%1': no such message identification
|
|
|
+ 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
|
|
|
+ one contained in the compiled-in message dictionary. Either the message
|
|
@@ -55,10 +55,10 @@ IDNOTFND could not replace message for '%s': no such message identification
|
|
|
+ This message may appear a number of times in the file, once for every such
|
|
|
+ unknown message identification.
|
|
|
|
|
|
-MSGRDERR error reading from message file %s: %s
|
|
|
+MSGRDERR error reading from message file %1: %2
|
|
|
+ The specified error was encountered reading from the named message file.
|
|
|
|
|
|
-MSGWRTERR error writing to %s: %s
|
|
|
+MSGWRTERR error writing to %1: %2
|
|
|
+ The specified error was encountered by the message compiler when writing to
|
|
|
+ the named output file.
|
|
|
|
|
@@ -67,13 +67,13 @@ NSEXTRARG $NAMESPACE directive has too many arguments
|
|
|
+ generated symbol names are placed. This error is generated when the
|
|
|
+ compiler finds a $NAMESPACE directive with more than one argument.
|
|
|
|
|
|
-NSINVARG $NAMESPACE directive has an invalid argument ('%s')
|
|
|
+NSINVARG $NAMESPACE directive has an invalid argument ('%1')
|
|
|
+ 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
|
|
|
+ are correct. The error is generated when the reader finds an invalid
|
|
|
+ character. (Valid are alphanumeric characters, underscores and colons.)
|
|
|
|
|
|
-NOMSGTXT a line containing a message ID ('%s') and nothing else was found
|
|
|
+NOMSGTXT a line containing a message ID ('%1') and nothing else was found
|
|
|
+ Message definitions comprise lines starting with a message identification (a
|
|
|
+ symbolic name for the message) and followed by the text of the message. This
|
|
|
+ error is generated when a line is found in the message file that contains just
|
|
@@ -84,11 +84,11 @@ NSNOARG no arguments were given to the $NAMESPACE directive
|
|
|
+ generated symbol names are placed. This error is generated when the
|
|
|
+ compiler finds a $NAMESPACE directive with no arguments.
|
|
|
|
|
|
-OPNMSGIN unable to open message file %s for input: %s
|
|
|
+OPNMSGIN unable to open message file %1 for input: %2
|
|
|
+ The program was not able to open the specified input message file for the
|
|
|
+ reason given.
|
|
|
|
|
|
-OPNMSGOUT unable to open %s for output: %s
|
|
|
+OPNMSGOUT unable to open %1 for output: %2
|
|
|
+ The program was not able to open the specified output file for the reason
|
|
|
+ given.
|
|
|
|
|
@@ -97,7 +97,7 @@ PRFEXTRARG $PREFIX directive has too many arguments
|
|
|
+ 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.
|
|
|
|
|
|
-PRFINVARG $PREFIX directive has an invalid argument ('%s')
|
|
|
+PRFINVARG $PREFIX directive has an invalid argument ('%1')
|
|
|
+ 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
|
|
|
+ alphanumeric characters or underscores, and may nor start with a digit). A
|
|
@@ -109,11 +109,11 @@ PRFNOARG no arguments were given to the $PREFIX directive
|
|
|
+ symbol names when a C++ .h file is created. This error is generated when the
|
|
|
+ compiler finds a $PREFIX directive with no arguments.
|
|
|
|
|
|
-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
|
|
|
+ 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.)
|
|
|
|
|
|
-UNRECDIR unrecognised directive '%s'
|
|
|
+UNRECDIR unrecognised directive '%1'
|
|
|
+ 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.
|