{
"id": "99984",
"key": "ALOY-208",
"fields": {
"issuetype": {
"id": "7",
"description": "gh.issue.story.desc",
"name": "Story",
"subtask": false
},
"project": {
"id": "11113",
"key": "ALOY",
"name": "Alloy",
"projectCategory": {
"id": "10400",
"description": "Tools for developing applications",
"name": "Tooling"
}
},
"fixVersions": [
{
"id": "14131",
"description": "",
"name": "2012 Sprint 18",
"archived": true,
"released": true,
"releaseDate": "2012-09-10"
},
{
"id": "14176",
"description": "Release 3.0.0",
"name": "Release 3.0.0",
"archived": false,
"released": true,
"releaseDate": "2012-12-13"
}
],
"resolution": {
"id": "1",
"description": "A fix for this issue is checked into the tree and tested.",
"name": "Fixed"
},
"resolutiondate": "2012-08-29T04:22:32.000+0000",
"created": "2012-08-28T06:58:45.000+0000",
"priority": {
"name": "Medium",
"id": "3"
},
"labels": [],
"versions": [
{
"id": "14131",
"description": "",
"name": "2012 Sprint 18",
"archived": true,
"released": true,
"releaseDate": "2012-09-10"
}
],
"issuelinks": [],
"assignee": null,
"updated": "2018-03-07T22:25:56.000+0000",
"status": {
"description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.",
"name": "Resolved",
"id": "5",
"statusCategory": {
"id": 3,
"key": "done",
"colorName": "green",
"name": "Done"
}
},
"components": [
{
"id": "12326",
"name": "XML",
"description": "View XML and parsing"
}
],
"description": "Apps are localized via the {{i18n}} directory: https://wiki.appcelerator.org/display/guidesSnapshot25Oct2011v2/Internationalizing+your+Application\r\n\r\nWe need to determine how we will handle this in alloy. Possibilities:\r\n\r\n# Just drop it in the {{assets}} and/or {{lib}} directory. Confusing, but will work.\r\n# Put it in the top-level app directory like this: {{/app/i18n}}\r\n\r\nI 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.",
"attachment": [],
"flagged": false,
"summary": "Handle i18n localization folder",
"creator": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"subtasks": [],
"reporter": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"environment": null,
"comment": {
"comments": [
{
"id": "216688",
"author": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"body": "Russ to talk to Gabe and Docs to get this resolved.",
"updateAuthor": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"created": "2012-08-28T19:55:17.000+0000",
"updated": "2012-08-28T19:55:17.000+0000"
},
{
"id": "216719",
"author": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"body": "Actually, in retrospect, we probably don't need to do much of anything here. The {{i18n}} directory exists at the project root, outside of {{Resources}} or {{app}}, just like plugins and modules. Localization can continue to work the same way.",
"updateAuthor": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"created": "2012-08-29T04:22:02.000+0000",
"updated": "2012-08-29T04:22:02.000+0000"
},
{
"id": "312860",
"author": {
"name": "yairp",
"key": "yairp",
"displayName": "Yair",
"active": true,
"timeZone": "America/Guatemala"
},
"body": "Tony, I think you're missing a major gap here.\r\n\r\nThe logical place to use i18n strings is in the alloy xml file\r\n\r\nbut these do not work\r\n\r\n\r\n\r\nSo how can the developer use the i18n strings?\r\nIn tss file? it is awkward\r\nIn controller JS code? the whole purpose of ALLOY is to make things simpler.\r\n\r\nSo I believe that a complete solution to parse the xml files and extract the i18n is needed.",
"updateAuthor": {
"name": "yairp",
"key": "yairp",
"displayName": "Yair",
"active": true,
"timeZone": "America/Guatemala"
},
"created": "2014-07-08T17:31:52.000+0000",
"updated": "2014-07-08T17:31:52.000+0000"
}
],
"maxResults": 3,
"total": 3,
"startAt": 0
}
}
}