« Hide

Steps to reproduce:
1. create a new project
2. create a folder on the same level as src called locale, and inside of that folder a folder called en_US and inside of that a file called general.properties
3. export a release build and enable view source, including the locale directory and its children
 
 Actual Results:
 the general.properties file and its folder structure is visible in the view source but when you select general.properties it displays a message saying Page not found.
 
 Expected Results:
 Clicking on the .properties file would show the contents of the .properties file.
 
 Workaround (if any):
 There is no workaround that I am aware of.

This is the method of localization (structure and naming conventions) that is described in documentation and other localization standards and so should be an expected user behavior. This is obviously not a show stopping issue but is disappointing as it would be a nice feature for a localization team as well as QA and bug fixers.
 
 

Show »

Steps to reproduce: 1. create a new project 2. create a folder on the same level as src called locale, and inside of that folder a folder called en_US and inside of that a file called general.properties 3. export a release build and enable view source, including the locale directory and its children    Actual Results:  the general.properties file and its folder structure is visible in the view source but when you select general.properties it displays a message saying Page not found.    Expected Results:  Clicking on the .properties file would show the contents of the .properties file.    Workaround (if any):  There is no workaround that I am aware of. This is the method of localization (structure and naming conventions) that is described in documentation and other localization standards and so should be an expected user behavior. This is obviously not a show stopping issue but is disappointing as it would be a nice feature for a localization team as well as QA and bug fixers.