FairCom RTG BTRV User Guide

<normalize>

The <normalize> configuration option normalizes file paths passed to FairCom RTG. This option is global-only, and can only be set only as a child of <config>. It is invalid if specified as child of <*instance> or <file>. When this option is used, the file path gets normalized before any file configuration matching.

The <normalize> option may contain the following sub-options (see links for examples):

<sep>

Specifies the path separator, such as a forward slash (/) or backslash (\).

<drive>

Specifies a drive letter to be used if the path to be normalized does not include a drive letter.

If a drive letter is already included in the path, it is not replaced with the one specified by <drive>. Also, <drive> applies only to full file paths, not relative ones. The following attributes can modify these behaviors:

• <drive force> - If the file path to be normalized already includes a drive letter, then setting <drive force="yes"> will force it to change the drive to the one specified. Defaults to "no".
• <drive relative> - Setting <drive relative="yes"> will cause the drive letter to be added to relative file paths as well, not just full file paths. Defaults to "no".

<relative>

Specifies if the relative file paths will be normalized to always begin with a "./" or ".\". Defaults to "no", meaning nothing is automatically added to the start of relative file paths.

<trim>

If "yes", all specified leading and trailing characters are automatically trimmed from the file paths. Defaults to "no". When "yes", then by default, all whitespace characters will be trimmed. This can be customized using the following attribute:

• <trim set> - Customizes which character types will be trimmed. Defaults to <trim set=" \t\n\r\f\v">, which trims the following list of whitespace character types:
  • (' ') - Space
  • '\t' - Tab
  • '\n' - Newline
  • '\r' - Carriage return
  • '\f' - Formfeed
  • '\v' - Vertical tab

In This Section <sep> <drive> <relative> <trim>