Internationalization and localization - Revision history

Karl Jones: /* JavaScript internationalization API */

2016-11-07T16:58:39Z

‎JavaScript internationalization API

2016-11-04T20:31:02Z

‎Web hosting

2016-11-04T19:59:16Z

‎Web hosting

2016-11-04T16:49:48Z

‎Web hosting

2016-11-04T16:48:16Z

2016-11-02T15:13:05Z

‎See also

2016-11-01T19:52:14Z

‎JavaScript and internationalization

2016-11-01T19:06:00Z

‎External links

2016-11-01T19:00:00Z

‎External links

2016-11-01T18:59:00Z

‎JavaScript and internationalization

@@ Line 45: / Line 45: @@
 === JavaScript internationalization API ===
-* [https://marcoscaceres.github.io/jsi18n/ JavaScript Internationalization API
+* [https://marcoscaceres.github.io/jsi18n/ JavaScript Internationalization API - a simple introduction]
-A simple introduction]
 === Web hosting ===

@@ Line 72: / Line 72: @@
 *** 2. If you are going to be building different divisions of the domain (Chinese, and perhaps later going French, German, etc), consider building out TLD's for each domain that's needed in specific languages and focus on building those separate sites. That way you can focus on content development, social media and marketing efforts specific to each language, thus improving your options for the search in each country.
 * [http://webmasters.stackexchange.com/questions/403/how-should-i-structure-my-urls-for-both-seo-and-localization How should I structure my URLs for both SEO and localization?]
 === Internationalization services ===

@@ Line 71: / Line 71: @@
 *** 1. If you are building a multilingual site, you should also consider how you will be building back-links through various methods (content development, company blog, etc) and will those be done in each language to support the authority needed to build rankings in each language you are working to expand on?
 *** 2. If you are going to be building different divisions of the domain (Chinese, and perhaps later going French, German, etc), consider building out TLD's for each domain that's needed in specific languages and focus on building those separate sites. That way you can focus on content development, social media and marketing efforts specific to each language, thus improving your options for the search in each country.
 === Internationalization services ===

@@ Line 55: / Line 55: @@
 ** Consider cross-linking each language version of a page. That way, a French user who lands on the German version of your page can get to the right language version with a single click.
 ** Avoid automatic redirection based on the user’s perceived language. These redirections could prevent users (and search engines) from viewing all the versions of your site.
 * [https://moz.com/community/q/subdomains-or-subfolders-for-language-specific-sites Subdomains or subfolders for language specific sites?] @ moz.com
 ** Comment 1:
@@ Line 68: / Line 71: @@
 *** 1. If you are building a multilingual site, you should also consider how you will be building back-links through various methods (content development, company blog, etc) and will those be done in each language to support the authority needed to build rankings in each language you are working to expand on?
 *** 2. If you are going to be building different divisions of the domain (Chinese, and perhaps later going French, German, etc), consider building out TLD's for each domain that's needed in specific languages and focus on building those separate sites. That way you can focus on content development, social media and marketing efforts specific to each language, thus improving your options for the search in each country.
 === Internationalization services ===

@@ Line 47: / Line 47: @@
 * [https://marcoscaceres.github.io/jsi18n/ JavaScript Internationalization API
 A simple introduction]
 === Internationalization services ===

@@ Line 13: / Line 13: @@
 * [[Common Locale Data Repository]]
 * [[Computing]]
 * [[Locale]]
 * [[Software]]

@@ Line 29: / Line 29: @@
 * [https://www.npmjs.com/browse/keyword/i18n packages with keyword "i18n"]
 * [https://www.npmjs.com/package/internationalization internationalization]
 * [http://i18next.com/ i18next]
 * [http://airbnb.io/polyglot.js/ Polyglot.js]

@@ Line 23: / Line 23: @@
 * [https://en.wikipedia.org/wiki/Internationalization_and_localization Internationalization and localization] @ Wikipedia
 * [https://www.w3.org/International/questions/qa-accept-lang-locales Accept-Language used for locale setting] @ w3.org
 === JavaScript and internationalization ===

← Older revision		Revision as of 19:00, 1 November 2016
Line 22:		Line 22:

	* [https://en.wikipedia.org/wiki/Internationalization_and_localization Internationalization and localization] @ Wikipedia		* [https://en.wikipedia.org/wiki/Internationalization_and_localization Internationalization and localization] @ Wikipedia
		+	* [https://www.w3.org/International/questions/qa-accept-lang-locales Accept-Language used for locale setting] @ w3.org

	=== JavaScript and internationalization ===		=== JavaScript and internationalization ===

@@ Line 37: / Line 37: @@
 * [https://blog.mozilla.org/webdev/2011/10/06/i18njs-internationalize-your-javascript-with-a-little-help-from-json-and-the-server/ i18njs : Internationalize Your JavaScript With A Little Help From JSON And The Server]
 * [https://rxaviers.github.io/javascript-globalization/  JavaScript Globalization Overview]
 === JavaScript internationalization API ===