VBLM's string exclusion list file options, set on the SX window, control SXL file format and usage. SXL files, which prevent the extraction of strings that should not be translated, are discussed in detail in the SXL overview.
File Format
SXL files can be stored in either text or binary format. Binary (the default) is faster, but there may be occasions when text will be helpful See SXL File Format for more info.
Use Without Asking
When commanded to extract strings, VBLM first looks in the project directory for an SXL file (ProjectName.sxl). If this box is checked, VBLM will use the file without asking. If not checked (the default), VBLM asks if you want to use it.
An SXL file stores a lot of info about the parent VB project -- for each excluded string, it records the file, the line number, the line of code, and the position of the string in the line. This info will often become obsolete (especially the line number). Thus whenever VBLM loads an SXL file (either to use it during string extraction, or to add to it after the LTE closes) it does a date check to test for this possibility. If the SXL file is older than the source files, VBLM consults this setting. If not checked (the default) VBLM will ask before verifying the information and updating it if necessary. If checked, it does this without asking. This is an option because the verify/update process can be lengthy on a large project, and if you know that it's unnecessary, why bother? Also, see below.
When this box is checked (the default), VBLM excludes strings only when everything matches, including the line number. When not checked, VBLM will exclude strings if the file, line of code, and string position in the line of code match, even if the line number does not. With this "loose" application, a) a single exclusion will exclude all instances in a file where the line of code matches, and b) an SXL file with obsolete line number info will still work. Thus if you skip verification & updating, you may want to uncheck this.
See Also