|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <root> |
|
3 <!-- |
|
4 Microsoft ResX Schema |
|
5 |
|
6 Version 2.0 |
|
7 |
|
8 The primary goals of this format is to allow a simple XML format |
|
9 that is mostly human readable. The generation and parsing of the |
|
10 various data types are done through the TypeConverter classes |
|
11 associated with the data types. |
|
12 |
|
13 Example: |
|
14 |
|
15 ... ado.net/XML headers & schema ... |
|
16 <resheader name="resmimetype">text/microsoft-resx</resheader> |
|
17 <resheader name="version">2.0</resheader> |
|
18 <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader> |
|
19 <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader> |
|
20 <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data> |
|
21 <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data> |
|
22 <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64"> |
|
23 <value>[base64 mime encoded serialized .NET Framework object]</value> |
|
24 </data> |
|
25 <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64"> |
|
26 <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value> |
|
27 <comment>This is a comment</comment> |
|
28 </data> |
|
29 |
|
30 There are any number of "resheader" rows that contain simple |
|
31 name/value pairs. |
|
32 |
|
33 Each data row contains a name, and value. The row also contains a |
|
34 type or mimetype. Type corresponds to a .NET class that support |
|
35 text/value conversion through the TypeConverter architecture. |
|
36 Classes that don't support this are serialized and stored with the |
|
37 mimetype set. |
|
38 |
|
39 The mimetype is used for serialized objects, and tells the |
|
40 ResXResourceReader how to depersist the object. This is currently not |
|
41 extensible. For a given mimetype the value must be set accordingly: |
|
42 |
|
43 Note - application/x-microsoft.net.object.binary.base64 is the format |
|
44 that the ResXResourceWriter will generate, however the reader can |
|
45 read any of the formats listed below. |
|
46 |
|
47 mimetype: application/x-microsoft.net.object.binary.base64 |
|
48 value : The object must be serialized with |
|
49 : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter |
|
50 : and then encoded with base64 encoding. |
|
51 |
|
52 mimetype: application/x-microsoft.net.object.soap.base64 |
|
53 value : The object must be serialized with |
|
54 : System.Runtime.Serialization.Formatters.Soap.SoapFormatter |
|
55 : and then encoded with base64 encoding. |
|
56 |
|
57 mimetype: application/x-microsoft.net.object.bytearray.base64 |
|
58 value : The object must be serialized into a byte array |
|
59 : using a System.ComponentModel.TypeConverter |
|
60 : and then encoded with base64 encoding. |
|
61 --> |
|
62 <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> |
|
63 <xsd:import namespace="http://www.w3.org/XML/1998/namespace" /> |
|
64 <xsd:element name="root" msdata:IsDataSet="true"> |
|
65 <xsd:complexType> |
|
66 <xsd:choice maxOccurs="unbounded"> |
|
67 <xsd:element name="metadata"> |
|
68 <xsd:complexType> |
|
69 <xsd:sequence> |
|
70 <xsd:element name="value" type="xsd:string" minOccurs="0" /> |
|
71 </xsd:sequence> |
|
72 <xsd:attribute name="name" use="required" type="xsd:string" /> |
|
73 <xsd:attribute name="type" type="xsd:string" /> |
|
74 <xsd:attribute name="mimetype" type="xsd:string" /> |
|
75 <xsd:attribute ref="xml:space" /> |
|
76 </xsd:complexType> |
|
77 </xsd:element> |
|
78 <xsd:element name="assembly"> |
|
79 <xsd:complexType> |
|
80 <xsd:attribute name="alias" type="xsd:string" /> |
|
81 <xsd:attribute name="name" type="xsd:string" /> |
|
82 </xsd:complexType> |
|
83 </xsd:element> |
|
84 <xsd:element name="data"> |
|
85 <xsd:complexType> |
|
86 <xsd:sequence> |
|
87 <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" /> |
|
88 <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" /> |
|
89 </xsd:sequence> |
|
90 <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" /> |
|
91 <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" /> |
|
92 <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" /> |
|
93 <xsd:attribute ref="xml:space" /> |
|
94 </xsd:complexType> |
|
95 </xsd:element> |
|
96 <xsd:element name="resheader"> |
|
97 <xsd:complexType> |
|
98 <xsd:sequence> |
|
99 <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" /> |
|
100 </xsd:sequence> |
|
101 <xsd:attribute name="name" type="xsd:string" use="required" /> |
|
102 </xsd:complexType> |
|
103 </xsd:element> |
|
104 </xsd:choice> |
|
105 </xsd:complexType> |
|
106 </xsd:element> |
|
107 </xsd:schema> |
|
108 <resheader name="resmimetype"> |
|
109 <value>text/microsoft-resx</value> |
|
110 </resheader> |
|
111 <resheader name="version"> |
|
112 <value>2.0</value> |
|
113 </resheader> |
|
114 <resheader name="reader"> |
|
115 <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> |
|
116 </resheader> |
|
117 <resheader name="writer"> |
|
118 <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> |
|
119 </resheader> |
|
120 <data name="CIPDCodeSegAvailability_CodeSegMisMatch_Description_L1" xml:space="preserve"> |
|
121 <value>The code segment: '{0}', for process: '{1}' conflicts with the symbolic information.</value> |
|
122 </data> |
|
123 <data name="CIPDCodeSegAvailability_CodeSegMisMatch_Description_L2" xml:space="preserve"> |
|
124 <value>Crash data indicates that the code segment base address is 0x{0:x8}, however, symbolic information suggests it should be: 0x{1:x8}</value> |
|
125 </data> |
|
126 <data name="CIPDCodeSegAvailability_CodeSegMisMatch_Title" xml:space="preserve"> |
|
127 <value>Code Segment Mismatch</value> |
|
128 </data> |
|
129 <data name="CIPDCodeSegAvailability_NoSymbols_Description" xml:space="preserve"> |
|
130 <value>The code segment: '{0}', for process: '{1}' does not have any associated symbols.</value> |
|
131 </data> |
|
132 <data name="CIPDCodeSegAvailability_NoSymbols_Title" xml:space="preserve"> |
|
133 <value>Symbols Unavailable</value> |
|
134 </data> |
|
135 <data name="CIPDRegAvailability_MissingLR_Description" xml:space="preserve"> |
|
136 <value>{0} the registers do not contain a value for the link register (R14).</value> |
|
137 </data> |
|
138 <data name="CIPDRegAvailability_MissingLR_Title" xml:space="preserve"> |
|
139 <value>Link Register (R14) Not Available</value> |
|
140 </data> |
|
141 <data name="CIPDRegAvailability_MissingPC_Description" xml:space="preserve"> |
|
142 <value>{0} the registers do not contain a value for the program counter (R15).</value> |
|
143 </data> |
|
144 <data name="CIPDRegAvailability_MissingPC_Title" xml:space="preserve"> |
|
145 <value>Program Counter (R15) Not Available</value> |
|
146 </data> |
|
147 <data name="CIPDRegAvailability_MissingSP_Description" xml:space="preserve"> |
|
148 <value>{0} the registers do not contain a value for the current stack pointer (R13).</value> |
|
149 </data> |
|
150 <data name="CIPDRegAvailability_MissingSP_Title" xml:space="preserve"> |
|
151 <value>Stack Pointer (R13) Not Available</value> |
|
152 </data> |
|
153 <data name="CIPDRegAvailability_NoRegsForStack_Description" xml:space="preserve"> |
|
154 <value>{0} the stack has no associated registers which reduces the accuracy of stack decoding.</value> |
|
155 </data> |
|
156 <data name="CIPDRegAvailability_NoRegsForStack_Title" xml:space="preserve"> |
|
157 <value>Registers Missing</value> |
|
158 </data> |
|
159 <data name="CIPDRegAvailability_NullThisPointer_Description" xml:space="preserve"> |
|
160 <value>{0} R00 was null and the thread raised an exception. This suggests a possible de-reference of a NULL 'this' pointer.</value> |
|
161 </data> |
|
162 <data name="CIPDRegAvailability_NullThisPointer_Title" xml:space="preserve"> |
|
163 <value>Possible De-reference of NULL 'this' Pointer?</value> |
|
164 </data> |
|
165 <data name="CIPDStackBoundaryValidator_StackOverflow_Description" xml:space="preserve"> |
|
166 <value>{0} the stack pointer is beyond the start of the stack range, which will result in an exception.</value> |
|
167 </data> |
|
168 <data name="CIPDStackBoundaryValidator_StackOverflow_Title" xml:space="preserve"> |
|
169 <value>Stack Overflow</value> |
|
170 </data> |
|
171 <data name="CIPDStackBoundaryValidator_StackUnderflow_Description" xml:space="preserve"> |
|
172 <value>{0} the stack pointer is outside of the stack address range.</value> |
|
173 </data> |
|
174 <data name="CIPDStackBoundaryValidator_StackUnderflow_Title" xml:space="preserve"> |
|
175 <value>Stack Underflow</value> |
|
176 </data> |
|
177 <data name="CIPDStackRegisterAvailability_MissingRegisters_Description" xml:space="preserve"> |
|
178 <value>{0} no registers are available, which may result in incomplete analysis.</value> |
|
179 </data> |
|
180 <data name="CIPDStackRegisterAvailability_MissingRegisters_Title" xml:space="preserve"> |
|
181 <value>Registers Missing</value> |
|
182 </data> |
|
183 <data name="CIPDStackRegisterAvailability_MissingSP_Description" xml:space="preserve"> |
|
184 <value>{0} stack data has been supplied but the stack pointer value is missing.</value> |
|
185 </data> |
|
186 <data name="CIPDStackRegisterAvailability_MissingSP_Title" xml:space="preserve"> |
|
187 <value>Stack Pointer (R13) Not Available</value> |
|
188 </data> |
|
189 <data name="CIPDThreadValidity_NoStack_Description" xml:space="preserve"> |
|
190 <value>{0} stack data is not available.</value> |
|
191 </data> |
|
192 <data name="CIPDThreadValidity_NoStack_Title" xml:space="preserve"> |
|
193 <value>Stack Data Unavailable</value> |
|
194 </data> |
|
195 <data name="CIProblemDetector_Msg_Stack" xml:space="preserve"> |
|
196 <value>In relation to the {0} mode stack,</value> |
|
197 </data> |
|
198 <data name="CIProblemDetector_Msg_Thread" xml:space="preserve"> |
|
199 <value>In relation to the thread '{0}',</value> |
|
200 </data> |
|
201 <data name="CIStackBuilder_AddressInfoException_BaseAddressBeforeTopAddress" xml:space="preserve"> |
|
202 <value>The stack base address appears to be invalid.</value> |
|
203 </data> |
|
204 <data name="CIStackBuilder_AddressInfoException_PointerMissing" xml:space="preserve"> |
|
205 <value>Unable to reconstruct call stack as no value was supplied for the current stack pointer (R13).</value> |
|
206 </data> |
|
207 <data name="CIStackBuilder_AddressInfoException_PointerOutOfBounds" xml:space="preserve"> |
|
208 <value>The current stack pointer (R13) is outside of the stack address boundary.</value> |
|
209 </data> |
|
210 <data name="CIStackBuilder_AddressInfoException_TopAddressAfterBaseAddress" xml:space="preserve"> |
|
211 <value>The stack top/limiting address appears to be invalid.</value> |
|
212 </data> |
|
213 <data name="CIStackBuilder_Error_Title" xml:space="preserve"> |
|
214 <value>Stack Reconstruction Error</value> |
|
215 </data> |
|
216 <data name="CIStackBuilder_Warning_Title" xml:space="preserve"> |
|
217 <value>Stack Reconstruction Warning</value> |
|
218 </data> |
|
219 <data name="CPIDStackDataValidator_Description" xml:space="preserve"> |
|
220 <value>{0} the stack pointer is outside of the supplied stack data. This may mean that part of the reconstructed call stack is omitted.</value> |
|
221 </data> |
|
222 <data name="CPIDStackDataValidator_Title" xml:space="preserve"> |
|
223 <value>Stack Data Incomplete</value> |
|
224 </data> |
|
225 </root> |