Update in LocalizationExample

src/extensions/samples/LocalizationExample/README.md

@@ -48,17 +48,19 @@ Move this plugin to the extensions\user\ folder to run the plugin. It will add a
 
 * main.js – loads the Strings module for the plugin and uses mustache to localize html content
 
+* package.json - add the translation languages as in the example: `"i18n: ["en", "fr" ]`
+
 * strings.js – uses i18n to load a strings.js file in the nls folder
 
 * htmlContent
     * htmlfragment.html – html template to be localized by mustache
-    * nls
-        * strings.js – configures i18n by specifying the root folder  and listing the locales supported by the plugin
-        * root
-		    * strings.js – contains the English strings
-	    * fr
-		    * strings.js – contains the French strings
-	    * etc. for each locale
+* nls
+    * strings.js – configures i18n by specifying the  root folder and listing the locales supported by the plugin
+    * root
+        * strings.js – contains the English strings
+    * fr
+        * strings.js – contains the French strings
+    * etc. for each locale
 
 #### Strings for plugins vs Brackets
 Note that there is a distinction between loading strings for a plugin vs. strings in the Brackets core. To access strings local to your plugin use `var strings = require("strings")`. To load the core Brackets strings use `var bracketsStrings = brackets.getModule("strings")`

src/extensions/samples/LocalizationExample/package.json

@@ -0,0 +1,16 @@
+{
+    "name": "localization-example",
+    "title": "Localization Example",
+    "description": "A guide on how to localize your extension.",
+    "homepage": "https://github.com/adobe/brackets/tree/master/src/extensions/samples/LocalizationExample",
+    "version": "1.0.0",
+    "author": "The Brackets team",
+    "license": "MIT",
+    "engines": {
+        "brackets": ">=0.42.0"
+    },
+    "i18n": [
+        "en", 
+        "fr" 
+    ]
+}