Extensions Docs Server: Doc conversion script - SVN

chrome/common/extensions/docs/server2/templates/intros/i18n.html

-<div id="pageData-name" class="pageData">Internationalization (i18n)</div>
-
 <!--
 [NOTEs for editors:
  * Try to be consistent about string vs. message (it's probably not yet).
 -->
 
-<!-- BEGIN AUTHORED CONTENT -->
+
 <p id="classSummary">
 An <em>internationalized</em> extension
 can be easily
 <em>localized</em> &mdash;
 adapted to languages and regions
 that it didn't originally support.
 </p>
 
 <p>
 To internationalize your extension,
 you need to put all of its user-visible strings into a file
 named <a href="i18n-messages.html"><code>messages.json</code></a>.
 Each time you localize your extension
 you add a messages file
 under a directory
 named <code>_locales/<em>localeCode</em></code>,
 where <em>localeCode</em> is a code such as
 <code>en</code> for English.
 </p>
 
 <p>
 Here's the file hierarchy
 for an internationalized extension that supports
 English (<code>en</code>),
 Spanish (<code>es</code>), and
 Korean (<code>ko</code>):
 </p>
 
-<img src="../images/i18n-hierarchy.gif"
+<img src="{{static}}/images/i18n-hierarchy.gif"
  alt='In the extension directory: manifest.json, *.html, *.js, _locales directory. In the _locales directory: en, es, and ko directories, each with a messages.json file.'
  width="385" height="77" />
 
 
 <h2 id="l10">How to support multiple languages</h2>
 
 <p>
 Say you have an extension
 with the files shown in the following figure:
 </p>
 
-<img src="../images/i18n-before.gif"
+<img src="{{static}}/images/i18n-before.gif"
  alt='A manifest.json file and a file with JavaScript. The .json file has "name": "Hello World". The JavaScript file has title = "Hello World";'
  width="323" height="148">
 
 <p>
 To internationalize this extension,
 you name each user-visible string
 and put it into a messages file.
 The extension's manifest,
 CSS files,
 and JavaScript code
 use each string's name to get its localized version.
 </p>
 
 <p>
 Here's what the extension looks like when it's internationalized
 (note that it still has only English strings):
 </p>
 
-<img src="../images/i18n-after-1.gif"
+<img src="{{static}}/images/i18n-after-1.gif"
  alt='In the manifest.json file, "Hello World" has been changed to "__MSG_extName__", and a new "default_locale" item has the value "en". In the JavaScript file, "Hello World" has been changed to chrome.i18n.getMessage("extName"). A new file named _locales/en/messages.json defines "extName".'
  width="782" height="228">
 
 <p class="note">
 <b>Important:</b>
 If an extension has a <code>_locales</code> directory,
 the <a href="manifest.html">manifest</a>
 <b>must</b> define "default_locale".
 </p>
 
@@ skipping 73 matching lines @@
 You copy <code>messages.json</code>,
 translate it,
 and put the copy into a new directory under <code>_locales</code>.
 For example, to support Spanish,
 just put a translated copy of <code>messages.json</code>
 under <code>_locales/es</code>.
 The following figure shows the previous extension
 with a new Spanish translation.
 </p>
 
-<img src="../images/i18n-after-2.gif"
+<img src="{{static}}/images/i18n-after-2.gif"
  alt='This looks the same as the previous figure, but with a new file at _locales/es/messages.json that contains a Spanish translation of the messages.'
  width="782" height="358">
 
 
 <h2 id="overview-predefined">Predefined messages</h2>
 
 <p>
 The internationalization system provides a few predefined
 messages to help you localize your extension.
 These include <code>@@ui_locale</code>,
@@ skipping 176 matching lines @@
 but "extName" is in only two of the locales.
 Wherever a user running Google Chrome in US English sees the label "Colors",
 a user of British English sees "Colours".
 Both US English and British English users
 see the extension name "Hello World".
 Because the default language is Spanish,
 users running Google Chrome in any non-English language
 see the label "Colores" and the extension name "Hola mundo".
 </p>
 
-<img src="../images/i18n-strings.gif"
+<img src="{{static}}/images/i18n-strings.gif"
  alt='Four files: manifest.json and three messages.json files (for es, en, and en_GB).  The es and en files show entries for messages named "extName" and "colores"; the en_GB file has just one entry (for "colores").'
  width="493" height="488" />
 
 <h3 id="locales-testing">How to set your browser's locale</h3>
 
 <p>
 To test translations, you might want to set your browser's locale.
 This section tells you how to set the locale in
 <a href="#testing-win">Windows</a>,
 <a href="#testing-mac">Mac OS X</a>, and
@@ skipping 194 matching lines @@
   chrome.i18n.getAcceptLanguages(function(languageList) {
     var languages = languageList.join(",");
     document.getElementById("languageSpan").innerHTML = languages;
   })
 }
 </pre>
 
 <p>
 For details on calling <code>getAcceptLanguages()</code>, see the
 <a href="#method-getAcceptLanguages">API reference</a>.
-</p>
-
-<!-- END AUTHORED CONTENT -->
+</p>