>>>>> "GvR" == Guido van Rossum <guido@python.org> writes:
>> The localization context should not (always) be taken from the
>> user environment. In systems like web-based services, the
>> context will instead be relative to the person/entity making
>> the remote request, so we have to be able to explicitly specify
>> the localization context, or at least query, modify, and
>> restore some global context.
GvR> Sure. So the interface may be different. The main argument
GvR> (that you shouldn't be using t.year() to format dates)
GvR> remains the same.
Doesn't Java have separate formatting objects? You decide which
format object you need based on the localication context, then you
pass in the timestamp/date/money/whatever thingie and the format
object knowws how to render that data representation in the
appropriate localization.
makes-sense-to-me-ly y'rs,
-Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4