Doc change: Add docs for licensing service.

Change-Id: Ia78467b8857cb8e83ab3920f4126bc7985a9d93d

docs/html/guide/guide_toc.cs

@@ -371,6 +371,9 @@
             <span class="zh-CN" style="display:none">应用程序版本控制</span>
             <span class="zh-TW" style="display:none">應用程式版本設定</span>
           </a></li>
+      <li><a href="<?cs var:toroot ?>guide/publishing/licensing.html">
+            <span class="en">Licensing Your Applications</span>
+          </a> <span class="new">new!</span></li>
       <li><a href="<?cs var:toroot ?>guide/publishing/preparing.html">
             <span class="en">Preparing to Publish</span>
             <span class="de" style="display:none">Vorbereitung auf die Veröffentlichung</span>

docs/html/guide/publishing/preparing.jd

@@ -39,13 +39,14 @@ Applications</a> document. </p>
 <ol>
 <li>Test your application extensively on an actual device </li>
 <li>Consider adding an End User License Agreement in your application</li>
+<li>Consider adding licensing support</li>
 <li>Specify an icon and label in the application's manifest</li>
 <li>Turn off logging and debugging and clean up data/files</li>
 </ol>
 
 <p>Before you do the final compile of your application:</p>
 
-<ol start="5">
+<ol start="6">
 <li>Version your application</li>
 <li>Obtain a suitable cryptographic key</li>
 <li>Register for a Maps API Key, if your application is using MapView elements</li>
@@ -53,7 +54,7 @@ Applications</a> document. </p>
 
 <p><em>Compile your application...</em></p>
 <p>After compiling your application:</p>
-<ol start="8">
+<ol start="9">
 <li>Sign your application</li>
 <li>Test your compiled application</li>
 </ol>
@@ -101,7 +102,19 @@ application</h3>
 <p>To protect your person, organization, and intellectual property, you may want
 to provide an End User License Agreement (EULA) with your application. 
 
-<h3 id="iconlabel">3. Specify an icon and label in the application's manifest</h3>
+<h3 id="eula">3. Consider adding support for Android Market Licensing</h3>
+
+<p>If you are publishing a paid application through Android Market, consider
+adding support for Android Market Licensing. Licensing lets you control access
+to your application based on whether the current user has purchased it.
+Using Android Market Licensing is optional. 
+
+<p>For complete information about Android Market Licensing Service and how to
+use it in your application, see <a
+href="{@docRoot}guide/publishing/licensing.html">Licensing Your
+Applications</a>.</p>
+
+<h3 id="iconlabel">4. Specify an icon and label in the application's manifest</h3>
 
 <p>The icon and label that you specify in an application's manifest are
 important because they are displayed to users as your application's icon and
@@ -116,7 +129,7 @@ display the icon and label to users. </p>
 <p>As regards the design of your icon, you should try to make it match as much
 as possible the style used by the built-in Android applications.</p>
 
-<h3 id="logging">4. Turn off logging and debugging and clean up data/files</h3>
+<h3 id="logging">5. Turn off logging and debugging and clean up data/files</h3>
 
 <p>For release, you should make sure that debug facilities are turned off and
 that debug and other unnecessary data/files are removed from your application
@@ -133,7 +146,7 @@ code.</li>
 
 <h2 id="finalcompile">Before you do the final compile of your application</h2>
 
-<h3 id="versionapp">5. Version your application</h3>
+<h3 id="versionapp">6. Version your application</h3>
 
 <p>Before you compile your application, you must make sure that you have defined
 a version number for your application, specifying an appropriate value for both
@@ -152,7 +165,7 @@ element in the application's manifest file, using appropriate values. </p>
 application, see <a href="{@docRoot}guide/publishing/versioning.html">Versioning 
 Your Applications</a>.</p>
 
-<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h3>
+<h3 id="cryptokey">7. Obtain a suitable cryptographic key</h3>
 
 <p>If you have read and followed all of the preparation steps up to this point,
 your application is compiled and ready for signing. Inside the .apk, the
@@ -173,7 +186,7 @@ elements.</li>
 <li>Sign your application for release, later in the preparation process</li>
 </ul>
 
-<h3 id="mapsApiKey">7. Register for a Maps API Key, if your application is using
+<h3 id="mapsApiKey">8. Register for a Maps API Key, if your application is using
 MapView elements</h3>
 
 <div class="sidebox-wrapper">
