RFC: Remove localization from format!

[alexcrichton]

No description provided.

[alexcrichton]

cc rust-lang/rust#12553

[lilyball]

FWIW we could make # work without escaping today, at the "top level", and only require escaping inside a {} specifier.

[bstrie]

The problem with escaping { in format strings bit me just the other day, so that change would be welcome.

What support would the compiler or stdlib need to provide in order to someday support localization in an external library? I'm completely unfamiliar with the needs of localization (as we all are, it seems). Would be nice to have a domain expert weigh in. Can we borrow one from Mozilla?

[alexcrichton]

@brson, @aturon, and I talked with a domain expert at Mozilla, and the conclusion was to basically implement the ECMA 402 spec as well as l20n in a library. The major conclusion from the discussions we had was that no language support was needed, but rather it only all needed to be in a library.

[brson]

Based on my understanding, the word 'internationalization' in this RFC should be changed to 'localization'. Localization is the process of supplying alternate translations, whereas internationalization is doing automatic format conversion for standard types like dates.

[alexcrichton]

Indeed, updated with internationalization => localization

[brson]

Accepted per https://github.com/mozilla/rust/wiki/Meeting-weekly-2014-06-10.

[jibal]

Based on my understanding, the word 'internationalization' in this RFC should be changed to 'localization'. Localization is the process of supplying alternate translations, whereas internationalization is doing automatic format conversion for standard types like dates.

This is not correct. See http://www.ecma-international.org/ecma-402/1.0/#sec-4.1