[ALOY-208] Handle i18n localization folder
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-08-29T04:22:32.000+0000 |
| Affected Version/s | 2012 Sprint 18 |
| Fix Version/s | 2012 Sprint 18, Release 3.0.0 |
| Components | XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-08-28T06:58:45.000+0000 |
| Updated | 2018-03-07T22:25:56.000+0000 |
Description
Apps are localized via the Just drop it in the
Put it in the top-level app directory like this:
I like option #2 personally as I think having localization visible at the top-level is a good thing. It makes it clear to the developer to expect that localization will be present in the project.
i18n directory: https://wiki.appcelerator.org/display/guidesSnapshot25Oct2011v2/Internationalizing+your+Application
We need to determine how we will handle this in alloy. Possibilities:
Russ to talk to Gabe and Docs to get this resolved.
Actually, in retrospect, we probably don't need to do much of anything here. The
i18ndirectory exists at the project root, outside ofResourcesorapp, just like plugins and modules. Localization can continue to work the same way.Tony, I think you're missing a major gap here. The logical place to use i18n strings is in the alloy xml file but these do not work So how can the developer use the i18n strings? In tss file? it is awkward In controller JS code? the whole purpose of ALLOY is to make things simpler. So I believe that a complete solution to parse the xml files and extract the i18n is needed.