You may have noticed that there is a new feature in RTC 6.0.5 regarding Keyword expansion.
It may only be from the CLI and builds.
Using the server setting “Server Default for Line Delimiter Handling” = NONE and usage limitation and understanding.
Users use a mixture of Windows and Linux platforms so have to manage the line endings carefully.
There is this statement:
"When keyword expansion is enabled for a load operation, all text files (those files whose line delimiter is set to a value other than NONE) are processed for keyword expansion."
1. Why should there be this dependency between Keyword expansion and the line delimiter setting?
When the delimiter is set to NONE, that file could be a binary file which we might not be able to read/modify. Hence those files are not processed for keyword expansion.
2. How is the Keyword expansion enabled for a load operation if it is only used for the CLI and builds?
At load time, the load operation is configured to expand keywords. Once content is loaded with keywords expanded, they will continue to be expanded for that loaded content such that additional accepts will update keywords and the keywords will be updated on check-in as well.
3. Does this mean the Keyword expansion is enabled for a load operation using the Eclipse client?
Currently there is an enhancement request open to support this feature in rich clients as well