File: ExceptionMessages.resx

package info (click to toggle)
mono 4.6.2.7+dfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 778,148 kB
  • ctags: 914,052
  • sloc: cs: 5,779,509; xml: 2,773,713; ansic: 432,645; sh: 14,749; makefile: 12,361; perl: 2,488; python: 1,434; cpp: 849; asm: 531; sql: 95; sed: 16; php: 1
file content (289 lines) | stat: -rw-r--r-- 11,484 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 1.3
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">1.3</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1">this is my long string</data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        [base64 mime encoded serialized .NET Framework object]
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        [base64 mime encoded string representing a byte array form of the .NET Framework object]
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used forserialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>1.3</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="TOSTRING">
    <value>{0}: {1} ({2}) {3}</value>
  </data>
  <data name="SERVER_MSG">
    <value>{0}: Server Message: {1}</value>
  </data>
  <data name="MATCHED_DN">
    <value>{0}: Matched DN: {1}</value>
  </data>
  <data name="FAILED_REFERRAL">
    <value>{0}: Failed Referral: {1}</value>
  </data>
  <data name="REFERRAL_ITEM">
    <value>{0}: Referral: {1}</value>
  </data>
  <data name="CONNECTION_ERROR">
    <value>Unable to connect to server {0}:{1}</value>
  </data>
  <data name="CONNECTION_IMPOSSIBLE">
    <value>Unable to reconnect to server, application has never called connect()</value>
  </data>
  <data name="CONNECTION_WAIT">
    <value>Connection lost waiting for results from {0}:{1}</value>
  </data>
  <data name="CONNECTION_FINALIZED">
    <value>Connection closed by the application finalizing the object</value>
  </data>
  <data name="CONNECTION_CLOSED">
    <value>Connection closed by the application disconnecting</value>
  </data>
  <data name="CONNECTION_READER">
    <value>Reader thread terminated</value>
  </data>
  <data name="DUP_ERROR">
    <value>RfcLdapMessage: Cannot duplicate message built from the input stream</value>
  </data>
  <data name="REFERENCE_ERROR">
    <value>Error attempting to follow a search continuation reference</value>
  </data>
  <data name="REFERRAL_ERROR">
    <value>Error attempting to follow a referral</value>
  </data>
  <data name="REFERRAL_LOCAL">
    <value>LdapSearchResults.{0}(): No entry found &amp; request is not complete</value>
  </data>
  <data name="REFERRAL_SEND">
    <value>Error sending request to referred server</value>
  </data>
  <data name="REFERENCE_NOFOLLOW">
    <value>Search result reference received, and referral following is off</value>
  </data>
  <data name="REFERRAL_BIND">
    <value>LdapBind.bind() function returned null</value>
  </data>
  <data name="REFERRAL_BIND_MATCH">
    <value>Could not match LdapBind.bind() connection with Server Referral URL list</value>
  </data>
  <data name="NO_DUP_REQUEST">
    <value>Cannot duplicate message to follow referral for {0} request, not allowed</value>
  </data>
  <data name="SERVER_CONNECT_ERROR">
    <value>Error connecting to server {0} while attempting to follow a referral</value>
  </data>
  <data name="NO_SUP_PROPERTY">
    <value>Requested property is not supported.</value>
  </data>
  <data name="ENTRY_PARAM_ERROR">
    <value>Invalid Entry parameter</value>
  </data>
  <data name="DN_PARAM_ERROR">
    <value>Invalid DN parameter</value>
  </data>
  <data name="RDN_PARAM_ERROR">
    <value>Invalid DN or RDN parameter</value>
  </data>
  <data name="OP_PARAM_ERROR">
    <value>Invalid extended operation parameter, no OID specified</value>
  </data>
  <data name="PARAM_ERROR">
    <value>Invalid parameter</value>
  </data>
  <data name="DECODING_ERROR">
    <value>Error Decoding responseValue</value>
  </data>
  <data name="ENCODING_ERROR">
    <value>Encoding Error</value>
  </data>
  <data name="IO_EXCEPTION">
    <value>I/O Exception on host {0}, port {1}</value>
  </data>
  <data name="INVALID_ESCAPE">
    <value>Invalid value in escape sequence "{0}"</value>
  </data>
  <data name="SHORT_ESCAPE">
    <value>Incomplete escape sequence</value>
  </data>
  <data name="UNEXPECTED_END">
    <value>Unexpected end of filter</value>
  </data>
  <data name="MISSING_LEFT_PAREN">
    <value>Unmatched parentheses, left parenthesis missing</value>
  </data>
  <data name="NO_OPTION">
    <value>Semicolon present, but no option specified</value>
  </data>
  <data name="MISSING_RIGHT_PAREN">
    <value>Unmatched parentheses, right parenthesis missing</value>
  </data>
  <data name="EXPECTING_RIGHT_PAREN">
    <value>Expecting right parenthesis, found "{0}"</value>
  </data>
  <data name="EXPECTING_LEFT_PAREN">
    <value>Expecting left parenthesis, found "{0}"</value>
  </data>
  <data name="NO_ATTRIBUTE_NAME">
    <value>Missing attribute description</value>
  </data>
  <data name="NO_DN_NOR_MATCHING_RULE">
    <value>DN and matching rule not specified</value>
  </data>
  <data name="NO_MATCHING_RULE">
    <value>Missing matching rule</value>
  </data>
  <data name="INVALID_FILTER_COMPARISON">
    <value>Invalid comparison operator</value>
  </data>
  <data name="INVALID_CHAR_IN_FILTER">
    <value>The invalid character "{0}" needs to be escaped as "{1}"</value>
  </data>
  <data name="INVALID_ESC_IN_DESCR">
    <value>Escape sequence not allowed in attribute description</value>
  </data>
  <data name="INVALID_CHAR_IN_DESCR">
    <value>Invalid character "{0}" in attribute description</value>
  </data>
  <data name="NOT_AN_ATTRIBUTE">
    <value>Schema element is not an LdapAttributeSchema object</value>
  </data>
  <data name="UNEQUAL_LENGTHS">
    <value>Length of attribute Name array does not equal length of Flags array</value>
  </data>
  <data name="IMPROPER_REFERRAL">
    <value>Referral not supported for command {0}</value>
  </data>
  <data name="NOT_IMPLEMENTED">
    <value>Method LdapConnection.startTLS not implemented</value>
  </data>
  <data name="NO_MEMORY">
    <value>All results could not be stored in memory, sort failed</value>
  </data>
  <data name="SERVER_SHUTDOWN_REQ">
    <value>Received unsolicited notification from server {0}:{1} to shutdown</value>
  </data>
  <data name="INVALID_ADDRESS">
    <value>Invalid syntax for address with port; {0}</value>
  </data>
  <data name="UNKNOWN_RESULT">
    <value>Unknown Ldap result code {0}</value>
  </data>
  <data name="OUTSTANDING_OPERATIONS">
    <value>Cannot start or stop TLS because outstanding Ldap operations exist on this connection</value>
  </data>
  <data name="WRONG_FACTORY">
    <value>StartTLS cannot use the set socket factory because it does not implement LdapTLSSocketFactory</value>
  </data>
  <data name="NO_TLS_FACTORY">
    <value>StartTLS failed because no LdapTLSSocketFactory has been set for this Connection</value>
  </data>
  <data name="NO_STARTTLS">
    <value>An attempt to stopTLS on a connection where startTLS had not been called</value>
  </data>
  <data name="STOPTLS_ERROR">
    <value>Error stopping TLS: Error getting input &amp; output streams from the original socket</value>
  </data>
  <data name="MULTIPLE_SCHEMA">
    <value>Multiple schema found when reading the subschemaSubentry for {0}</value>
  </data>
  <data name="NO_SCHEMA">
    <value>No schema found when reading the subschemaSubentry for {0}</value>
  </data>
  <data name="READ_MULTIPLE">
    <value>Read response is ambiguous, multiple entries returned</value>
  </data>
  <data name="CANNOT_BIND">
    <value>Cannot bind. Use PoolManager.getBoundConnection()</value>
  </data>
  <data name="SSL_PROVIDER_MISSING">
    <value>Please ensure that SSL Provider is properly installed.</value>
  </data>
</root>