Issue 2410: Clarify contradiction betw setFormatByLocale & setFormattingString Clarify exceptions for setFormattingString in MoneyFormatter (currency-rtf) Source: (, ) Nature: Revision Severity: Summary: 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. Resolution: resolved by Currency 2 RTF Revised Text: Resolution: Add text to clarify that setting the format by locale will in effect change the formatting string and retrieving the formatting string will return the default locale format. Revised Text: Add this final sentence to the first paragraph of section 2.3.12.3 FormatterSpecification Operations after the setFormatByLocal() method. The default locale format for a given locale can be returned as a wstring by a subsequent call to getFormattingString(in long stateIdentifier). Actions taken: January 11, 1999: received issue May 4, 2000: closed issue Discussion: End of Annotations:===== Return-Path: From: Robert_Mickley@CYBORG.COM X-Lotus-FromDomain: CYBORG@CYBORG_NET To: issues@omg.org cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM Date: Mon, 11 Jan 1999 21:28:52 -0700 Subject: Currency RTF Issues Content-Disposition: inline Today is the deadline for comments for the Currency RTF. Below is an itemized list of additions to that list. Issue Title: Clarify the implied contradiction between setFormatByLocale and setFormattingString Issue Type: Text Revision Issue Description: 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.