Task #11035
Divide supported locales into two categories
| Status: | Closed | Start date: | 2010-11-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 0% |
|
| Category: | I18n | |||
| Target version: | TYPO3 Flow Base Distribution - 1.1 | |||
| Sprint: | Has patch: | No | ||
| PHP Version: | Complexity: |
Description
There should be two types of locales supported by I18n package. One collection of Locale object would represent a group of locales fully supported by the system (e.g. locales for which translation files and other localized resources are available) - as it is now. The other category would consist of all locales supported by CLDR itself. There should be possibility to use functionality based on CLDR data (like number formatting, parsing etc) for locales which does not belong to the first category (the "fully supported" locales).
History
#1 Updated by Karsten Dambekalns about 4 years ago
- Target version set to 1.1
#2 Updated by Karsten Dambekalns over 3 years ago
- Status changed from New to Needs Feedback
- Has patch set to No
What would be the advantage of that distinction?
#3 Updated by Christian Müller over 3 years ago
- Assigned To deleted (
Karol Gusak)
#4 Updated by Karsten Dambekalns about 3 years ago
- Status changed from Needs Feedback to Closed
- Assigned To set to Karsten Dambekalns
Support for using anything the CLDR offers is something different. That distinction seems not useful.