Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: Release 3.4.0
-
Component/s: Alloy, Content Assist
-
Labels:
-
Story Points:13
-
Sprint:2014 Sprint 16 Studio, 2014 Sprint 17 Studio
Description
We should allow a user to select a string and extract ti out to i18n XML files in their titanium projects, much like the Eclipse PDE support for extracting strings in Java files.
Attachments
Issue Links
- relates to
-
TISTUD-6692 Add hyperlink detector to jump from i18n translation keys in Alloy View XML attributes to their definition in strings.xml files
-
- Closed
-
-
TISTUD-6693 Add hyperlink detector to jump from string keys in i18n files to usage in view files
-
- Closed
-
-
TISTUD-6834 Add F3 command to jump from string keys in i18n files to usage
-
- Closed
-
-
TISTUD-6835 Add F3 command to jump from i18n translation keys in Alloy view XML to definition in strings.xml file
-
- Closed
-
-
TISTUD-6836 Index translation key references in TSS files
-
- Closed
-
-
TISTUD-6837 Index translation key references in Titanium Mobile JS files
-
- Closed
-
-
TISTUD-6838 Add hyperlink detector to jump from i18n translation keys in JS code to definition in strings.xml file
-
- Closed
-
-
TISTUD-6839 Add hyperlink detector to jump from i18n translation keys in TSS code to definition in strings.xml file
-
- Closed
-
-
TISTUD-6840 Add F3 command to jump from i18n translation keys in TSS code to definition in strings.xml file
-
- Closed
-
-
TISTUD-6841 Add F3 command to jump from i18n translation keys in JS code to definition in strings.xml file
-
- Closed
-
-
TISTUD-6847 Support detection of i18n translation keys in Alloy View XML text nodes and id attributes
-
- Closed
-
-
ALOY-1067 Support L() in XML as Label text
-
- Closed
-
-
TISTUD-6694 content assist to suggest strings inside L() calls in Alloy view XML from the available keys in i18n files
-
- Closed
-