Merge "docs: Replacing curly apostrophes with straight ones" into nyc-docs

camera application that checks to see if device hardware supports those features and fails

gracefully if a feature is not available.</p>

<p>You can check the availabilty of camera features by getting an instance of a camera’s parameters

<p>You can check the availabilty of camera features by getting an instance of a camera's parameters

object, and checking the relevant methods. The following code sample shows you how to obtain a

{@link android.hardware.Camera.Parameters} object and check if the camera supports the autofocus

feature:</p>

<p>This technique works for nearly all camera features, and most parameters can be changed at any

time after you have obtained an instance of the {@link android.hardware.Camera} object. Changes to

parameters are typically visible to the user immediately in the application’s camera preview.

parameters are typically visible to the user immediately in the application's camera preview.

On the software side, parameter changes may take several frames to actually take effect as the

camera hardware processes the new instructions and then sends updated image data.</p>

</pre>

<p>The {@link android.hardware.Camera.Area} object contains two data parameters: A {@link

android.graphics.Rect} object for specifying an area within the camera’s field of view and a weight

android.graphics.Rect} object for specifying an area within the camera's field of view and a weight

value, which tells the camera what level of importance this area should be given in light metering

or focus calculations.</p>

}

</pre>

<p>After creating this class, you then set it into your application’s

<p>After creating this class, you then set it into your application's

{@link android.hardware.Camera} object, as shown in the example code below:</p>

<pre>

<p class="note"><strong>Note:</strong> Remember to call this method <em>after</em> calling

{@link android.hardware.Camera#startPreview startPreview()}. Do not attempt to start face detection

in the {@link android.app.Activity#onCreate onCreate()} method of your camera app’s main activity,

in the {@link android.app.Activity#onCreate onCreate()} method of your camera app's main activity,

as the preview is not available by this point in your application's the execution.</p>

{@code android:focusable}</a> attribute is set to {@code true}. This setting allows users to focus

on the element using the directional controls and then interact with it. The user interface controls

provided by the Android framework are focusable by default and visually indicate focus by changing

the control’s appearance.</p>

the control's appearance.</p>

<p>Android provides several APIs that let you control whether a user interface control is focusable

and even request that a control be given focus:</p>

<h3 id="populate-events">Populating accessibility events</h3>

<p>Each {@link android.view.accessibility.AccessibilityEvent} has a set of required properties that

describe the current state of the view. These properties include things such as the view’s class

describe the current state of the view. These properties include things such as the view's class

name, content description and checked state. The specific properties required for each event type

are described in the {@link android.view.accessibility.AccessibilityEvent} reference documentation.

The {@link android.view.View} implementation provides default values for these properties. Many of

</service>

</pre>

<p>This meta-data element refers to an XML file that you create in your application’s resource

<p>This meta-data element refers to an XML file that you create in your application's resource

directory ({@code <project_dir>/res/xml/accessibility_service_config.xml}). The following code

shows example contents for the service configuration file:</p>

accessibility services to provide more useful feedback to users.</p>

<p>An accessibility service gets information about an user interface event through an {@link

android.view.accessibility.AccessibilityEvent} passed by the system to the service’s

android.view.accessibility.AccessibilityEvent} passed by the system to the service's

{@link android.accessibilityservice.AccessibilityService#onAccessibilityEvent

onAccessibilityEvent()} callback method. This object provides details about the event, including the

type of object being acted upon, its descriptive text and other details. Starting in Android 4.0

  of a user. This feature, added in Android 4.1 (API Level 16), and requires that your

  accessibility service request activation of the Explore by Touch feature. Your service can

  request this activation by setting the

  {@link android.accessibilityservice.AccessibilityServiceInfo#flags flags} member of the service’s

  {@link android.accessibilityservice.AccessibilityServiceInfo#flags flags} member of the service's

  {@link android.accessibilityservice.AccessibilityServiceInfo} instance to

  {@link android.accessibilityservice.AccessibilityServiceInfo#FLAG_REQUEST_TOUCH_EXPLORATION_MODE},

  as shown in the following example.

    <a href="http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html">

      <h4>Say Goodbye to the Menu Button</h4>

      <p>As Ice Cream Sandwich rolls out to more devices, it’s important that you begin to migrate

      <p>As Ice Cream Sandwich rolls out to more devices, it's important that you begin to migrate

your designs to the action bar in order to promote a consistent Android user experience.</p> </a>

    <a href="http://android-developers.blogspot.com/2011/11/new-layout-widgets-space-and-gridlayout.html">

    <a href="http://android-developers.blogspot.com/2011/08/horizontal-view-swiping-with-viewpager.html">

      <h4>Horizontal View Swiping with ViewPager</h4>

      <p>Whether you have just started out in Android app development or are a veteran of the craft,

it probably won’t be too long before you’ll need to implement horizontally scrolling sets of views.

it probably won't be too long before you'll need to implement horizontally scrolling sets of views.

</p> </a>

  </div>

<p>The Android framework includes a variety of {@link android.preference.Preference} subclasses that

allow you to build a UI for several different types of settings.

However, you might discover a setting you need for which there’s no built-in solution, such as a

number picker or date picker. In such a case, you’ll need to create a custom preference by extending

However, you might discover a setting you need for which there's no built-in solution, such as a

number picker or date picker. In such a case, you'll need to create a custom preference by extending

the {@link android.preference.Preference} class or one of the other subclasses.</p>

<p>When you extend the {@link android.preference.Preference} class, there are a few important