CURR11 — Clarify contradiction betw setFormatByLocale & setFormattingString

Summary: It appears that setFormatByLocale() and setFormattingString() override each
other, but the supporting text for each does not support this conclusion.
If setFormatByLocale() is executed, and then a call to
getFormattingString() is executed, a format specification for the given
locale should be returned correct? If a call to setFormattingString() is
then executed (which would change the format specification for the given
state identifier from the locale based specification previously),
getFormattingString() then returns the format specification just assigned
correct? The supporting text needs to address this behavior.

resolved by Currency 2 RTF