Annotation of embedaddon/ntp/ports/winnt/libntp/messages.mc, revision 1.1.1.1

1.1       misho       1: ; /*
                      2: ; Microsoft Developer Support
                      3: ; Copyright (c) 1992 Microsoft Corporation
                      4: ;
                      5: ; This file contains the message definitions for the Win32
                      6: ; syslog support messages for the nntp firewall
                      7: 
                      8: ;-------------------------------------------------------------------------
                      9: ; HEADER SECTION
                     10: ;
                     11: ; The header section defines names and language identifiers for use
                     12: ; by the message definitions later in this file. The MessageIdTypedef,
                     13: ; SeverityNames, FacilityNames, and LanguageNames keywords are
                     14: ; optional and not required.
                     15: ;
                     16: ;
                     17: MessageIdTypedef=DWORD
                     18: ;
                     19: ; The MessageIdTypedef keyword gives a typedef name that is used in a
                     20: ; type cast for each message code in the generated include file. Each
                     21: ; message code appears in the include file with the format: #define
                     22: ; name ((type) 0xnnnnnnnn) The default value for type is empty, and no
                     23: ; type cast is generated. It is the programmer's responsibility to
                     24: ; specify a typedef statement in the application source code to define
                     25: ; the type. The type used in the typedef must be large enough to
                     26: ; accomodate the entire 32-bit message code.
                     27: ;
                     28: ;
                     29: SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
                     30:                Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
                     31:                Warning=0x2:STATUS_SEVERITY_WARNING
                     32:                Error=0x3:STATUS_SEVERITY_ERROR
                     33:               )
                     34: ;
                     35: ; The SeverityNames keyword defines the set of names that are allowed
                     36: ; as the value of the Severity keyword in the message definition. The
                     37: ; set is delimited by left and right parentheses. Associated with each
                     38: ; severity name is a number that, when shifted left by 30, gives the
                     39: ; bit pattern to logical-OR with the Facility value and MessageId
                     40: ; value to form the full 32-bit message code. The default value of
                     41: ; this keyword is:
                     42: ;
                     43: ; SeverityNames=(
                     44: ;   Success=0x0
                     45: ;   Informational=0x1
                     46: ;   Warning=0x2
                     47: ;   Error=0x3
                     48: ;   )
                     49: ;
                     50: ; Severity values occupy the high two bits of a 32-bit message code.
                     51: ; Any severity value that does not fit in two bits is an error. The
                     52: ; severity codes can be given symbolic names by following each value
                     53: ; with :name
                     54: ;
                     55: ;
                     56: ;FacilityNames=(System=0x0:FACILITY_SYSTEM
                     57: ;               Runtime=0x2:FACILITY_RUNTIME
                     58: ;               Stubs=0x3:FACILITY_STUBS
                     59: ;               Io=0x4:FACILITY_IO_ERROR_CODE
                     60: ;              )
                     61: ;
                     62: ; The FacilityNames keyword defines the set of names that are allowed
                     63: ; as the value of the Facility keyword in the message definition. The
                     64: ; set is delimited by left and right parentheses. Associated with each
                     65: ; facility name is a number that, when shift it left by 16 bits, gives
                     66: ; the bit pattern to logical-OR with the Severity value and MessageId
                     67: ; value to form the full 32-bit message code. The default value of
                     68: ; this keyword is:
                     69: ;
                     70: ; FacilityNames=(
                     71: ;   System=0x0FF
                     72: ;   Application=0xFFF
                     73: ;   )
                     74: ;
                     75: ; Facility codes occupy the low order 12 bits of the high order
                     76: ; 16-bits of a 32-bit message code. Any facility code that does not
                     77: ; fit in 12 bits is an error. This allows for 4,096 facility codes.
                     78: ; The first 256 codes are reserved for use by the system software. The
                     79: ; facility codes can be given symbolic names by following each value
                     80: ; with :name
                     81: ;
                     82: ;
                     83: ; The LanguageNames keyword defines the set of names that are allowed
                     84: ; as the value of the Language keyword in the message definition. The
                     85: ; set is delimited by left and right parentheses. Associated with each
                     86: ; language name is a number and a file name that are used to name the
                     87: ; generated resource file that contains the messages for that
                     88: ; language. The number corresponds to the language identifier to use
                     89: ; in the resource table. The number is separated from the file name
                     90: ; with a colon. The initial value of LanguageNames is:
                     91: ;
                     92: ; LanguageNames=(English=1:MSG00001)
                     93: ;
                     94: ; Any new names in the source file which don't override the built-in
                     95: ; names are added to the list of valid languages. This allows an
                     96: ; application to support private languages with descriptive names.
                     97: ;
                     98: ;
                     99: ;-------------------------------------------------------------------------
                    100: ; MESSAGE DEFINITION SECTION
                    101: ;
                    102: ; Following the header section is the body of the Message Compiler
                    103: ; source file. The body consists of zero or more message definitions.
                    104: ; Each message definition begins with one or more of the following
                    105: ; statements:
                    106: ;
                    107: ; MessageId = [number|+number]
                    108: ; Severity = severity_name
                    109: ; Facility = facility_name
                    110: ; SymbolicName = name
                    111: ;
                    112: ; The MessageId statement marks the beginning of the message
                    113: ; definition. A MessageID statement is required for each message,
                    114: ; although the value is optional. If no value is specified, the value
                    115: ; used is the previous value for the facility plus one. If the value
                    116: ; is specified as +number then the value used is the previous value
                    117: ; for the facility, plus the number after the plus sign. Otherwise, if
                    118: ; a numeric value is given, that value is used. Any MessageId value
                    119: ; that does not fit in 16 bits is an error.
                    120: ;
                    121: ; The Severity and Facility statements are optional. These statements
                    122: ; specify additional bits to OR into the final 32-bit message code. If
                    123: ; not specified they default to the value last specified for a message
                    124: ; definition. The initial values prior to processing the first message
                    125: ; definition are:
                    126: ;
                    127: ; Severity=Success
                    128: ; Facility=Application
                    129: ;
                    130: ; The value associated with Severity and Facility must match one of
                    131: ; the names given in the FacilityNames and SeverityNames statements in
                    132: ; the header section. The SymbolicName statement allows you to
                    133: ; associate a C/C++ symbolic constant with the final 32-bit message
                    134: ; code.
                    135: ; */
                    136: 
                    137: MessageId=0x1
                    138: Severity=Error
                    139: Facility=Application
                    140: SymbolicName=NTP_ERROR
                    141: Language=English
                    142: %1
                    143: .
                    144: 
                    145: MessageId=0x2
                    146: Severity=Warning
                    147: Facility=Application
                    148: SymbolicName=NTP_WARNING
                    149: Language=English
                    150: %1
                    151: 
                    152: .
                    153: MessageId=0x3
                    154: Severity=Informational
                    155: Facility=Application
                    156: SymbolicName=NTP_INFO
                    157: Language=English
                    158: %1
                    159: 
                    160: 
                    161: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>