Browse Source

[trac1077] add space between "BIND 10"

Where is the style guide for .mes messages files?
Jeremy C. Reed 14 years ago
parent
commit
27c6b8cef4
1 changed files with 7 additions and 7 deletions
  1. 7 7
      src/lib/log/log_messages.mes

+ 7 - 7
src/lib/log/log_messages.mes

@@ -36,8 +36,8 @@ Logging has been configured so that output is written to the terminal
 Allowed values are "stdout" and "stderr".
 Allowed values are "stdout" and "stderr".
 
 
 % LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code
 % LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code
-During start-up, BIND10 detected that the given message identification
-had been defined multiple times in the BIND10 code.  This indicates a
+During start-up, BIND 10 detected that the given message identification
+had been defined multiple times in the BIND 10 code.  This indicates a
 programming error; please log a bug report.
 programming error; please log a bug report.
 
 
 % LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found
 % LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found
@@ -99,10 +99,10 @@ There may be several reasons why this message may appear:
 - The program outputting the message may not use that particular message
 - The program outputting the message may not use that particular message
 (e.g. it originates in a module not used by the program.)
 (e.g. it originates in a module not used by the program.)
 
 
-- The local file was written for an earlier version of the BIND10 software
+- The local file was written for an earlier version of the BIND 10 software
 and the later version no longer generates that message.
 and the later version no longer generates that message.
 
 
-Whatever the reason, there is no impact on the operation of BIND10.
+Whatever the reason, there is no impact on the operation of BIND 10.
 
 
 % LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2
 % LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2
 Originating within the logging code, the program was not able to open
 Originating within the logging code, the program was not able to open
@@ -115,7 +115,7 @@ This error is generated when the compiler finds a $PREFIX directive with
 more than one argument.
 more than one argument.
 
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND10.
+version of BIND 10.
 
 
 % LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')
 % LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')
 Within a message file, the $PREFIX directive takes a single argument,
 Within a message file, the $PREFIX directive takes a single argument,
@@ -126,10 +126,10 @@ with a digit).  A $PREFIX directive was found with an argument (given
 in the message) that violates those restrictions.
 in the message) that violates those restrictions.
 
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND10.
+version of BIND 10.
 
 
 % LOG_READING_LOCAL_FILE reading local message file %1
 % LOG_READING_LOCAL_FILE reading local message file %1
-This is an informational message output by BIND10 when it starts to read
+This is an informational message output by BIND 10 when it starts to read
 a local message file.  (A local message file may replace the text of
 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.)
 one of more messages; the ID of the message will not be changed though.)