@@ -231,7 +244,7 @@ you can compile your application for release.</p>
 
 <h2 id="post-compile">After compiling your application</h2>
 
-<h3 id="signapp">8. Sign your application</h3>
+<h3 id="signapp">9. Sign your application</h3>
 
 <p>Sign your application using your private key and then
 align it with the {@code zipalign} tool. Signing your application
@@ -239,7 +252,7 @@ correctly is critically important. Please see
 <a href="{@docRoot}guide/publishing/app-signing.html">Signing Your 
 Applications</a> for complete information. </p>
 
-<h3 id="testapp">9. Test your compiled and signed application</h3>
+<h3 id="testapp">10. Test your compiled and signed application</h3>
 
 <p>Before you release your compiled application, you should thoroughly test it
 on the target mobile device (and target network, if possible). In particular,

docs/html/guide/publishing/publishing.jd

@@ -18,7 +18,8 @@ page.title=Publishing Your Applications
 <ol>
 <li><a href="#overview">Publishing on Android Market</a>
     <ol>
-    <li><a href="#marketupgrade">Publishing Updates on Android Market</a>
+    <li><a href="#marketupgrade">Publishing Updates on Android Market</a></li>
+    <li><a href="#marketLicensing">Using Android Market Licensing Service</a></li>
     <li><a href="#marketintent">Using Intents to Launch the Market Application</a></li>
     </ol></li>
 <!--
@@ -30,6 +31,7 @@ page.title=Publishing Your Applications
 <h2>See also</h2>
 
 <ol>
+<li><a href="{@docRoot}guide/publishing/licensing.html">Licensing Your Applications</a></li>
 <li><a href="{@docRoot}guide/publishing/preparing.html">Preparing to Publish</a></li>
 </ol>
 
@@ -59,7 +61,7 @@ the .apk. Your application is now ready for publishing. </p>
 <p>The sections below provide information about publishing your Android
 application to mobile device users.</p>
 
-<h2 id="market">Publishing on Android Market</h2>
+<h2 id="overview">Publishing on Android Market</h2>
 
 <p>Android Market is a hosted service that makes it easy for users to find and
 download Android applications to their Android-powered devices, and makes it 
@@ -121,7 +123,26 @@ certificate do <em>not</em> match those of the existing version, Market will
 consider it a new application and will not offer it to users as an update.</p>
 
 
+<h3 id="marketLicensing">Using Android Market Licensing Service</h3>
 
+<p>Android Market offers a licensing service that lets you enforce licensing
+policies for paid applications that you publish through Android Market. With
+Android Market Licensing, your applications can query Android Market at run time
+to obtain their licensing status for the current user, then allow or disallow
+further use as appropriate. Using the service, you can apply a flexible
+licensing policy on an application-by-application basis &mdash; each 
+application can enforce its licensing status in the way most appropriate
+for it. </p>
+
+<p>Any application that you publish through Android Market can use the Android
+Market Licensing Service. The service uses no dedicated framework APIs, you can
+add licensing to any legacy application that uses a minimum API level of 3 or
+higher.</p>
+
+<p>For complete information about Android Market Licensing Service and how to
+use it in your application, see <a
+href="{@docRoot}guide/publishing/licensing.html">Licensing Your
+Applications</a>.</p>
 
 
 <h3 id="marketintent">Using Intents to Launch the Market Application on 

docs/html/resources/faq/commontasks.jd

@@ -158,7 +158,7 @@ It is not necessary to put external JARs in the assets folder.
 <ul>
     <li>Create an {@link android.app.Dialog app.Dialog} class </li>
     <li>Create an {@link android.app.AlertDialog app.AlertDialog} class </li>
-    <li>Set the {@link android.R.style#Theme_Dialog} <em>theme</em> attribute to <code>&#064;android:style/Theme.Dialog</code>
+    <li>Set the {@link android.R.style#Theme_Dialog} <em>theme</em> attribute to <code>&#64;android:style/Theme.Dialog</code>
         in your AndroidManifest.xml file. For example:    
     <pre>&lt;activity class=&quot;AddRssItem&quot; android:label=&quot;Add an item&quot; android:theme=&quot;&#064;android:style/Theme.Dialog&quot;/&gt;</pre></li>
 </ul>