[TIMOB-6604] MobileWeb: Build a robust internationalization and locale system
| GitHub Issue | n/a |
|---|
| Type | New Feature |
|---|
| Priority | Low |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-03-08T16:42:26.000+0000 |
|---|
| Affected Version/s | Release 2.0.0 |
|---|
| Fix Version/s | Sprint 2012-05, Release 2.0.0 |
|---|
| Components | MobileWeb |
|---|
| Labels | n/a |
|---|
| Reporter | Chris Barber |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2011-12-13T10:20:32.000+0000 |
|---|
| Updated | 2017-03-04T00:22:00.000+0000 |
|---|
Description
Mobile web needs a newly designed internationalization (i18n) and localization (l10n system. The system needs to be designed so that there's a default implementation in en-US, but then have several subdirectories for each language/locale with specific overrides.
For i18n, these are string tables. This is tied into the Ti.Locale.getString() or L() function.
For l10n, we need modules that describe things such as currency, decimal, and date/time formatting.
When the app launches, it will detect the language and locale, then load the appropriate strings. Language/locale bundles can be lazy loaded.
The build system will need to have support for i18n and l10n bundles. That means that when you do a build, you can specify the supported languages that you want bundled into the build.
Attachments
| File | Date | Size |
|---|
| Archive.zip | 2012-03-08T04:09:04.000+0000 | 3644666 |
Pull request: https://github.com/appcelerator/titanium_mobile/pull/1603
Test with KitchenSink and attached test case.
Closing ticket due to MobileWeb no longer being supported.