Remove .html extension from links

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

 <!--
 [NOTEs for editors:
  * Try to be consistent about string vs. message (it's probably not yet).
 -->
 
 <p>
 You need to put all of its user-visible strings into a file
-named <a href="i18n-messages.html"><code>messages.json</code></a>.
+named <a href="i18n-messages"><code>messages.json</code></a>.
 Each time you add a new locale,
 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="{{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.'
+ alt='In the extension directory: manifest.json, *, *.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>
 
@@ skipping 16 matching lines @@
 (note that it still has only English strings):
 </p>
 
 <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>
+the <a href="manifest">manifest</a>
 <b>must</b> define "default_locale".
 </p>
 
 <p>
 Some notes about internationalizing:
 </p>
 
 <ul>
   <li><p>
     You can use any of the <a href="#overview-locales">supported locales</a>.
@@ skipping 48 matching lines @@
 {
   "search_string": {
     "message": "hello%20world",
     "description": "The string we search for. Put %20 between words that go together."
   },
   ...
 }</pre>
 
 <p>
 For more information, see
-<a href="i18n-messages.html">Formats: Locale-Specific Messages</a>.
+<a href="i18n-messages">Formats: Locale-Specific Messages</a>.
 </p>
   </li>
 </ul>
 
 <p>
 Once an extension or app is internationalized,
 translating it is simple.
 You copy <code>messages.json</code>,
 translate it,
 and put the copy into a new directory under <code>_locales</code>.
@@ skipping 12 matching lines @@
 <h2 id="overview-predefined">Predefined messages</h2>
 
 <p>
 The internationalization system provides a few predefined
 messages to help you localize.
 These include <code>@@ui_locale</code>,
 so you can detect the current UI locale,
 and a few <code>@@bidi_...</code> messages
 that let you detect the text direction.
 The latter messages have similar names to constants in the
-<a href="http://code.google.com/apis/gadgets/docs/i18n.html#BIDI">
+<a href="http://code.google.com/apis/gadgets/docs/i18n#BIDI">
 gadgets BIDI (bi-directional) API</a>.
 </p>
 
 <p>
 The special message <code>@@extension_id</code>
 can be used in the CSS and JavaScript files,
 whether or not the extension or app is localized.
 This message doesn't work in manifest files.
 </p>
 
@@ skipping 101 matching lines @@
 including some (such as <code>en</code>)
 that let a single translation support multiple variations of a language
 (such as <code>en_GB</code> and <code>en_US</code>).
 </p>
 
 
 <h3 id="locales-supported">Supported locales</h3>
 
 <p>
 You can use any of the
-<a href="http://code.google.com/chrome/webstore/docs/i18n.html#localeTable">locales that the Chrome Web Store supports</a>.
+<a href="http://code.google.com/chrome/webstore/docs/i18n#localeTable">locales that the Chrome Web Store supports</a>.
 </p>
 
 
 <h3 id="locales-usage">Searching for messages</h3>
 
 <p>
 You don't have to define every string for every supported locale.
 As long as the default locale's <code>messages.json</code> file
 has a value for every string,
 your extension or app will run no matter how sparse a translation is.
@@ skipping 182 matching lines @@
 
 <h2 id="overview-examples">Examples</h2>
 
 <p>
 You can find simple examples of internationalization in the
 <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/api/i18n/">examples/api/i18n</a>
 directory.
 For a complete example, see
 <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/news/">examples/extensions/news</a>.
 For other examples and for help in viewing the source code, see
-<a href="samples.html">Samples</a>.
+<a href="samples">Samples</a>.
 </p>
 
 
 <h3 id="examples-getMessage">Examples: getMessage</h3>
 
 <!--
 [PENDING: improve this section. it should probably start with a
 one-variable example that includes the messages.json code.]
 -->
 
@@ skipping 27 matching lines @@
     "details": {
       "content": "$1",
       "example": "Failed to fetch RSS feed."
     }
   }
 }
 </pre>
 
 <p>
 For more information about placeholders, see the
-<a href="i18n-messages.html">Locale-Specific Messages</a> page.
+<a href="i18n-messages">Locale-Specific Messages</a> page.
 For details on calling <code>getMessage()</code>, see the
 $(ref:i18n.getMessage API reference).
 </p>
 
 <h3 id="example-accept-languages">Example: getAcceptLanguages</h3>
 <p>
 The following code gets accept-languages from the browser and displays them as a
 string by separating each accept-language with ','.
 </p>
 
 <pre>
 function getAcceptLanguages() {
   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
 $(ref:i18n.getAcceptLanguages API reference).
 </p>