Static documentation for Font Settings Extension API.

chrome/common/extensions/docs/experimental.fontSettings.html

Index: chrome/common/extensions/docs/experimental.fontSettings.html
diff --git a/chrome/common/extensions/docs/experimental.fontSettings.html b/chrome/common/extensions/docs/experimental.fontSettings.html
index ede5fdbd18e6347e28d91d4068ef142007780a49..b1992cd570d990796194c033a4540c4f93130dfa 100644
--- a/chrome/common/extensions/docs/experimental.fontSettings.html
+++ b/chrome/common/extensions/docs/experimental.fontSettings.html
@@ -191,6 +191,19 @@
         <div id="toc">
           <h2>Contents</h2>
           <ol>
+            <li>
+              <a href="#manifest">Manifest</a>
+              <ol>
+              </ol>
+            </li><li>
+              <a href="#scripts">Generic Font Families and Scripts</a>
+              <ol>
+              </ol>
+            </li><li>
+              <a href="#examples">Examples</a>
+              <ol>
+              </ol>
+            </li>
               <li>
                 <a href="#apiReference">API reference: chrome.experimental.fontSettings</a>
                 <ol>
@@ -238,7 +251,54 @@
           For information on how to use experimental APIs, see the <a href="experimental.html">chrome.experimental.* APIs</a> page.
         </p>
         <!-- STATIC CONTENT PLACEHOLDER -->
-        <div id="static"></div>
+        <div id="static"><!-- BEGIN AUTHORED CONTENT -->
+<p>The Font Settings API allows you to manage Chrome's font settings.</p>
+<h2 id="manifest">Manifest</h2>
+<p>The Font Settings API is currently experimental, so you must declare the
+"experimental" permission to use it. For example:</p>
+<pre>{
+  "name": "My Font Settings Extension",
+  "description": "Customize your fonts",
+  "version": "0.2",
+  "permissions": ["experimental"]
+}</pre>
+<h2 id="scripts">Generic Font Families and Scripts</h2>
+<p>Chrome allows for some font settings to depend on certain generic font
+families and language scripts. For example, the font used for sans-serif
+Simplified Chinese may be different than the font used for serif Japanese.</p>
+<p>The generic font families supported by Chrome are based on
+<a href="http://www.w3.org/TR/CSS21/fonts.html#generic-font-families">CSS generic font families</a>
+and are listed in the API reference below. When a webpage specifies a generic
+font family, Chrome selects the font based on the corresponding setting. If no
+generic font family is specified, Chrome uses the setting for the "standard"
+generic font family.</p>
+<p>When a webpage specifies a language, Chrome selects the font based on the
+setting for the corresponding language script. If no language is specified,
+Chrome uses the setting for the default, or global, script.</p>
+<p>The supported language scripts are based on ISO 15924 script codes and listed
+in the API reference below. Technically, Chrome settings are not strictly
+per-script but also depend on language. For example, Chrome chooses the font for
+Hangul (ISO 15924 script code "Hang") when a webpage specifies Korean language,
+and uses this font not just for Hangul script but for everything the font
+covers, such as Hanja.</p>
+<h2 id="examples">Examples</h2>
+<p>The following code gets the standard font for Arabic.</p>
+<pre>chrome.experimental.fontSettings.getFontName(
+  { genericFamily: 'standard', script: 'Arab' },
+  function(details) { console.log(details.fontName); }
+);
+</pre>
+<p>The next snippet sets the sans-serif font for Japanese.</p>
+<pre>chrome.experimental.fontSettings.setFontName(
+  { genericFamily: 'sansserif', script: 'Hrkt', fontName: 'IPAPGothic' }

[jungshik at Google, 2012/03/28 20:09:45]

This is not a documentation issue but the API implementation issue. In Webkit,
we'd have used 'Japn' if ICU on earlier version of Mac OS has 'Japn' script
available. Using 'Hrkt' for Japanese may not be very user-friendly (well, not
many extensions will be written with this api so that it may not matter
terribly). 

Still, Japn would be better. For now, how about explaining a bit as to why Hrkt
is used here for Japanese?

Later, we may want to change the API to translate Japn to Hrkt before talking to
WebCore. That way, we expose a more user-friendly 'Japn' to extension writers
without changing WebCore. 

The same can be said of Kore vs Hang. However, Hang is  almost as good a Kore so
that we can leave that alone. 

[falken, 2012/03/29 06:58:22]

Thanks, good idea. I added a little explanation to the previous section about
language scripts.

+);
+</pre>
+<p>You can find a sample extension using the Font Settings API in the
+<a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/api/fontSettings/">examples/api/fontSettings</a>
+directory. For other examples and for help in viewing the source code, see
+<a href="samples.html">Samples</a>.</p>
+<!-- END AUTHORED CONTENT -->
+</div>
         <!-- API PAGE -->
         <div class="apiPage">
         <a name="apiReference"></a>