Closed Bug 181520 Opened 22 years ago Closed 7 years ago

Convert locale names from nsString to nsCString

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: smontagu, Assigned: smontagu)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [bcp47])

By specification in RFC 3066, locale names can only contain ASCII characters (in fact only a subset of ASCII), so representing them with an nsString is unnecessary.
Blocks: 181515
Status: NEW → ASSIGNED
nsACString, please, as long as you're doing this... ;) nsAFlatCString if absolutely necessary.
Yes, of course, nsACString for the interfaces and nsCString for the member data. That's what I meant ;-)
QA Contact: amyy → i18n
Depends on: 660584
Just make sure this is compliant with BCP 47.
Blocks: bcp47
OS: Windows 2000 → All
Hardware: x86 → All
Whiteboard: [bcp47]
Yes it is. As far as I remember, it is part of the stability policy for BCP 47 that the character repertoire for language subtags will never be extended beyond US-ASCII, but I can't find a reference for this right now. At any rate, it is still the case in the current version.
Depends on: 711893
The new LocaleService uses nsCString everywhere. I think this bug is fixed.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.