![]() |
Scan Rule of Windows Forms |
Use this dialog to edit a scan rule of Windows Forms form resources.
Enter the type name of the component where the property belongs. Enter this value only if the property is component-specific. If you want to scan all the same name properties no matter the component's type, leave this value empty. The value can contain wild cards (* and ?). If the property rule is a rule of a component, this edit is hidden.
Note! When specifying a scan property, you must include the full namespace of the component type. So instead of "Label" enter "System.Windows.Forms.Label".
Enter the name of the property. You must enter a value. The value can contain wild cards (* and ?).
Specifies if the property is localized or not. Possible values are:
| Exclude | Properties matching this rule are not localized. |
| Localize | Properties matching this rule are localized. |
| Hide | Properties matching this rule are scanned but hidden. |
Select the type of property. Possible values are
| Value | Property type | Description |
|---|---|---|
| Default | any | Soluling detects the property value and uses an appropriate parser to scan it. |
| Image list (binary) | binary | Property has an image list data. |
| Expression string | string | Property has a string that contains a structured text that is scanned using a regular expression set. When selected, the dialog shows an edit box where you can enter the expression. You can also test the expression. |
| XML string | string | Property has a string that contains XML data. Some 3rd party components have special properties that contain multiple values in a single property by storing the data in XML. Most often, this XML contains only a few elements that should be localized, and all others must be left intact. This is why you can add selection items that specify what elements of the XML are localized. When selected, the dialog shows a selection list edit where you can edit the selection list. |
| JSON string | string | Property has a string that contains JSON data. Some 3rd party components have special properties that contain multiple values in a single property by storing the data in JSON. Most often, this JSON contains only a few elements that should be localized, and all others must be left intact. This is why you can add selection items that specify what elements of the JSON are localized. When selected, the dialog shows a selection list edit where you can edit the selection list. |
| HTML string | string | Property has a string that contains HTML data. |
| ComponentOne column info string | string | Property has a string that contains structured text similar to the Column info property of ComponentOne's Flex Grid component (online help). The format is such a complex and proprietary format that cannot be scanned using a standard parser such as a regular expression parser.
This is why we have implemented a dedicated parser for this property. The following line contains a sample value. 4,1,0,0,0,95,Columns:1{Caption:"One";} 2{Caption:"Two";} 3{Caption:"Three";} As you can see, only the strings following "Caption:" should be localized, and all others must be left intact. Our parser safely extracts only the strings. |
| DevExpress LookUpEdit column string | string | DevExpress LookUpEdit stores captions and ids in the same collection. If you select this type, our parser can skip the id strings and extracts only the caption strings. |
If you don't know the format, leave it to default. If the property you want to scan is so complex that default does not work and you can not use either expression or XML format, contact us to check if we can implement a dedicated parser for that property.
If the above format is set either to XML or JSON, specify here the items you want to localize.