Skip to contentSkip to navigationSkip to topbar
Rate this Page:

TwiML™ Voice: <Gather>


You can use TwiML's <Gather> verb to collect digits or transcribe speech during a call.

The following example shows the most basic use of <Gather> TwiML:


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather/>
_10
</Response>

You can always send Twilio plain TwiML, or leverage the helper libraries to add TwiML to your web applications:

Simple <Gather>

simple-gather page anchor

Toggle to your preferred programming language, or view the raw TwiML to see how the libraries and TwiML syntax differ

Node.js
Python
C#
Java
PHP
Ruby

_10
const VoiceResponse = require('twilio').twiml.VoiceResponse;
_10
_10
_10
const response = new VoiceResponse();
_10
response.gather();
_10
_10
console.log(response.toString());

Output

_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<!-- page located at http://example.com/simple_gather.xml -->
_10
<Response>
_10
<Gather/>
_10
</Response>

When Twilio executes this TwiML, it will pause for up to five seconds to wait for the caller to enter digits on their keypad. A few things might happen next:

  • The caller enters digits followed by a # symbol or 5 seconds of silence. Twilio then sends the user's input as a parameter in a POST request to the URL hosting the <Gather> TwiML (if no action attribute is provided) or to the action URL.
  • The caller doesn't enter any digits and 5 seconds pass. Twilio will move on to the next TwiML verb in the document - since there are no more verbs here, Twilio will end the call.
(information)

Info

By nesting <Say> or <Play> in your <Gather>, you can read some text or play music for your caller while waiting for their input. See "Nest other verbs" below for examples and more information.


<Gather> Attributes

gather-attributes page anchor

<Gather> supports the following attributes that change its behavior:

Attribute nameAllowed valuesDefault value
actionURL (relative or absolute)current document URL
finishOnKey0-9, #, *, and '' (the empty string)#
hints"words, phrases that have many words", class tokens(link takes you to an external page)none
inputdtmf, speech, dtmf speechdtmf
languageBCP-47 language tagsen-US
methodGET, POSTPOST
numDigitspositive integerunlimited
partialResultCallbackURL (relative or absolute)none
partialResultCallbackMethodGET, POSTPOST
profanityFiltertrue, falsetrue
speechTimeoutpositive integer or autotimeout attribute value
timeoutpositive integer5
speechModeldefault, numbers_and_commands, phone_call, experimental_conversations, experimental_utterancesdefault
enhancedtrue, falsefalse
actionOnEmptyResulttrue, falsefalse

Use one or more of these attributes in a <Gather> verb like so:


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather input="speech dtmf" timeout="3" numDigits="1">
_10
<Say>Please press 1 or say sales for sales.</Say>
_10
</Gather>
_10
</Response>

action

action page anchor

The action attribute takes an absolute or relative URL as a value. When the caller finishes entering digits (or the timeout is reached), Twilio will make an HTTP request to this URL. That request will include the user's data and Twilio's standard request parameters.

If you do not provide an action parameter, Twilio will POST to the URL that houses the active TwiML document.

Twilio may send some extra parameters with its request after the <Gather> ends:

If you gather digits from the caller, Twilio will include the Digits parameter containing the numbers your caller entered.

If you specify speech as an input with input="speech", Twilio will include SpeechResult and Confidence:

  • SpeechResult contains the transcribed result of your caller's speech.
  • Confidence contains a confidence score between 0.0 and 1.0. A higher confidence score means a better likelihood that the transcription is accurate.

Note: Your code should not expect confidence as a required field as it is not guaranteed to be accurate, or even set, in any of the results.

After <Gather> ends and Twilio sends its request to your action URL, the current call will continue using the TwiML you send back from that URL. Because of this, any TwiML verbs that occur after your <Gather> are unreachable.

However, if the caller did not enter any digits or speech, call flow would continue in the original TwiML document.

(error)

Danger

Without an action URL, Twilio will re-request the URL that hosts the TwiML you just executed. This can lead to unwanted looping behavior if you're not careful. See our example below for more information.

(warning)

Warning

If you started or updated a call with a twiml parameter, the action URLs for <Record>, <Gather>, and <Pay> must be absolute.

The Call Resource API Docs have language-specific examples of creating and updating Calls with TwiML:

  • See "Create a Call resource with TwiML" under Create a Call Resource to see examples of creating a call with a twiml parameter.
  • See "Update a Call resource with TwiML" under Update a Call Resource to see examples of updating a call with a twiml parameter.

