PATENT DOCUMENT

Publication Number: US-10101822-B2
Application Number: US-201514844829-A
Country: US
Kind Code: B2

Title: Language input correction

Abstract:
The present disclosure generally relates to language input correction. In one example process, a sequence of contact inputs can be detected via a keyboard interface on a touch-sensitive display. A contact input of the sequence of contact inputs can include a contact motion from a first position to a second position of the keyboard interface. A plurality of candidate words corresponding to the sequence of contact inputs can be determined. The plurality of candidate words can be ranked based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface. A portion of the plurality of candidate words can be displayed for user selection.

Claims:
What is claimed is: 
     
       1. A method for inputting language, the method comprising:
 at a device having one or more processors, memory, and a touch-sensitive display:
 detecting a sequence of contact inputs via a keyboard interface on the touch-sensitive display, wherein detecting a contact input of the sequence of contact inputs comprises detecting an initiation of contact with the touch-sensitive display at a first position of the keyboard interface, a continuous contact motion from the first position to a second position of the keyboard interface, and a release of contact from the touch-sensitive display at the second position, and wherein the contact input represents a user selection of at most one character key of the keyboard interface; 
 determining a plurality of candidate words corresponding to the sequence of contact inputs; 
 ranking the plurality of candidate words based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface; and 
 displaying a portion of the plurality of candidate words for user selection. 
 
 
     
     
       2. The method of  claim 1 , wherein the first key corresponds to a first writing symbol of a language and the second key corresponds to a second writing symbol of the language. 
     
     
       3. The method of  claim 1 , wherein the plurality of candidate words includes words of a first writing system and words of a second writing system. 
     
     
       4. The method of  claim 1 , further comprising:
 determining a plurality of character strings that potentially correspond to the sequence of contact inputs; and 
 determining, using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact inputs, wherein the plurality of candidate words is determined from the plurality of character strings based on the probability of each character string of the plurality of character strings given the sequence of contact inputs. 
 
     
     
       5. The method of  claim 1 , wherein the plurality of candidate words are determined based on a lexicon of a language model. 
     
     
       6. The method of  claim 1 , wherein:
 the probability that the contact input is an intended input to select the first key of the keyboard interface is determined based on a distance between the first position and a center position of the first key; and 
 the probability that the contact input is an intended input to select the second key of the keyboard interface is determined based on a distance between the first position and a center position of the second key. 
 
     
     
       7. The method of  claim 1 , further comprising:
 determining a probability of each candidate word given the sequence of contact inputs, wherein ranking the plurality of candidate words is based on the probability of each candidate word given the sequence of contact inputs. 
 
     
     
       8. The method of  claim 7 , wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on a probability of a respective character string of the plurality of character strings given the sequence of contact inputs. 
     
     
       9. The method of  claim 7 , further comprising:
 determining a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
 
     
     
       10. The method of  claim 9 , wherein the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings is determined using one or more language models. 
     
     
       11. The method of  claim 1 , wherein the plurality of candidate words is determined using a lexicon with a trie data structure. 
     
     
       12. The method of  claim 1 , wherein the plurality of candidate words is ranked based on a distance between the first position and a center position of each key on the keyboard interface. 
     
     
       13. The method of  claim 1 , wherein the plurality of candidate words is ranked based on a distance between the first position and the second position of the contact motion. 
     
     
       14. The method of  claim 1 , wherein the plurality of candidate words is ranked based on a speed of the contact motion from the first position and the second position. 
     
     
       15. The method of  claim 1 , wherein the plurality of candidate words is ranked based on an angle of the contact motion with respect to a reference axis of the keyboard interface. 
     
     
       16. The method of  claim 1 , wherein the keyboard interface is a 10-key kana keyboard interface. 
     
     
       17. The method of  claim 1 , wherein at a first time prior to detecting the contact input, the first key is displayed on the touch-sensitive display without displaying the second key, and wherein the second key is displayed at a second time while detecting the contact motion. 
     
     
       18. The method of  claim 1 , wherein the probability that the contact input is an intended input to select the second key of the keyboard interface increases as a distance between the first position and a center position of the first key decreases and as a distance between the first position and the second position of the contact motion increases. 
     
     
       19. The method of  claim 1 , further comprising:
 determining, based on a distance of the contact motion from the first position to the second position, the probability that the contact input is an intended input to select the first key of the keyboard interface and the probability that the contact input is an intended input to select the second key of the keyboard interface. 
 
     
     
       20. The method of  claim 19 , wherein, as the distance of the contact motion from the first position to the second position increases, the probability that the contact input is an intended input to select the first key of the keyboard interface decreases and the probability that the contact input is an intended input to select the second key of the keyboard interface increases. 
     
     
       21. A non-transitory computer-readable storage medium comprising computer-executable instructions, which when executed by one or more processors, cause the one or more processors to:
 detect a sequence of contact inputs via a keyboard interface on the touch-sensitive display, wherein detecting a contact input of the sequence of contact inputs comprises detecting an initiation of contact with the touch-sensitive display at a first position of the keyboard interface, a continuous contact motion from the first position to a second position of the keyboard interface, and a release of contact from the touch-sensitive display at the second position, and wherein the contact input represents a user selection of at most one character key of the keyboard interface; 
 determine a plurality of candidate words corresponding to the sequence of contact inputs; 
 rank the plurality of candidate words based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface; and 
 display a portion of the plurality of candidate words for user selection. 
 
     
     
       22. The computer-readable storage medium of  claim 21 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a plurality of character strings that potentially correspond to the sequence of contact inputs; and 
 determine, using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact inputs, wherein the plurality of candidate words is determined from the plurality of character strings based on the probability of each character string of the plurality of character strings given the sequence of contact inputs. 
 
     
     
       23. The computer-readable storage medium of  claim 21 , wherein:
 the probability that the contact input is an intended input to select the first key of the keyboard interface is determined based on a distance between the first position and a center position of the first key; and 
 the probability that the contact input is an intended input to select the second key of the keyboard interface is determined based on a distance between the first position and a center position of the second key. 
 
     
     
       24. The computer-readable storage medium of  claim 21 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a probability of each candidate word given the sequence of contact inputs, wherein ranking the plurality of candidate words is based on the probability of each candidate word given the sequence of contact inputs. 
 
     
     
       25. The computer-readable storage medium of  claim 24 , wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on a probability of a respective character string of the plurality of character strings given the sequence of contact inputs. 
     
     
       26. The computer-readable storage medium of  claim 24 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
 
     
     
       27. The computer-readable storage medium of  claim 21 , wherein the probability that the contact input is an intended input to select the second key of the keyboard interface increases as a distance between the first position and a center position of the first key decreases and as a distance between the first position and the second position of the contact motion increases. 
     
     
       28. The computer-readable storage medium of  claim 21 , wherein the computer-readable instructions further cause the one or more processors to:
 determine, based on a distance of the contact motion from the first position to the second position, the probability that the contact input is an intended input to select the first key of the keyboard interface and the probability that the contact input is an intended input to select the second key of the keyboard interface. 
 
     
     
       29. The computer-readable storage medium of  claim 28 , wherein, as the distance of the contact motion from the first position to the second position increases, the probability that the contact input is an intended input to select the first key of the keyboard interface decreases and the probability that the contact input is an intended input to select the second key of the keyboard interface increases. 
     
     
       30. A system comprising:
 one or more processors; and 
 memory storing computer-readable instructions, which when executed by the one or more processors, cause the one or more processors to:
 detect a sequence of contact inputs via a keyboard interface on the touch-sensitive display, wherein detecting a contact input of the sequence of contact inputs comprises detecting an initiation of contact with the touch-sensitive display at a first position of the keyboard interface, a continuous contact motion from the first position to a second position of the keyboard interface, and a release of contact from the touch-sensitive display at the second position, and wherein the contact input represents a user selection of at most one character key of the keyboard interface; 
 determine a plurality of candidate words corresponding to the sequence of contact inputs; 
 rank the plurality of candidate words based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface; and 
 display a portion of the plurality of candidate words for user selection. 
 
 
     
     
       31. The system of  claim 30 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a plurality of character strings that potentially correspond to the sequence of contact inputs; and 
 determine, using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact inputs, wherein the plurality of candidate words is determined from the plurality of character strings based on the probability of each character string of the plurality of character strings given the sequence of contact inputs. 
 
     
     
       32. The system of  claim 30 , wherein:
 the probability that the contact input is an intended input to select the first key of the keyboard interface is determined based on a distance between the first position and a center position of the first key; and 
 the probability that the contact input is an intended input to select the second key of the keyboard interface is determined based on a distance between the first position and a center position of the second key. 
 
     
     
       33. The system of  claim 30 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a probability of each candidate word given the sequence of contact inputs, wherein ranking the plurality of candidate words is based on the probability of each candidate word given the sequence of contact inputs. 
 
     
     
       34. The system of  claim 33 , wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on a probability of a respective character string of the plurality of character strings given the sequence of contact inputs. 
     
     
       35. The system of  claim 33 , wherein the computer-readable instructions further cause the one or more processors to:
 determine a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, wherein the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
 
     
     
       36. The system of  claim 30 , wherein the probability that the contact input is an intended input to select the second key of the keyboard interface increases as a distance between the first position and a center position of the first key decreases and as a distance between the first position and the second position of the contact motion increases. 
     
     
       37. The system of  claim 30 , wherein the computer-readable instructions further cause the one or more processors to:
 determine, based on a distance of the contact motion from the first position to the second position, the probability that the contact input is an intended input to select the first key of the keyboard interface and the probability that the contact input is an intended input to select the second key of the keyboard interface. 
 
     
     
       38. The system of  claim 37 , wherein, as the distance of the contact motion from the first position to the second position increases, the probability that the contact input is an intended input to select the first key of the keyboard interface decreases and the probability that the contact input is an intended input to select the second key of the keyboard interface increases.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims priority from U.S. Provisional Ser. No. 62/171,911, filed on Jun. 5, 2015, entitled LANGUAGE INPUT CORRECTION, which is hereby incorporated by reference in its entirety for all purposes. 
    
    
     FIELD 
     The present disclosure relates generally to language input, and more specifically to techniques for language input correction. 
     BACKGROUND 
     Various keyboard interfaces can be provided to enable users to enter text or other content elements into application documents, such as word processing documents, messages, or emails. For example, in touch-interface mobile devices, a keyboard interface can be displayed via a touch-sensitive display. User touch inputs can be processed to determine which keys were intended to be inputted by the user and corresponding characters associated with the intended keys can be displayed in a text field. 
     Due to physical limitations (e.g., size) of keyboard interfaces on mobile devices, touch inputs from a user can be determined to correspond to keys that the user did not intend to input. This can bring about significant inaccuracy and inefficiency when inputting text. Further, for languages that rely on converting phonetic-based inputs (e.g., Chinese pinyin, Japanese hiragana, etc.) into predicted candidate text (e.g., Chinese characters, Japanese words, etc.), errors in text input can result in the generation of a large number of irrelevant candidates. This can significantly compromise user experience and productivity. 
     BRIEF SUMMARY 
     Systems and processes for language input correction are provided. In one example process, a sequence of contact inputs can be detected via a keyboard interface on a touch-sensitive display. A contact input of the sequence of contact inputs can include a contact motion from a first position to a second position of the keyboard interface. A plurality of candidate words corresponding to the sequence of contact inputs can be determined. The plurality of candidate words can be ranked based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface. A portion of the plurality of candidate words can be displayed for user selection. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG. 1A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. 
         FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. 
         FIG. 2  illustrates a portable multifunction device having a touch screen in accordance with some embodiments. 
         FIG. 3  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. 
         FIG. 4A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG. 4B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG. 5A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG. 5B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIGS. 6A-C  are screenshots of an electronic device illustrating an exemplary reduced keyboard interface in accordance with some embodiments. 
         FIG. 7  is a flow diagram illustrating an exemplary process for language input correction in accordance with some embodiments. 
         FIGS. 8A-D  are exemplary screenshots of an electronic device illustrating various stages of an exemplary process for language input correction in accordance with some embodiments. 
         FIG. 9  is a functional block diagram illustrating an exemplary electronic device in accordance with some embodiments. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments. 
     The present disclosure generally relates to systems and processes for language input correction. In an exemplary process, a sequence of contact inputs can be detected via a keyboard interface on a touch-sensitive display. A contact input of the sequence of contact inputs can include a contact motion from a first position to a second position of the keyboard interface. A plurality of candidate words corresponding to the sequence of contact inputs can be determined. The plurality of candidate words can be ranked based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface. A portion of the plurality of candidate words can be displayed for user selection. By considering more than one key of the keyboard interface as the intended input of the contact input, the process can determine and display candidate words that more accurately reflect the user&#39;s intent. Further, the process can correct for unintended contact inputs (e.g., typos) by considering other possible intended keys, thereby increasing the relevancy of displayed candidate words. This can improve the accuracy and productivity for inputting text. 
     Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch. 
     The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. 
     The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. 
     The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application. 
     The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user. 
     1. Exemplary Devices for Performing Language Input Correction 
     Attention is now directed toward embodiments of portable devices with touch-sensitive displays.  FIG. 1A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive display system  112  in accordance with some embodiments. Touch-sensitive display  112  is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device  100  includes memory  102  (which optionally includes one or more computer-readable storage mediums), memory controller  122 , one or more processing units (CPUs)  120 , peripherals interface  118 , RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , input/output (I/O) subsystem  106 , other input control devices  116 , and external port  124 . Device  100  optionally includes one or more optical sensors  164 . Device  100  optionally includes one or more contact intensity sensors  165  for detecting intensity of contacts on device  100  (e.g., a touch-sensitive surface such as touch-sensitive display system  112  of device  100 ). Device  100  optionally includes one or more tactile output generators  167  for generating tactile outputs on device  100  (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system  112  of device  100  or touchpad  355  of device  300 ). These components optionally communicate over one or more communication buses or signal lines  103 . 
     As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  100  is only one example of a portable multifunction device, and that device  100  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG. 1A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  102  may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. The computer-readable storage medium may store instructions for performing process  700 , described below. Memory  102  may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller  122  may control access to memory  102  by other components of device  100 . 
     Peripherals interface  118  can be used to couple input and output peripherals of the device to CPU  120  and memory  102 . The one or more processors  120  run or execute various software programs and/or sets of instructions stored in memory  102  to perform various functions for device  100  and to process data. In some embodiments, peripherals interface  118 , CPU  120 , and memory controller  122  may be implemented on a single chip, such as chip  104 . In some other embodiments, they may be implemented on separate chips. 
     RF (radio frequency) circuitry  108  receives and sends RF signals, also called electromagnetic signals. RF circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  108  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  108  optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data may be retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG. 2 ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input control devices  116 . The other input control devices  116  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG. 2 ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG. 2 ). 
     A quick press of the push button may disengage a lock of touch screen  112  or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) may turn power to device  100  on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  112 . In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen  112  and display controller  156  may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif. 
     A touch-sensitive display in some embodiments of touch screen  112  may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  112  displays visual output from device  100 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  112  may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  112  may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  may also include one or more optical sensors  164 .  FIG. 1A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical sensor  164  may capture still images or video. In some embodiments, an optical sensor is located on the back of device  100 , opposite touch screen display  112  on the front of the device so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image may be obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  164  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  164  may be used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG. 1A  shows a contact intensity sensor coupled to intensity sensor controller  159  in I/O subsystem  106 . Contact intensity sensor  165  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  165  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ). In some embodiments, at least one contact intensity sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  may also include one or more proximity sensors  166 .  FIG. 1A  shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  may be coupled to input controller  160  in L/O subsystem  106 . Proximity sensor  166  may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen  112  when the multifunction device is placed near the user&#39;s ear (e.g., when the user is making a phone call). 
     Device  100  optionally also includes one or more tactile output generators  167 .  FIG. 1A  shows a tactile output generator coupled to haptic feedback controller  161  in I/O subsystem  106 . Tactile output generator  167  optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  165  receives tactile feedback generation instructions from haptic feedback module  133  and generates tactile outputs on device  100  that are capable of being sensed by a user of device  100 . In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device  100 ) or laterally (e.g., back and forth in the same plane as a surface of device  100 ). In some embodiments, at least one tactile output generator sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  may also include one or more accelerometers  168 .  FIG. 1A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  may be coupled to an input controller  160  in I/O subsystem  106 . Accelerometer  168  may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  100  optionally includes, in addition to accelerometer(s)  168 , a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) stores device/global internal state  157 , as shown in  FIGS. 1A and 3 . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  126  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/motion module  130  optionally detects contact with touch screen  112  (in conjunction with display controller  156 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  130  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  130  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some embodiments, contact/motion module  130  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  100 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  130  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which may be a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , IM  141 , browser  147 , and any other application that needs text input). For example, text input module  134  can include instructions for providing keyboard interface  800  describe below with reference to  FIGS. 8A-8D . Additionally, text input module  134  can include instructions for performing process  700 , described below. In particular, text input module  134  can include one or more geometry models and one or more language models, described below, for language input correction. 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  138  for use in location-based dialing; to camera  143  as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Applications  136  may include the following modules (or sets of instructions), or a subset or superset thereof:
         Contacts module  137  (sometimes called an address book or contact list);   Telephone module  138 ;   Video conference module  139 ;   E-mail client module  140 ;   Instant messaging (IM) module  141 ;   Workout support module  142 ;   Camera module  143  for still and/or video images;   Image management module  144 ;   Video player module;   Music player module;   Browser module  147 ;   Calendar module  148 ;   Widget modules  149 , which may include one or more of: weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , dictionary widget  149 - 5 , and other widgets obtained by the user, as well as user-created widgets  149 - 6 ;   Widget creator module  150  for making user-created widgets  149 - 6 ;   Search module  151 ;   Video and music player module  152 , which merges video player module and music player module;   Notes module  153 ;   Map module  154 ; and/or   Online video module  155 .       

     Examples of other applications  136  that may be stored in memory  102  include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , contacts module  137  may be used to manage an address book or contact list (e.g., stored in application internal state  192  of contacts module  137  in memory  102  or memory  370 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  138 , video conference module  139 , e-mail  140 , or IM  141 ; and so forth. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , telephone module  138  may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module  137 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , optical sensor  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , text input module  134 , contacts module  137 , and telephone module  138 , video conference module  139  includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , e-mail client module  140  includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module  144 , e-mail client module  140  makes it very easy to create and send e-mails with still or video images taken with camera module  143 . 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , the instant messaging module  141  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 . GPS module  135 , map module  154 , and music player module, workout support module  142  includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 
     In conjunction with touch screen  112 , display controller  156 , optical sensor(s)  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , and image management module  144 , camera module  143  includes executable instructions to capture still images or video (including a video stream) and store them into memory  102 , modify characteristics of a still image or video, or delete a still image or video from memory  102 . 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and camera module  143 , image management module  144  includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , browser module  147  includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , e-mail client module  140 , and browser module  147 , calendar module  148  includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , widget modules  149  are mini-applications that may be downloaded and used by a user (e.g., weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , and dictionary widget  149 - 5 ) or created by the user (e.g., user-created widget  149 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , the widget creator module  150  may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , search module  151  includes executable instructions to search for text, music, sound, image, video, and/or other files in memory  102  that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , and browser module  147 , video and music player module  152  includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen  112  or on an external, connected display via external port  124 ). In some embodiments, device  100  optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , notes module  153  includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , and browser module  147 , map module  154  may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , text input module  134 , e-mail client module  140 , and browser module  147 , online video module  155  includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port  124 ), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module  141 , rather than e-mail client module  140 , is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 
     Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module  152 ,  FIG. 1A ). In some embodiments, memory  102  may store a subset of the modules and data structures identified above. Furthermore, memory  102  may store additional modules and data structures not described above. 
     In some embodiments, device  100  is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  100 , the number of physical input control devices (such as push buttons, dials, and the like) on device  100  may be reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  100  to a main, home, or root menu from any user interface that is displayed on device  100 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) includes event sorter  170  (e.g., in operating system  126 ) and a respective application  136 - 1  (e.g., any of the aforementioned applications  137 - 151 ,  155 ,  380 - 390 ). 
     Event sorter  170  receives event information and determines the application  136 - 1  and application view  191  of application  136 - 1  to which to deliver the event information. Event sorter  170  includes event monitor  171  and event dispatcher module  174 . In some embodiments, application  136 - 1  includes application internal state  192 , which indicates the current application view(s) displayed on touch-sensitive display  112  when the application is active or executing. In some embodiments, device/global internal state  157  is used by event sorter  170  to determine which application(s) is (are) currently active, and application internal state  192  is used by event sorter  170  to determine application views  191  to which to deliver event information. 
     In some embodiments, application internal state  192  includes additional information, such as one or more of: resume information to be used when application  136 - 1  resumes execution, user interface state information that indicates information being displayed or that is ready for display by application  136 - 1 , a state queue for enabling the user to go back to a prior state or view of application  136 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  171  receives event information from peripherals interface  118 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  112 , as part of a multi-touch gesture). Peripherals interface  118  transmits information it receives from I/O subsystem  106  or a sensor, such as proximity sensor  166 , accelerometer(s)  168 , and/or microphone  113  (through audio circuitry  110 ). Information that peripherals interface  118  receives from I/O subsystem  106  includes information from touch-sensitive display  112  or a touch-sensitive surface. 
     In some embodiments, event monitor  171  sends requests to the peripherals interface  118  at predetermined intervals. In response, peripherals interface  118  transmits event information. In other embodiments, peripherals interface  118  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of event recognizers  180 . In other embodiments, one or more of event recognizers  180  are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  may utilize or call data updater  176 , object updater  177 , or GUI updater  178  to update the application internal state  192 . Alternatively, one or more of the application views  191  include one or more respective event handlers  190 . Also, in some embodiments, one or more of data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective event recognizer  180  receives event information (e.g., event data  179 ) from event sorter  170  and identifies an event from the event information. Event recognizer  180  includes event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which may include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event  1  ( 187 - 1 ), event  2  ( 187 - 2 ), and others. In some embodiments, sub-events in an event ( 187 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event  1  ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event  2  ( 187 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  112 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event definition  187  includes a definition of an event for a respective user-interface object. In some embodiments, event comparator  184  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 187 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  188  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module. In some embodiments, object updater  177  creates and updates objects used in application  136 - 1 . For example, object updater  177  creates a new user-interface object or updates the position of a user-interface object. GUI updater  178  updates the GUI. For example, GUI updater  178  prepares display information and sends it to graphics module  132  for display on a touch-sensitive display. 
     In some embodiments, event handler(s)  190  includes or has access to data updater  176 , object updater  177 , and GUI updater  178 . In some embodiments, data updater  176 , object updater  177 , and GUI updater  178  are included in a single module of a respective application  136 - 1  or application view  191 . In other embodiments, they are included in two or more software modules. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  100  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG. 2  illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  may also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  may be used to navigate to any application  136  in a set of applications that may be executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In some embodiments, device  100  includes touch screen  112 , menu button  204 , push button  206  for powering the device on/off and locking the device, volume adjustment button(s)  208 , subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       FIG. 3  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device  300  need not be portable. In some embodiments, device  300  is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device  300  typically includes one or more processing units (CPUs)  310 , one or more network or other communications interfaces  360 , memory  370 , and one or more communication buses  320  for interconnecting these components. Communication buses  320  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  300  includes input/output (I/O) interface  330  comprising display  340 , which is typically a touch screen display. I/O interface  330  also optionally includes a keyboard and/or mouse (or other pointing device)  350  and touchpad  355 , tactile output generator  357  for generating tactile outputs on device  300  (e.g., similar to tactile output generator(s)  167  described above with reference to  FIG. 1A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG. 1A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 . In some embodiments, memory  370  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  102  of portable multifunction device  100  ( FIG. 1A ), or a subset thereof. Furthermore, memory  370  optionally stores additional programs, modules, and data structures not present in memory  102  of portable multifunction device  100 . For example, memory  370  of device  300  optionally stores drawing module  380 , presentation module  382 , word processing module  384 , website creation module  386 , disk authoring module  388 , and/or spreadsheet module  390 , while memory  102  of portable multifunction device  100  ( FIG. 1A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG. 3  may be stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory  370  may store a subset of the modules and data structures identified above. Furthermore, memory  370  may store additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device  100 . 
       FIG. 4A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces may be implemented on device  300 . In some embodiments, user interface  400  includes the following elements, or a subset or superset thereof:
         Signal strength indicator(s)  402  for wireless communication(s), such as cellular and Wi-Fi signals;   Time  404 ;   Bluetooth indicator  405 ;   Battery status indicator  406 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Messages;”   Icon  426  for calendar module  148 , labeled “Calendar;”   Icon  428  for image management module  144 , labeled “Photos;”   Icon  430  for camera module  143 , labeled “Camera;”   Icon  432  for online video module  155 , labeled “Online Video;”   Icon  434  for stocks widget  149 - 2 , labeled “Stocks;”   Icon  436  for map module  154 , labeled “Maps;”   Icon  438  for weather widget  149 - 1 , labeled “Weather;”   Icon  440  for alarm clock widget  149 - 4 , labeled “Clock;”   Icon  442  for workout support module  142 , labeled “Workout Support;”   Icon  444  for notes module  153 , labeled “Notes;” and   Icon  446  for a settings application or module, labeled “Settings,” which provides access to settings for device  100  and its various applications  136 .   
               

     It should be noted that the icon labels illustrated in  FIG. 4A  are merely exemplary. For example, icon  422  for video and music player module  152  may optionally be labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG. 4B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG. 3 ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG. 3 ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  357 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  359  for generating tactile outputs for a user of device  300 . 
     Although some of the examples which follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG. 4B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) has a primary axis (e.g.,  452  in  FIG. 4B ) that corresponds to a primary axis (e.g.,  453  in  FIG. 4B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG. 4B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG. 4B, 460  corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG. 5A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some embodiments, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS. 1A-4B ). In some embodiments, device  500  has touch-sensitive display screen  504 , hereafter touch screen  504 . Alternatively, or in addition to touch screen  504 , device  500  has a display and a touch-sensitive surface. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) may have one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  500  has one or more input mechanisms  506  and  508 . Input mechanisms  506  and  508 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  500  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device  500  to be worn by a user. 
       FIG. 5B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS. 1A, 1B , and  3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, touch-intensity sensitive component  524 . In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  may be a button, in some examples. 
     Input mechanism  508  may be a microphone, in some examples. Personal electronic device  500  can include various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including process  700  (e.g.,  FIG. 7 ). The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory computer-readable storage medium” can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG. 5B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS. 1, 3, and 5 ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG. 3  or touch-sensitive surface  451  in  FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG. 1A  or touch screen  112  in  FIG. 4A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     2. Reduced Keyboard Interface 
     Reduced keyboard interfaces can be used to provide text input on electronic devices (e.g., devices  100 ,  300 , or  500 ).  FIGS. 6A-C  illustrate exemplary reduced keyboard interface  600  for inputting Japanese text. Reduced keyboard interface  600  can be referred to as a 10-key kana keyboard interface. Reduced keyboard interface  600  can be displayed on a touch screen (e.g., touch screen  112 ) of the electronic device. As shown, reduced keyboard interface  600  can include 10 primary character keys  602  (e.g., labelled  ,  ,  ,  ,  ,  ,  ,  ,  , and  ) for inputting Japanese hiragana characters and 2 additional keys  604 ,  606  for adding diacritic symbols and punctuation, respectively. Each primary character key  602  can be configured to provide access to one or more secondary character keys. In particular, as shown in  FIG. 6B , providing a touch contact to primary character key  602 - 1  associated with the character   an cause four secondary character keys  608 ,  610 ,  612 ,  614  associated with the characters  ,  ,  ,  , respectively, to be displayed. As such, in the present example, 50 character keys can be available for input via the 10 primary character keys  602 . 
     Reduced keyboard interface  600  can be configured to receive contact inputs from a user and cause respective hiragana characters to be inputted to the device. For inputting hiragana characters associated with primary character keys  602 , a single-tap input can be provided to the respective primary character key  602 . For example, with reference to  FIG. 6B , a single-tap input can be provided to primary character key  602 - 1  to input the character  . A single-tap input can include a touch contact to a primary character key followed by a release or break in contact from the primary character key. In addition, lateral movement during the touch contact can be less than a predetermined threshold amount. 
     For inputting hiragana characters associated with secondary character keys, a flick input can be provided to the respective primary character key  602 . For example, as shown in  FIGS. 6B-C , a flick input in a first direction (e.g., a direction represented by arrow  616 ) can be provided to primary character key  602 - 1  and to input the character   via secondary character key  608 . As shown in  FIG. 6C , in response to the flick input, reduced keyboard interface  600  can highlight secondary character key  608  to indicate that input of the characterr   is received via secondary character key  608 . The flick input can include a contact motion from first position  617  (e.g., at primary character key  602 - 1 ) to second position  619  (e.g., at secondary character key  608 ) on the reduced keyboard interface  600 . In particular, in the present example, the flick input can include initiating a touch contact to primary character key  602 - 1  at first position  617 , providing a contact motion from first position  617  to second position  619 , and releasing touch contact at second position  619  from secondary character key  608 . The flick input can be provided such that there is no break in contact with reduced language input interface  600  from the initial touch contact to the release in touch contact. 
     Hiragana characters associated with secondary character keys can alternatively be inputted by providing a multi-tap input to the respective primary character key  602 . In particular, each secondary character key can be associated with a predefined multi-tap input pattern. For example, to input the character  , a predefined multi-tap input pattern that includes a first touch contact to primary character key  602 - 1  followed by a second touch contact to character key  602 - 1  can be received (e.g., double-tap input). A break or release in touch contact can occur between the first touch contact and the second touch contact. Further, the first touch contact and the second touch contact can occur within a predetermined amount of time. In a similar manner, the character   can be inputted with a predefined multi-tap input pattern that includes three touch contacts to primary character key  602 - 1  (e.g., triple-tap input). 
     Although in the present example, reduced keyboard interface  600  is configured to input Japanese text, it should be recognized that in other examples, the reduced keyboard interface can be configured to input text of other languages. In particular, each primary character key and secondary character key can correspond to a written symbol of a language. Further, it should be appreciated that the number of primary character keys and the number of secondary character keys that can be accessed via each primary character key can vary. 
     3. Processes for Language Input Correction 
       FIG. 7  is a flow diagram illustrating process  700  for language input correction according to various examples.  FIGS. 8A-D  are exemplary screenshots of an electronic device illustrating various stages of an exemplary process for language input correction according to various examples. Process  700  can be performed at a device (e.g., device  100 ,  300 , or  500 ) with a touch-sensitive display (e.g., touch screen  112 ). Process  700  is described below with simultaneous reference to  FIG. 7  and  FIGS. 8A-D . It should be appreciated that some operations in process  700  can be combined, the order of some operations can be changed, and some operations can be omitted. 
     At block  702  of process  700 , a sequence of contact inputs can be detected via a keyboard interface on the touch-sensitive display (e.g., touch screen  112 ). The keyboard interface can be any keyboard interface for inputting text. For example, keyboard interface can be similar or identical to reduced keyboard interface  600  described above with reference to  FIGS. 6A-C . In some examples, the keyboard interface can be a 10-key kana keyboard interface for inputting Japanese characters. The sequence of contact inputs can include one or more of a single-tap input, a flick input, or a multi-tap input to one or more character keys of the keyboard interface. One or more of blocks  704 - 718  can be performed in response to detecting the sequence of contact inputs at block  702 . 
     In examples where a flick input is used to input text (e.g., Japanese hiragana input), a contact input of the sequence of contact inputs can include a contact motion from a first position to a second position of the keyboard interface (e.g., a flick input described above with reference to  FIGS. 6B-C ). For example, as shown in  FIG. 8A , a sequence of contact inputs can be detected to input the string of hiragana characters   (e.g., first character string  818 ). The sequence of contact inputs can include a first contact input to primary character key  802 - 1 , a second contact input to primary character key  802 - 3 , and a third contact input to primary character key  802 - 4 . In this example, the first contact input and the third contact input can each be single-tap inputs. In particular, the first contact input and the third contact input can be intended to select primary character keys  802 - 1  and  802 - 4 , respectively, on keyboard interface  800 . Corresponding characters   and   can be respectively inputted as a result of the first contact input and the third contact input. Further, the second contact input can be a flick input. In particular, with reference to  FIG. 8B , the second contact input can be a contact motion from first position  806  to second position  808  on keyboard interface  800  in a direction indicated by arrow  810 . Second contact input can be intended to select secondary character key  804 - 1 . Thus, corresponding character   can be inputted as a result of second contact input. 
     In flick input examples, the contact motion of second contact input can include various characteristics associated with the intended character key corresponding to the contact motion. In particular, the contact motion can be associated with a flick distance between first position  806  and second position  808  of the contact motion or a flick speed of the contact motion from first position  806  and second position  808 . Further, the contact motion of the second contact input can be associated with a flick angle (e.g., angle  812 ) with respect to a reference axis (e.g., reference axis  814 ) of keyboard interface  800 . 
     In examples where multi-tap input is used to input text, a contact input of the sequence of contact inputs can include a first contact to a key of the keyboard interface and a second contact to the key of the keyboard interface (e.g., a double-tap input). The first contact and the second contact can occur within a predetermined amount of time. Additionally, the contact input can include a break in contact between the first contact and the second contact. Referring back to the example shown in  FIG. 8A , the sequence of contact inputs for inputting the string of hiragana characters   can include a multi-tap input. Specifically, the first contact input and the third contact input of the sequence of contact inputs can each include a single-tap input to primary character keys  802 - 1  and  802 - 3 , respectively. The second contact input of the sequence of contact inputs can include a first touch input to primary character key  802 - 3  followed by a second touch input to primary character key  802 - 3 . First touch input and second touch input can occur within a predetermined amount of time. Further, a break in touch contact can occur between the first touch contact and the second touch contact. 
     In multi-tap input examples, the contact input can include various characteristics for determining the character key corresponding to the contact input. Some of these characters can be similar to those of flick inputs, such as, for example, the position of each tap input with respect to the center position of each character key. Other characteristics can be different from those of flick inputs. For example, the first contact and the second contact of a multi-tap input can each be associated with a contact intensity (e.g., an intensity of the contact on a touch-sensitive surface) and a contact duration (e.g., the duration of time in which each contact remains on the touch-sensitive surface). The contact input can also include a time interval between the first contact and the second contact (e.g., the time interval from when the first contact is released to when the second contact is initiated). The contact intensity, contact duration, and time interval can each be utilized to determine the character key corresponding to the contact input. 
     At block  704  of process  700 , a plurality of character strings that potentially correspond to the sequence of contact inputs can be determined. In particular, each contact input of the sequence of contact inputs can be interpreted as a selection of one of several possible character keys and thus can correspond to several respective characters. Returning to the example shown in  FIG. 8A , the first contact input, intended to be an input to primary character key  802 - 1 , can be determined to potentially be an input to one of the surrounding primary character keys  802 - 2 ,  802 - 4 ,  802 - 5 . As shown, primary character keys  802 - 1 ,  802 - 2 ,  802 - 4 ,  802 - 5  correspond to Japanese hiragana characters  ,  ,  , or  , respectively, and thus first contact input can be determined to correspond to any one of characters  ,  ,  , or  . Similarly, third contact input, intended to be an input to primary character key  802 - 4 , can be determined to potentially be an input to one of the surrounding primary character keys  802 - 1 ,  802 - 5 ,  802 - 7 . Thus, third contact input can be determined to correspond to any one of character  ,  ,  , and  . 
     Further, second contact input, intended to be an input to secondary character key  804 - 1 , can be determined to potentially be an input to other character keys. In particular, depending on the position of the flick input, the second contact input can potentially be interpreted as a flick input to a neighboring character key. For example, second contact input can be determined to potentially be an input to secondary character key  816 - 1  of  FIG. 8C  (e.g., character  ), where the second contact input is interpreted as a flick input initiated at neighboring primary character key  802 - 2  rather than at primary character key  802 - 3 . Additionally, depending on the speed or distance of the flick input, the second contact input can potentially be interpreted as a tap input to primary character key  802 - 3  (e.g., character  ) rather than a flick input to primary character key  802 - 3  (e.g., character  ). Thus, in this example, second contact input can potentially correspond to any one of characters  ,  , and  . 
     The plurality of character strings that potentially correspond to the sequence of contact inputs can include any combination of characters that potentially correspond to the first, second, and third contact inputs. Specifically, in the example of  FIGS. 8A-C , the plurality of character strings can include the first character string   (“asita”—meaning tomorrow) and the second character string   (“Akita”—the name of a place). The first and second character strings can correspond to the same portion of the sequence of contact input. In this example, the first character string   includes the first character   that corresponds to one interpretation of the contact motion of the second contact input. The second character string     includes the second character   that corresponds to another interpretation of the contact motion of the second contact input. 
     In examples where multi-tap inputs are received, each multi-tap input can similarly correspond to two or more character keys and thus two or more characters. For example, an intended double-tap input could be interpreted as having fewer taps (e.g., a single-tap input) or additional taps (e.g., a triple-tap input), depending on the duration or intensity of each tap. In addition, depending on the position of each tap or the time interval between taps, a double-tap input could be interpreted as two single-tap inputs to the same character key or to two different character keys. Returning to the example of  FIG. 8A , the second contact input of the sequence of contact inputs can include a first touch input to primary character key  802 - 3  followed by a second touch input to primary character key  802 - 3 . In this example, the second contact input can potentially be interpreted as corresponding to a first predefined input pattern (e.g., a double-tap input) to primary character key  802 - 3 , which corresponds to the first character  . In addition, the second contact input can potentially be interpreted as corresponding to a second predefined input pattern (e.g., a single-tap input) to primary character key  802 - 3 , which corresponds to the third character  . In this example, the plurality of character strings that potentially correspond to the sequence of contact inputs can include the first character string   (“asita”—meaning tomorrow) and the third character string   (“Asada”—a family name). In this example, the first character string   includes the first character   that corresponds to one interpretation of the second contact input. The third character string   includes the third character   that corresponds to another interpretation of the second contact input. 
     Further, as described above, a double-tap input can potentially be interpreted as two single-tap inputs to the same character key or to two different character keys depending on the position of each tap or the time interval between taps. Thus, in the present example, the second contact input can potentially be interpreted as corresponding to two separate single-tap inputs to any of primary character key  802 - 3  and neighboring prima character keys  802 - 2 , and  802 - 6 , which can correspond to, for example, the input of characters  ,  ,  , and    . Therefore, in this example, the plurality of character string can include the character strings of  ,  ,  , and  . It should be recognized that other character strings resulting from other combinations of character inputs can be contemplated. 
     Although, in the examples described above, only some of the neighboring character keys are considered to determine the plurality of character strings, it should be appreciated that any number of the character keys (primary or secondary) can be considered to determine the plurality of character strings. 
     At block  706  of process  700 , a probability of each character string of the plurality of character strings given the sequence of contact inputs can be determined. In particular, the probability of inputting each character key associated with each character of the character string given the sequence of contact inputs can be determined using one or more geometry models. A geometry model can encode the probability of selecting each possible character key calculated from the sequence of contact inputs on the keyboard interface. The probability of each character string can then be determined based on a combined probability of inputting each character key associated with each character of the character string given the sequence of contact inputs. 
     In one example, with reference to the first character string  , the probability that the first contact input (e.g., a tap input) is an intended input to select primary character key  802 - 1  (e.g., corresponding to the character  ), the probability that the second contact input (e.g., a flick input from position  806  to position  808 ) is an intended input to select secondary character key  804 - 1  (e.g., corresponding to the character  ), and the probability that the third contact input is an intended input to select primary character key  802 - 4  (e.g., corresponding to the character  ) can each be determined using one or more geometry models. The probability of the first character string   given the sequence of contact inputs can thus be determined based on a combination of each of the above determined probabilities. The probability of the second character string   given the sequence of contact inputs and the probability of the third character string   given the sequence of contact inputs can be determined in a similar manner. 
     The probability that a contact input is an intended input to select a particular character key can be based on several factors associated with the contact input. For tap inputs, such factors can include the position of the tap input with respect to the center position of each character key, the intensity of the tap input, or the duration of the tap input (e.g., the duration in which contact is sustained with the keyboard interface). In particular, a higher probability can be associated with a shorter distance between the position of the tap input and the center position of the particular character key, a greater intensity of the tap input, or a longer duration of the tap input. 
     For flick inputs, the probability that a contact input is an intended input to select a particular character key can be based on similar factors as for tap inputs, described above. Additionally, the probability can be based on a flick input distance (e.g., a distance between first position  806  and second position  808  of the contact motion in  FIG. 8B ), a flick input speed (e.g., a speed of the contact motion from first position  806  to second position  808 ), or a flick input angle (e.g., angle  812  in  FIG. 8B ). In particular, a higher probability can be associated with a longer flick distance or a slower flick speed. With respect to flick angle, the probability can be based on how close the flick angle corresponds to the position of a particular character key. For example, with reference to  FIG. 8B , the probability that the flick input from position  806  to position  808  is an intended input to secondary character key  804 - 1  can be higher for angle  812  that is closer to 90 degrees with respect to reference axis  814  than to 0 degrees. 
     In some examples, a geometry model can be implemented to account for the position of a tap input when determining the probability that a contact input is an intended input to select a character key. In these examples, the probability mass can be distributed to each possible key based on two-dimensional Gaussian distributions. In particular, the probability that a contact input at a position p is an intended input to a primary character key k can be expressed as: 
               P   ⁡     (     k   |   p     )       =       exp   ⁡     [     -       (            p   -     c   ⁡     (   k   )              ⁢     /     ⁢   D     )     2       ]       Z           
where Z=Σk exp [−(|p−c(k)/D) 2 ], Σk is the summation over all possible primary character keys, D is a constant decay factor, and c(k) is the center of the character key k. As evident from the above equation, the probability that a contact input at a position p (e.g., position  801  in  FIG. 8A ) is an intended input to a primary character key k (e.g., primary character key  802 - 1  in  FIG. 8A ) can be determined to be higher when a distance between position p and the center position of the character key k(|p−c(k)|) is smaller.
 
     Further, in some examples, a geometry model can be implemented to account for the flick distance and the initial position of flick inputs. In these examples, a threshold distance θ can be set on the flick distance x, where the contact input is interpreted as a flick input (rather than a tap input) only when the flick distance is larger than the threshold distance θ. Additionally, the initial position p of the flick input (e.g., first position  806  in  FIG. 8B ) can be modeled according to the Gaussian distribution described above. For example, with reference to  FIG. 8B , if the flick distance x (e.g., the distance between position  806  and position  808 ) is greater or equal to the threshold distance θ, the probability that a contact input, initiated at a position p (e.g., position  806 ) of primary character key k o  (e.g., primary character key  802 - 3 ) and having a flick distance x, is an intended flick input to select secondary character key k 1  (e.g., secondary character key  804 - 1 ) can be expressed as P(k 1 |p, x)=P(k o |p)*(G/(G+exp [−x 2 /E 2 ])), and the probability that a contact input, initiated at a position p (e.g., position  806 ) of primary character key k o  (e.g., primary character key  802 - 3 ) and having a flick distance x, is an intended tap input to select primary character key k o  (e.g., primary character key  802 - 3 ) can be expressed as P(k o |p,x)=P(k o |P)*(exp [−x 2 /E 2 ]/(G+exp [−x 2 /E 2 ])), where E and G are constants. Further, if the flick distance x (e.g., the distance between position  806  and position  808 ) is less than the threshold distance θ, the probability that a contact input, initiated at a position p (e.g., position  806 ) of primary character key k o  (e.g., primary character key  802 - 3 ) and having a flick distance x is an intended flick input to select secondary character key k 1  (e.g., secondary character key  804 - 1 ) can be expressed as P(k 1 |p, x)=P(k o |P)*(exp [−F/x]/(H+exp [−F/x])) and the probability that a contact input, initiated at a position p (e.g., position  806 ) on primary character key k o  (e.g., primary character key  802 - 3 ) and having a flick distance x, is an intended tap input to primary character key k o  (e.g., primary character key  802 - 3 ) can be expressed as P(k o |p,x)=P(k o |p)*(H/(H+exp [−F/x])), where F and H are constants. 
     By utilizing the geometry models described above, the probability that a contact input is an intended input to select a particular character key can be determined based on the position and/or the flick distance of the contact input. For example, with reference to the second contact input comprising a contact motion from position  806  to position  808  in  FIG. 8B , the second contact input could be interpreted as an intended flick input to select secondary character key  804 - 1 , an intended flick input to select secondary character key  816 - 1  ( FIG. 8C ), an intended tap input to selected primary character key  802 - 3 , or an intended tap input to select primary character key  802 - 2  ( FIG. 8C ). Based on the position  806 , the center position of primary character keys  802 - 2  and  802 - 3 , and the distance between position  806  and  808 , the geometry models described above can be used to determine the probability that the second input is an intended input to select each of these character keys. Although specific examples of geometry models are described above to account for flick distance and/or contact position, it should be recognized that other geometry models implementing different distributions can be contemplated. Further, it should be appreciated that the other factors described above can also be modeled using one or more geometry models to determine the probability of inputting a particular character key given a contact input. For example, factors such as contact intensity, contact duration, flick speed, or flick angle can be modeled in one or more geometry models. Further, for multi-tap inputs, it can be contemplated that analogous geometry models can be implemented to account for one or more factors such as the contact intensity of each tap, the contact position of each tap, the contact duration of each tap, and the time interval between successive taps. 
     In some examples, a probability that a contact input of the sequence of contact inputs comprises a first predefined input pattern can be determined. For example, with reference to the first character string  , the second contact input can be a multi-tap input for inputting the character  . In this example, the first predefined input pattern can comprise two successive tap inputs (e.g., a first touch input followed by a second touch input with a break in contact in between) to primary character key  802 - 3  and can correspond to the character  . Thus, the probability of the first character string   given the sequence of contact inputs can be determined based on the probability that the second contact input of the sequence of contact inputs comprises the first predefined input pattern. Similarly, for the third character string    , a probability that the second contact input of the sequence of contact inputs comprises a second predefined input pattern can be determined. In this example, the second predefined input pattern can comprise a single-tap input (e.g., a first touch input followed by a break in contact) to primary character key  802 - 3  and can correspond to the character  . Thus, the probability of the third character string   given the sequence of contact inputs can be determined based on the probability that the second contact input of the sequence of contact inputs comprises the second predefined input pattern. 
     The probability that a contact input comprises a first predefined input pattern or a second predefined input pattern can be based on several factors associated with the contact input. As discussed above, such factors can include the position of each tap input on the keyboard interface with respect to the center position of each character key, the contact intensity of each tap input, the contact duration of each tap input, and the time interval between successive tap inputs of the multi-tap input. In particular, each tap input of a multi-tap input can be detected with greater confidence with respect to a character key when the position of each tap is closer to the center position of the character key, when the contact intensity of each tap input is greater, or when the contact duration of each time is longer. Further, two successive tap inputs can be detected with greater confidence when a time interval between each tap input is greater than a lower threshold value and less than an upper threshold value. It should be recognized that similar geometry models as described above can be implemented to account for one or more of these factors and the geometry model can be used to determine the probability that a contact input comprises a first predefined input pattern or a second predefined input pattern. 
     At block  708  of process  700 , a first character string corresponding to the sequence of contact inputs can be displayed in a text field on a touchscreen display (e.g., on touchscreen  112 ). In some examples, the first character string can be associated with the highest probability among the plurality of character strings given the sequence of contact inputs. For example, as shown in  FIG. 8B , first character string  818    is displayed on text field  820 . As shown, first character string  818    includes first character  822   . As described above, first character  822    can correspond to a flick input to select secondary character key  804 - 1  (e.g., a contact motion from position  806  to position  808  in  FIG. 8B ). Alternatively, first character  822    can correspond to a double-tap input to primary character key  802 - 3  (e.g., the contact input comprising a first and a second touch contact to primary character key  802 - 3 ). In this example, first character string  818    can be determined at block  706  to have the highest probability among the plurality of character strings given the sequence of contact inputs. 
     At block  710  of process  700 , a plurality of candidate words corresponding to the sequence of contact inputs can be determined. The plurality of candidate words can be determined from the plurality of character strings of block  706 . In some examples, word matching with respect to each of the plurality of character strings can be performed by searching a lexicon. A search of the lexicon can identify candidate words that correspond to the plurality of character strings. In some implementations, a lexicon having a trie data structure can be used to perform the word matching. In particular, an efficient stack-based search algorithm can be utilized in conjunction with the trie data structure lexicon. Such a search implementation can enable a large number of word matches for each computational pass through the lexicon. As such, the determining of candidate words corresponding to the plurality of character strings can be efficiently achieved with fewer computational passes, which significantly reduces computational time and cost. 
     The plurality of candidate words can include words of one or more writing systems (e.g., hiragana, katakana, or kanji). In particular, the plurality of candidate words can include words of a first writing system and words of a second writing system. For example the first character string   can be determined to correspond to the candidate words   (e.g., a hiragana candidate word),   (e.g., a kanji candidate word), and   (e.g., a katakana candidate word); the second character string   can be determined to correspond to the candidate words  ,  , and  ; and the third character string   can be determined to correspond to the candidate words  ,  , and  . As evident in this example, the sequence of contact inputs can correspond to a large number of candidate words that are determined from multiple character strings. As shown in  FIG. 7 , block  710  can include blocks  712 - 714 . 
     At block  712  of process  700 , a probability of each candidate word given a respective character string of the plurality of character strings can be determined. For example, with reference to the first character string  , the probability of the candidate word   given the first character string   can be determined. The probability can be determined using one or more language models. In particular, a language model can be trained using a corpus of text, and the probability of a candidate word given the first character string can be based on the probability of occurrence of the candidate word in the corpus of text. Additionally or alternatively, the determined probability can take into account contextual information. In particular, the probability of each candidate word can be determined based on various contextual information, such as, for example, the surrounding textual context, the type of application, the type of text, time of day or year, and the like. 
     In some examples, a class-based language model (e.g., class bi-gram language model) can be used in conjunction with an n-gram language model (e.g., a tri-gram language model) to determine a probability of each candidate word given a respective character string. In particular, a class bi-gram language model can be less computationally intensive than a tri-gram language model. Thus, an initial probability can be determined using a class bi-gram language model, and words having a probability less than a threshold value can be excluded from the plurality of candidate words. The remaining candidate words can then be processed through a tri-gram language model to determine a final probability of each candidate word given a respective character string. In this way, the determination can be performed more quickly and efficiently. 
     At block  714  of process  700 , a probability of each candidate word of the plurality of candidate words given the sequence of contact inputs can be determined. The probability of each candidate word given the sequence of contact inputs can be determined based on a combination of the probability of each candidate word given the respective character string (e.g., determined at block  712 ) and the probability of the respective character string given the sequence of contact inputs (e.g., determined at block  706 ). Suitable weighting factors can be applied to the probability of each candidate word given the respective character string and the probability of the respective character string given the sequence of contact inputs when determining the probability of each candidate word given the sequence of contact inputs. In some implementations, a linear interpolation of the probability of each candidate word given the respective character string and the probability of the respective character string given the sequence of contact inputs can be performed. 
     Because the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs can be determined based on the probability of the respective character string given the sequence of contact inputs, it should be recognized that the probability of each candidate word given the sequence of contact inputs can be dependent on the various factors modeled in the one or more geometry models described in block  706 . In particular, the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs can be based on factors such as the position of the contact input with respect to the center position of each key, the flick distance, the flick speed, the flick angle, the contact intensity, the contact duration, and the time interval between successive tap inputs of multi-tap inputs. 
     In some examples, the plurality of candidate words can be determined based on the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs. For example, candidate words having a probability less than a predetermined threshold value can be excluded from the determined plurality of candidate words. 
     At block  716  of process  700 , the plurality of candidate words of block  710  can be ranked. The ranking can be performed according to the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs. In particular, the plurality of candidate words can be ranked from the highest probability to the lowest probability. In one example, the first candidate words   and the second candidate words   can be ranked based on the probability of the first candidate word   given the sequence of contact inputs and the probability of the second candidate word   given the sequence of contact inputs, respectively. As described above, the probability of the first candidate word   given the sequence of contact inputs and the probability of the second candidate word   given the sequence of contact inputs can be based on the probability of the first character string   given the sequence of contact inputs and the probability of the second character string   given the sequence of contact inputs, respectively. In turn, the probability of the first character string   given the sequence of contact inputs and the probability of the second character string   given the sequence of contact inputs can be based on the probability that a contact input of the sequence of contact inputs is an intended input to select the secondary character key  804 - 1  ( FIG. 8B ) and the probability that a contact input of the sequence of contact inputs is an intended input to select the secondary character key  816 - 1  ( FIG. 8C ), respectively. 
     Because the plurality of candidate words are ranked based on the probability of each candidate word given the sequence of contact inputs, it should be recognized that the ranking can be based on the various factors modeled in the one or more geometry models discussed above in block  706 . In particular, the ranking can be based on factors such as the position of the contact input with respect to the center position of each key, the flick distance, the flick speed, the flick angle, the contact intensity, the contact duration, and the time interval between successive tap inputs in multi-tap inputs. 
     At block  718  of process  700 , a portion of the plurality of candidate words for user selection can be displayed for user selection. The displayed portion can include a subset of the plurality of candidate words that are determined and ranked at blocks  710 - 716 . In some examples, the portion of the plurality of candidate words can include the top N ranked candidate words, where N is a predetermined integer. The portion of the plurality of candidate words can include a first candidate word and a second candidate word. The first candidate word and the second candidate word can correspond to different character strings that are determined based on the sequence of contact inputs. 
     With reference to  FIG. 8D , candidate words  ,  ,  ,  , and   can be displayed in word selection interface  824 . These candidate words can be the candidate words with the four highest probabilities among a plurality of determined candidate words given the sequence of inputs. In particular, a user can select one of the displayed candidate words via word selection interface  824  to input the respective candidate word. As shown, the displayed candidate words include first candidate word  826   , second candidate word  828   , and third candidate word  830   . Notably, in this example, the displayed candidate words include words that are determined from different character strings. In particular, as described above, first candidate word  826   , second candidate word  828   , and third candidate word  830    can be determined based on the first character string  , the second character string  , and the third character string  , respectively. Each of these character strings can be determined by considering various possible intended inputs corresponding to each contact input of the sequence of contact inputs. Thus, in contrast to language input methods that determine candidate words based only a single character string (e.g., first character string  ), process  700  can determine a larger range of candidate words based on various probable character strings that correspond to the sequence of contact inputs. In this way, words that better correspond to the user&#39;s intent can be displayed for user selection. Further, the process can correct for unintended contact inputs (e.g., typos) by determining and displaying candidate words corresponding to potentially intended contact inputs. 
     Although, in the above examples, process  700  is described with respect to a Japanese kana keyboard, Japanese hiragana character strings, and Japanese candidate word strings (e.g., hiragana, katakana, and kanji words), it should be recognized that process  700  can also be practiced using other keyboard interfaces and writing systems (e.g., Chinese, Korean, etc.). Further, it can be contemplated that process  700  can be implemented for inputting text of one language and obtaining a translation of the text in another language. 
     4. Exemplary Electronic Devices 
     In accordance with some embodiments,  FIG. 9  shows an exemplary functional block diagram of an electronic device  900  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  900  are configured to perform the techniques described above. The functional blocks of the device  900  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 9  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 9 , an electronic device  900  includes a display unit  902  configured to display a graphic user interface (e.g., a text field, word selection interface, keyboard interface, etc.), optionally, a touch-sensitive surface unit  904  configured to receive contacts, and a processing unit  906  coupled to the display unit  902  and, optionally, the touch-sensitive surface unit  904 . In some embodiments, the display unit  902  and the touch-sensitive surface unit  904  can be a single unit (e.g., a touch-sensitive display unit). In some embodiments, the processing unit  906  includes a detecting unit  908 , a determining unit  910 , a ranking unit  912 , and a displaying unit  914 . 
     The processing unit  906  is configured to detect (e.g., with detecting unit) a sequence of contact inputs via a keyboard interface on the display unit  902  and/or the touch-sensitive surface unit  904 . A contact input of the sequence of contact inputs comprises a contact motion from a first position to a second position of the keyboard interface. The processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a plurality of candidate words corresponding to the sequence of contact inputs. The processing unit  906  is further configured to rank (e.g., with ranking unit  912 ) the plurality of candidate words based on a probability that the contact input is an intended input to a first key of the keyboard interface, and a probability that the contact input is an intended input to a second key of the keyboard interface. The processing unit  906  is further configured to display (e.g., with displaying unit), via display unit  902 , a portion of the plurality of candidate words for user selection. 
     In some embodiments, the first key corresponds to a first writing symbol of a language and the second key corresponds to a second writing symbol of the language. In some embodiments, the plurality of candidate words includes words of a first writing system and words of a second writing system. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a plurality of character strings that potentially correspond to the sequence of contact inputs. The processing unit  906  is further configured to determine (e.g., with determining unit  910 ) using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact inputs, where the plurality of candidate words is determined from the plurality of character strings based on the probability of each character string of the plurality of character strings given the sequence of contact inputs. 
     In some embodiments, the plurality of candidate words are determined based on a lexicon of a language model. In some embodiments, the probability that the contact input is an intended input to the first key of the keyboard interface is determined based on a distance between the first position and a center position of the first key, and the probability that the contact input is an intended input to the second key of the keyboard interface is determined based on a distance between the first position and a center position of the second key. 
     In some embodiments, the probability that the contact input is an intended input to the first key of the keyboard interface and the probability that the contact input is an intended input to the second key of the keyboard interface are each determined based on a distance between the first position and the second position of the contact motion. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a probability of each candidate word given the sequence of contact inputs, where ranking the plurality of candidate words is based on the probability of each candidate word given the sequence of contact inputs. 
     In some embodiments, the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on a probability of a respective character string of the plurality of character strings given the sequence of contact inputs. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, where the probability of each candidate word of the plurality of candidate words given the sequence of contact inputs is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
     In some embodiments, the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings is determined using one or more language models. 
     In some embodiments, the plurality of candidate words is determined using a lexicon with a trie data structure. 
     In some embodiments, the plurality of candidate words is ranked based on a distance between the first position and a center position of each key on the keyboard interface. In some embodiments, the plurality of candidate words is ranked based on a distance between the first position and the second position of the contact motion. In some embodiments, the plurality of candidate words is ranked based on a speed of the contact motion from the first position and the second position. In some embodiments, the plurality of candidate words is ranked based on an angle of the contact motion with respect to a reference axis of the keyboard interface. In some embodiments, the keyboard interface is a 10-key kana keyboard interface. 
     In some embodiments, the processing unit  906  is configured to detect (e.g., with detecting unit) a sequence of contact inputs via a keyboard interface on the display unit  902  and/or the touch-sensitive surface unit  904 . A contact input of the sequence of contact inputs comprises a contact motion from a first position to a second position of the keyboard interface. The processing unit  906  is further configured to display (e.g., with displaying unit  914 ) in a text field via the display unit  902 , a first character string corresponding to the sequence of contact inputs. The first character string includes a first character that corresponds to the contact motion. The processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a plurality of candidate words corresponding to the sequence of contact inputs. The plurality of candidate words includes a first candidate word and a second candidate word. The first candidate word is based on the first character string and the second candidate word is based on a second character string that corresponds to the sequence of contact inputs. The second character string includes a second character corresponding to the contact motion. The processing unit  906  is further configured to display (e.g., with displaying unit  914 ), via the display unit  902 , a portion of the plurality of candidate words for user selection. The portion includes the first candidate word and the second candidate word. 
     In some embodiments, the first character corresponds to a first key of the keyboard interface, and the second character corresponds to a second key of the keyboard interface that is different from the first key. In some embodiments, the first character string and the second character string each include characters of a first writing system and the plurality of candidate words includes words of a first writing system and words of a second writing system. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a plurality of character strings corresponding to the sequence of contact inputs, where the plurality of character strings includes the first character string and the second character string. The processing unit  906  is further configured to determine (e.g., with determining unit  910 ), using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact inputs, where the plurality of candidate words is determined based on the probability of each character string of the plurality of character strings given the sequence of contact inputs. 
     In some embodiments, the probability of each character string of the plurality of character strings given the sequence of contact inputs is determined based on a distance between the first position and a center position of each key on the keyboard interface. In some embodiments, the probability of each character string of the plurality of character strings given the sequence of contact inputs is determined based on a distance between the first position and the second position of the contact motion. 
     In some embodiments, the probability of each character string of the plurality of character strings given the sequence of contact inputs is determined based on a speed of the contact motion from the first position and a second position. In some embodiments, the probability of each character string of the plurality of character strings given the sequence of contact inputs is determined based on an angle of the contact motion with respect to a reference axis of the keyboard interface. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, where the plurality of candidate words is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
     In some embodiments, the plurality of candidate words is determined using a lexicon with a trie data structure. In some embodiments, the keyboard interface is a 10-key kana keyboard interface. 
     In some embodiments, the processing unit  906  is configured to detect (e.g., with detecting unit) a sequence of contact inputs via a keyboard interface on the display unit  902  and/or touch-sensitive surface unit  904 ). A contact input of the sequence of contact inputs comprises a first contact to a key of the keyboard interface and a second contact to the key of the keyboard interface. The processing unit  906  is further configured to display (e.g., with displaying unit  914 ), in a text field on the display unit  902 , a first character string corresponding to the sequence of contact inputs, where the first character string includes a first character that corresponds to the contact input. The processing unit  906  is further configured to determined (e.g., with determining unit  910 ) a plurality of candidate words corresponding to the sequence of contact inputs. The plurality of candidate words includes a first candidate word and a second candidate word, where the first candidate word is based on the first character string and the second candidate word is based on a second character string that corresponds to the sequence of contact inputs. The second character string includes a second character corresponding to the contact input. The processing unit  906  is further configured to display (e.g., with displaying unit  914 ), via the display unit  902 , a portion of the plurality of candidate words for user selection. The portion includes the first candidate word and the second candidate word. 
     In some embodiments, the contact input further comprises a break in contact between the first contact and the second contact. In some embodiments, the first character string and the second character string each include characters of a first writing system, and the plurality of candidate words includes words of a first writing system and words of a second writing system. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a plurality of character strings that potentially correspond to the sequence of contact inputs, the plurality of character strings include the first character string and the second character string. The processing unit  906  is further configured to determine (e.g., with determining unit  910 ), using a geometry model, a probability of each character string of the plurality of character strings given the sequence of contact input, where the plurality of candidate words is determined based on the probability of each character string of the plurality of character strings given the sequence of contact input. 
     In some embodiments, the first character corresponds to a first predefined input pattern to the key of the keyboard interface, and the second character corresponds to a second predefined input pattern to the key of the keyboard interface. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a probability that the contact input comprises the second predefined input pattern, wherein the probability of each character string of the plurality of character strings given the sequence of contact input is determined based on the probability that the contact input comprises the second predefined input pattern. 
     In some embodiments, the probability that the contact input comprises the second predefined input pattern is determined based on an intensity of the first contact or the second contact. In some embodiments, the probability that the contact input comprises the second predefined input pattern is determined based on a duration of the first contact or the second contact. In some embodiments, the probability that the contact input comprises the second predefined input pattern is determined based on a distance between a center position of the key and a position of the first contact or the second contact. In some embodiments, the probability that the contact input comprises the second predefined input pattern is determined based on a time interval between the first contact and the second contact. 
     In some embodiments, the processing unit  906  is further configured to determine (e.g., with determining unit  910 ) a probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings, where the plurality of candidate words is determined based on the probability of each candidate word of the plurality of candidate words given a respective character string of the plurality of character strings. 
     In some embodiments, the plurality of candidate words is determined using a lexicon with a trie data structure. In some embodiments, the keyboard interface is a 10-key kana keyboard interface. 
     The operations described above with reference to  FIG. 7  are, optionally, implemented by components depicted in  FIGS. 1A-1B  or  FIG. 9 . For example, detecting operation  702 , determining operations  704 ,  706 ,  710 ,  712 ,  714 , ranking operation  716 , and displaying operations  708 ,  718  may be implemented by text input module  134 . Text input module  134  can detect a sequence of contact inputs via a keyboard interface displayed on touch-sensitive display  112 . Text input module  134  can determine a plurality of character strings potentially corresponding to the sequence of contact inputs. Text input module  134  can determine (e.g., with a geometry model of the text input module  134 ) a probability of each character string given the sequence of contact inputs. Text input module  134  can display a first character string of the plurality of character strings in a text field displayed on touch-sensitive display  112 . Text input module  134  can determine a plurality of candidate words corresponding to the sequence of contact inputs. Text input module  134  can determine (e.g., with a language model of the text input module  134 ) a probability of each candidate word given a respective character string of the plurality of character strings. Text input module  134  can determine a probability of each candidate word given the sequence of contact inputs. Text input module  134  can rank the plurality of candidate words based on a probability that the contact input is an intended input to a first key of the keyboard interface, and a probability that the contact input is an intended input to a second key of the keyboard interface. Text input module  134  can display on touch-sensitive display  112  a portion of the plurality of candidate words for user selection. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1A-1B . 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

Metadata:
Filing Date: 20150903
Publication Date: 20181016
Grant Date: 20181016
Priority Date: 20150605
Inventors: HATORI, Jun
YU, DOMINIC
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0236", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0237", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0236", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0237", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0237", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0237", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 57451040