From d26b319fd6f98517cc3421f10bf18698b953e4d2 Mon Sep 17 00:00:00 2001 From: Ruben Rodriguez Date: Thu, 13 Sep 2018 20:39:48 -0400 Subject: Updated extensions list for v60 --- .../node_modules/pathfinder/docs/l10n.md | 41 ---------------------- 1 file changed, 41 deletions(-) delete mode 100644 data/extensions/jid1-KtlZuoiikVfFew@jetpack/node_modules/pathfinder/docs/l10n.md (limited to 'data/extensions/jid1-KtlZuoiikVfFew@jetpack/node_modules/pathfinder/docs/l10n.md') diff --git a/data/extensions/jid1-KtlZuoiikVfFew@jetpack/node_modules/pathfinder/docs/l10n.md b/data/extensions/jid1-KtlZuoiikVfFew@jetpack/node_modules/pathfinder/docs/l10n.md deleted file mode 100644 index 2207d16..0000000 --- a/data/extensions/jid1-KtlZuoiikVfFew@jetpack/node_modules/pathfinder/docs/l10n.md +++ /dev/null @@ -1,41 +0,0 @@ - - -The `l10n` module allows one to localize their Jetpack. - -## Example ## - - var _ = require("l10n").l10n({ - filename: "text.properties", - baseURL: require("self").data.url("locale") - }); - console.log(_("hello.world")); - - -@function - Creates and returns a function which can be used to access translations by - key. - - Translations should be grouped together in a folder which contains a folder - for each locale being supported whose name is the locale being supported - (examples: "en", "en-US", "ja", "ja-JP"). Inside each locale's folder should - be a `.properties` file with a name that is the same for every locale. Here - is a example of how you might organize things: - - - data/ - - locale/ - - en/ - - text.properties - - ja/ - - text.properties - -@param options {object} - - -@prop filename {string} - The name of the file storing the translations. -@prop baseURL {string} - The url to the folder containing the locale folders. -@prop [defaultLocale] {string} - Defines the locale to use when you don't have translations for the user's - locale. The default is `"en"`. - -- cgit v1.2.3