Imagine you have the following TwiML hosted at http://example.com/complex_gather.xml:


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather>
_10
<Say>
_10
Please enter your account number,
_10
followed by the pound sign
_10
</Say>
_10
</Gather>
_10
<Say>We didn't receive any input. Goodbye!</Say>
_10
</Response>

Scenario 1: If the caller:

  • does not press the keypad or say anything for five seconds, or
  • enters '#' (the default finishOnKey value) before entering any other digits

then they will hear, "We didn't receive any input. Goodbye!"

Scenario 2: If the caller:

  • enters a digit while the call is speaking "Please enter your account number..."

then the <Say> verb will stop speaking and wait for the user's action.

Scenario 3: If the caller:

  • enters 12345 and then presses # , or
  • allows 5 seconds to pass

then Twilio will submit the digits and request parameters to the URL hosting this TwiML (http://example.com/complex_gather.xml). Twilio will fetch this same TwiML again and execute it, getting the caller stuck in this <Gather> loop.

To avoid this behavior, it's best practice to point your action URL to a new URL that hosts some other TwiML for handling the duration of the call.

The following code sample is almost identical to the TwiML above, but we've added the action and method attributes:

Complex <Gather> with action/method and nested <Say>

complex-gather-with-actionmethod-and-nested-say page anchor

Specify an action URL to properly handle the rest of the call

Node.js
Python
C#
Java
PHP
Ruby

_12
const VoiceResponse = require('twilio').twiml.VoiceResponse;
_12
_12
_12
const response = new VoiceResponse();
_12
const gather = response.gather({
_12
action: '/process_gather.php',
_12
method: 'GET'
_12
});
_12
gather.say('Please enter your account number,\nfollowed by the pound sign');
_12
response.say('We didn\'t receive any input. Goodbye!');
_12
_12
console.log(response.toString());

Output

_11
<?xml version="1.0" encoding="UTF-8"?>
_11
<!-- page located at http://example.com/complex_gather.xml -->
_11
<Response>
_11
<Gather action="/process_gather.php" method="GET">
_11
<Say>
_11
Please enter your account number,
_11
followed by the pound sign
_11
</Say>
_11
</Gather>
_11
<Say>We didn't receive any input. Goodbye!</Say>
_11
</Response>

Now when the caller enters their input, Twilio will submit the digits and request parameters to the process_gather.php URL.

If we wanted to read back this input to the caller, our code hosted at /process_gather.php might look like:


_10
<?php
_10
// page located at http://yourserver/process_gather.php
_10
echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n";
_10
echo "<Response><Say>You entered " . $_REQUEST['Digits'] . "</Say></Response>";
_10
?>

Back to attributes list

finishOnKey lets you set a value that your caller can press to submit their digits.

For example, if you set finishOnKey to # and your caller enters 1234#, Twilio will immediately stop waiting for more input after they press #.

Twilio will then submit Digits=1234 to your action URL (note that the # is not included).

Allowed values for this attribute are:

  • # (this is the default value)
  • *
  • Single digits 0 - 9
  • An empty string ( '' )

If you use an empty string, <Gather> will capture all user input and no key will end the <Gather>. In this case, Twilio submits the user's digits to the action URL only after the timeout is reached.

Back to attributes list

(information)

Info

If the following TwiML is used, finishOnKey has no impact once the caller starts speaking.


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather input="speech dtmf" finishOnKey="#" timeout="5">
_10
<Say>
_10
Please say something or press * to access the main menu
_10
</Say>
_10
</Gather>
_10
<Say>We didn't receive any input. Goodbye!</Say>
_10
</Response>

You can improve Twilio's recognition of the words or phrases you expect from your callers by adding hints to your <Gather>.

The hints attribute contains a list of words or phrases that Twilio should expect during recognition.

You may provide up to 500 words or phrases in this list, separating each entry with a comma. Your hints may be up to 100 characters each, and you should separate each word in a phrase with a space, e.g.:


_10
hints="this is a phrase I expect to hear, keyword, product name, name"

We have also implemented Google's class token(link takes you to an external page) list to improve recognition(link takes you to an external page). You can pass a class token directly in the hints.


_10
hints="$OOV_CLASS_ALPHANUMERIC_SEQUENCE"

Back to attributes list

Specify which inputs (DTMF or speech) Twilio should accept with the input attribute.

The default input for <Gather> is dtmf. You can set input to dtmf, speech, or dtmf speech.

(information)

Info

If you set input to speech, Twilio will gather speech from the caller for a maximum duration of 60 seconds.

Please note that <Gather> speech recognition is not yet optimized for Alphanumeric inputs (e.g. ABC123), this could lead to inaccurate results and thus, we do not recommend it.

If you set dtmf speech for your input, the first detected input (speech or dtmf) will take precedence. If speech is detected first, finishOnKey will be ignored.

The following example shows a <Gather> that specifies speech input from the user. When this TwiML executes, the caller will hear the <Say> prompt. Twilio will then collect speech input for up to 60 seconds.

Once the caller stops speaking for five seconds, Twilio posts their transcribed speech to your action URL.

Node.js
Python
C#
Java
PHP
Ruby

_11
const VoiceResponse = require('twilio').twiml.VoiceResponse;
_11
_11
_11
const response = new VoiceResponse();
_11
const gather = response.gather({
_11
input: 'speech',
_11
action: '/completed'
_11
});
_11
gather.say('Welcome to Twilio, please tell us why you\'re calling');
_11
_11
console.log(response.toString());

Output

_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<!-- page located at http://example.com/simple_gather.xml -->
_10
<Response>
_10
<Gather input="speech" action="/completed">
_10
<Say>Welcome to Twilio, please tell us why you're calling</Say>
_10
</Gather>
_10
</Response>

Back to attributes list

The language attribute specifies the language Twilio should recognize from your caller.

This value defaults to en-US, but you can set your language to any of our supported languages: see the full list.

Back to attributes list

The method you set on <Gather> tells Twilio whether to request your action URL via HTTP GET or POST.

POST is <Gather>'s default method.

Back to attributes list

You can set the number of digits you expect from your caller by including numDigits in <Gather>.

(warning)

Warning

The numDigits attribute only applies to DTMF input.

For example, you might wish to set numDigits="5" when asking your caller to enter their 5-digit zip code. Once the caller enters the final digit of 94117, Twilio will immediately submit the data to your action URL.

Back to attributes list

If you provide a partialResultCallback URL, Twilio will make requests to this URL in real-time as it recognizes speech. These requests will contain a parameter labeled UnstableSpeechResult which contains partial transcriptions. These transcriptions may change as the speech recognition progresses.

(warning)

Warning

The webhooks Twilio makes to your partialResultCallback are asynchronous. They do not accept any TwiML in response. If you want to take more actions based on this partial result, you need to use the REST API to modify the call.

Back to attributes list

The profanityFilter specifies if Twilio should filter profanities out of your speech transcription. This attribute defaults to true, which replaces all but the initial character in each filtered profane word with asterisks, e.g., 'f***.'

If you set this attribute to false, Twilio will no longer filter any profanities in your transcriptions.

Back to attributes list

When collecting speech from your caller, speechTimeout sets the limit (in seconds) that Twilio will wait after a pause in speech before it stops its recognition. After this timeout is reached, Twilio will post the speechResult to your action URL.

(information)

Info

If you use both timeout and speechTimeout in your <Gather>, timeout will take precedence for DTMF input and speechTimeout will take precedence for speech.

If you set speechTimeout to auto, Twilio will stop speech recognition when there is a pause in speech and return the results immediately.

Back to attributes list

timeout allows you to set the limit (in seconds) that Twilio will wait for the caller to press another digit or say another word before it sends data to your action URL.

For example, if timeout is 3, Twilio wait three seconds for the caller to press another key or say another word before submitting their data.

Twilio will wait until all nested verbs execute before it begins the timeout period.

The default timeout value is 5.

Back to attributes list

speechModel allows you to select a specific model that is best suited for your use case to improve the accuracy of speech to text. The attribute currently supports default, numbers_and_commands, phone_call,experimental_conversations, and experimental_utterances.

numbers_and_commands and phone_call are best suited for the use cases where you'd expect to receive short queries such as voice commands or voice search. phone_call is best for audio that originated from a PSTN phone call (typically an 8khz sample rate).


_10
<Gather input="speech" enhanced="true"speechModel="phone_call">
_10
<Say>Please tell us why you're calling.</Say>
_10
</Gather>

(warning)

Warning

The phone_call value for speechModel currently only supports a set of languages, they are: en-US, en-GB, en-AU, fr-FR, fr-CA, ja-JP, ru-RU, es-US, es-ES, and pt-BR. You must also set the speechTimeout value to a positive integer, rather than using auto.

Experimental models are designed to give access to the latest speech technology and machine learning research, and can provide higher accuracy for speech recognition over other available models. However, some features that are supported by other available models are not yet supported by the experimental models such as confidence scores.

The experimental_utterances model is for short utterances that are a few seconds in length and is useful for trying to capture commands or other single shot directed speech use cases; think "press 0 or say 'support' to speak with an agent". The experimental_conversations model supports spontaneous speech and conversations; think "tell us why you're calling today".

Both experimental_conversations and experimental_utterances values for speechModel currently only supports a set of languages, they are listed here.

Please explore all options to see which works best for your use case.

Back to attributes list

The enhanced attribute instructs <Gather> to use a premium speech model that will improve the accuracy of transcription results. The premium speech model is only supported with phone_call speechModel. It costs 50% more at $0.03 per 15s of <Gather> than the standard phone_call model. The premium phone_call model was built using thousands of hours of training data. It ensures 54% fewer errors when transcribing phone conversations when compared to the basic phone_call model.

The following TwiML instructs <Gather> to use premium phone_call model:


_10
<Gather input="speech" enhanced="true"speechModel="phone_call">
_10
<Say>Please tell us why you're calling.</Say>
_10
</Gather>

(warning)

Warning

<Gather> will ignore the enhanced attribute if any other speechModel, other than phone_call is used.

For example, in the following TwiML, <Gather> ignores the enhanced attribute and applies standard numbers_and_commands speechModel.


_10
<Gather input="speech" enhanced="true" speechModel="numbers_and_commands">
_10
<Say>Please tell us why you're calling.</Say>
_10
</Gather>

(information)

Info

The premium enhancedphone_call model is priced at $0.03 per utterance while the standard phone_call model is priced at $0.02 per utterance.

Read the Language appendix to see if the enhanced model is available for your language.

Back to attributes list

actionOnEmptyResult allows you to force <Gather> to send a webhook to the action url even when there is no DTMF input. By default, if <Gather> times out while waiting for DTMF input, it will continue on to the next TwiML instruction.

For example, in the following TwiML when <Gather> times out, <Say> instruction is executed.


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather>
_10
<Say>
_10
Please enter your account number,
_10
followed by the pound sign
_10
</Say>
_10
</Gather>
_10
<Say>We didn't receive any input. Goodbye!</Say>
_10
</Response>

To always force <Gather> to send a webhook to the action Url use the following TwiML,


_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather actionOnEmptyResult="true" action="/gather-action">
_10
<Say>
_10
Please enter your account number,
_10
followed by the pound sign
_10
</Say>
_10
</Gather>
_10
</Response>


You can nest the following verbs within <Gather>:

The following example shows a <Gather> with a nested <Say>. This will read some text to the caller, and allows the caller to enter input at any time while that text is read to them:

Gather speech or DTMF with nested <Say>

gather-speech-or-dtmf-with-nested-say page anchor
Node.js
Python
C#
Java
PHP
Ruby

_12
const VoiceResponse = require('twilio').twiml.VoiceResponse;
_12
_12
_12
const response = new VoiceResponse();
_12
const gather = response.gather({
_12
input: 'speech dtmf',
_12
timeout: 3,
_12
numDigits: 1
_12
});
_12
gather.say('Please press 1 or say sales for sales.');
_12
_12
console.log(response.toString());

Output

_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<Response>
_10
<Gather input="speech dtmf" timeout="3" numDigits="1">
_10
<Say>Please press 1 or say sales for sales.</Say>
_10
</Gather>
_10
</Response>

(information)

Info

When a <Gather> contains nested <Say> or <Play> verbs, the timeout begins either after the audio completes or when the caller presses their first key. If <Gather> contains multiple <Play> verbs, the contents of all files will be retrieved before the <Play> begins.

Cache static media for <Play> verbs

cache-static-media-for-play-verbs page anchor

If you are using <Play> verbs, we recommend hosting your media in AWS S3 in us-east-1, eu-west-1, or ap-southeast-2 depending on which Twilio Region you are using. No matter where you host your media files, always ensure that you're setting appropriate Cache Control headers. Twilio uses a caching proxy in its webhook pipeline and will cache media files that have cache headers. Serving media out of Twilio's cache can take 10ms or less. Keep in mind that we run a fleet of caching proxies so it may take multiple requests before all of the proxies have a copy of your file in cache.

When a <Gather> reaches its timeout without any user input, call control will fall through to the next verb in your original TwiML document.

If you wish to have Twilio submit a request to your action URL even if <Gather> times out, include a <Redirect> after the <Gather> like this:

<Redirect> after <Gather>

redirect-after-gather page anchor

Send information to your action URL even if <Gather> times out

Node.js
Python
C#
Java
PHP
Ruby

_14
const VoiceResponse = require('twilio').twiml.VoiceResponse;
_14
_14
_14
const response = new VoiceResponse();
_14
const gather = response.gather({
_14
action: '/process_gather.php',
_14
method: 'GET'
_14
});
_14
gather.say('Enter something, or not');
_14
response.redirect({
_14
method: 'GET'
_14
}, '/process_gather.php?Digits=TIMEOUT');
_14
_14
console.log(response.toString());

Output

_10
<?xml version="1.0" encoding="UTF-8"?>
_10
<!-- page located at http://example.com/gather_hints.xml -->
_10
<Response>
_10
<Gather action="/process_gather.php" method="GET">
_10
<Say>Enter something, or not</Say>
_10
</Gather>
_10
<Redirect method="GET">
_10
/process_gather.php?Digits=TIMEOUT
_10
</Redirect>
_10
</Response>

With this code, Twilio will move to the next verb in the document (<Redirect>) when <Gather> times out. In our example, we instruct Twilio to make a new GET request to /process_gather.php?Digits=TIMEOUT


A few common problems users face when working with <Gather>:

Problem: <Gather> doesn't receive caller input when the caller is using a VoIP phone.

Solution: Some VoIP phones have trouble sending DTMF digits. This is usually because these phones use compressed bandwidth-conserving audio protocols that interfere with the transmission of the digit's signal. Consult your phone's documentation on DTMF problems.

Problem: Twilio does not send the Digits parameter to your <Gather> URL.

Solution: Check to ensure your application is not responding to the action URL with an HTTP 3xx redirect. Twilio will follow this redirect, but won't resend the Digits parameter.
If you encounter other issues with <Gather>, please reach out to our support team for assistance(link takes you to an external page).

Language appendix

languagetags page anchor

Click here to download a .csv file of all available languages(link takes you to an external page).

LanguageLanguage TagSupports enhanced modelSupports experimental models
Afrikaans (South Africa)af-ZANoNo
Albanian (Albania)sq-ALNoNo
Amharic (Ethiopia)am-ETNoNo
Arabic (Algeria)ar-DZNoYes
Arabic (Bahrain)ar-BHNoYes
Arabic (Egypt)ar-EGNoYes
Arabic (Iraq)ar-IQNoYes
Arabic (Israel)ar-ILNoYes
Arabic (Jordan)ar-JONoYes
Arabic (Kuwait)ar-KWNoYes
Arabic (Lebanon)ar-LBNoYes
Arabic (Mauritania)ar-MRNoYes
Arabic (Morocco)ar-MANoYes
Arabic (Oman)ar-OMNoYes
Arabic (Qatar)ar-QANoYes
Arabic (Saudi Arabia)ar-SANoYes
Arabic (State of Palestine)ar-PSNoYes
Arabic (Tunisia)ar-TNNoYes
Arabic (United Arab Emirates)ar-AENoYes
Arabic (Yemen)ar-YENoYes
Armenian (Armenia)hy-AMNoNo
Azerbaijani (Azerbaijani)az-AZNoNo
Basque (Spain)eu-ESNoNo
Bengali (Bangladesh)bn-BDNoNo
Bengali (India)bn-INNoNo
Bosnian (Bosnia and Herzgovina)bs-BANoNo
Bulgarian (Bulgaria)bg-BGNoNo
Burmese (Myanmar)my-MMNoNo
Catalan (Spain)ca-ESNoNo
Chinese, Cantonese (Traditional, Hong Kong)yue-Hant-HKNoNo
Chinese, Mandarin (Simplified, China)cmn-Hans-CNNoNo
Chinese, Mandarin (Simplified, Hong Kong)cmn-Hans-HKNoNo
Chinese, Mandarin (Traditional, Taiwan)cmn-Hant-TWNoNo
Croatian (Croatia)hr-HRNoNo
Czech (Czech Republic)cs-CZNoNo
Danish (Denmark)da-DKNoYes
Dutch (Netherlands)nl-NLNoYes
Dutch (Belgium)nl-BENoNo
English (Australia)en-AUNoYes
English (Canada)en-CANoNo
English (Ghana)en-GHNoNo
English (Hong Kong)en-HKNoNo
English (India)en-INNoYes
English (Ireland)en-IENoNo
English (Kenya)en-KENoNo
English (New Zealand)en-NZNoNo
English (Nigeria)en-NGNoNo
English (Pakistan)en-PKNoNo
English (Philippines)en-PHNoNo
English (Singapore)en-SGNoNo
English (South Africa)en-ZANoNo
English (Tanzania)en-TZNoNo
English (United Kingdom)en-GBYesYes
English (United States)en-USYesYes
Estonian (Estonia)et-EENoNo
Filipino (Philippines)fil-PHNoNo
Finnish (Finland)fi-FINoYes
French (Belgium)fr-BENoNo
French (Canada)fr-CANoYes
French (France)fr-FRYesYes
French (Switzerland)fr-CHYesNo
Galician (Spain)gl-ESNoNo
Georgian (Georgia)ka-GENoNo
German (Austria)de-ATNoNo
German (Germany)de-DENoYes
German (Switzerland)de-CHNoNo
Greek (Greece)el-GRNoNo
Gujarati (India)gu-INNoNo
Hebrew (Israel)he-ILNoNo
Hindi (India)hi-INNoYes
Hungarian (Hungary)hu-HUNoNo
Icelandic (Iceland)is-ISNoNo
Indonesian (Indonesia)id-IDNoNo
Italian (Italy)it-ITNoNo
Italian (Switzerland)it-CHNoNo
Japanese (Japan)ja-JPYesYes
Javanese (Indonesia)jv-IDNoNo
Kannada (India)kn-INNoNo
Kazakh (Kazakhistan)kk-KZNoNo
Khmer (Cambodian)km-KHNoNo
Korean (South Korea)ko-KRNoYes
Lao (Laos)lo-LANoNo
Latvian (Latvia)lv-LVNoNo
Lithuanian (Lithuania)lt-LTNoNo
Macedonian (North Macedonia)mk-MKNoYes
Malay (Malaysia)ms-MYNoNo
Malayalam (India)ml-INNoNo
Marathi (India)mr-INNoNo
Mongolian (Mongolia)mn-MNNoNo
Nepali (Nepal)ne-NPNoNo
Norwegian Bokmål (Norway)nb-NONoYes
Persian (Iran)fa-IRNoNo
Polish (Poland)pl-PLNoYes
Portuguese (Brazil)pt-BRNoYes
Portuguese (Portugal)pt-PTNoYes
Punjabi (Gurmukhi India)pa-guru-INNoNo
Romanian (Romania)ro-RONoYes
Russian (Russia)ru-RUYesYes
Serbian (Serbia)sr-RSNoNo
Sinhala (Sri Lanka)si-LKNoNo
Slovak (Slovakia)sk-SKNoNo
Slovenian (Slovenia)sl-SINoNo
Spanish (Argentina)es-ARNoNo
Spanish (Bolivia)es-BONoNo
Spanish (Chile)es-CLNoNo
Spanish (Colombia)es-CONoNo
Spanish (Costa Rica)es-CRNoNo
Spanish (Dominican Republic)es-DONoNo
Spanish (Ecuador)es-ECNoNo
Spanish (El Salvador)es-SVNoNo
Spanish (Guatemala)es-GTNoNo
Spanish (Honduras)es-HNNoNo
Spanish (Mexico)es-MXNoNo
Spanish (Nicaragua)es-NINoNo
Spanish (Panama)es-PANoNo
Spanish (Paraguay)es-PYNoNo
Spanish (Peru)es-PENoNo
Spanish (Puerto Rico)es-PRNoNo
Spanish (Spain)es-ESYesYes
Spanish (United States)es-USYesYes
Spanish (Uruguay)es-UYNoNo
Spanish (Venezuela)es-VENoNo
Sundanese (Indonesia)su-IDNoNo
Swahili (Kenya)sw-KENoNo
Swahili (Tanzania)sw-TZNoNo
Swedish (Sweden)sv-SENoNo
Tamil (India)ta-INNoNo
Tamil (Malaysia)ta-MYNoNo
Tamil (Singapore)ta-SGNoNo
Tamil (Sri Lanka)ta-LKNoNo
Telugu (India)te-INNoNo
Thai (Thailand)th-THNoYes
Turkish (Turkey)tr-TRNoYes
Ukrainian (Ukraine)uk-UANoYes
Urdu (India)ur-INNoNo
Urdu (Pakistan)ur-PKNoNo
Uzbek (Uzbekistan)uz-UZNoNo
Vietnamese (Vietnam)vi-VNNoYes
Zulu (South Africa)zu-ZANoNo

Rate this Page: