The built-in field types and grammars for Japanese are listed here.
Element | Implementation details |
---|---|
boolean | Users can say positive responses such as , ok, and or negative responses such as and . Users can also provide DTMF input: 1 is yes, and 2 is no. The return value sent is a boolean
true or false. If the field name is subsequently used in a value attribute
within a prompt, the TTS engine will speak . |
currency | Users can say Japanese currency values in “yen”
from 0 to 999,999,999,999. Users can also provide DTMF input using the numbers 0 through 9 and must terminate DTMF entry using the # key. The return value sent is a string in the format UUUdddddddd.cc, where UUU is a currency indicator; currently the only supported currency type is JPY (for Japanese yen.) If the field name is subsequently used in a value attribute within a prompt, the TTS engine will speak the currency value. In DTMF input's case, only input digits are returned. |
date | Users can say a date using months, days, and years,
as well as the words , , and . Common constructs such as “ ” are supported. Users can also provide DTMF input in the form yyyymmdd. Note: The
date grammar does not perform leap year calculations.
is accepted as a valid date regardless of the year. If desired, your application or servlet can perform the required calculations. The return value sent is a string in the format yyyymmdd, with the VoiceXML browser returning a ? in any positions omitted in spoken input. If the value is subsequently spoken in <say-as> with the interpret-as value vxml:date, then it is spoken as a date appropriate to this language. |
digits | Users can say numeric integer values as individual
digits (0 through 9). For example, a user could say 123456 as “1 2
3 4 5 6.” Users can also provide DTMF input using the numbers 0 through 9, and must terminate DTMF entry using the # key. The return value sent is a string of one or more digits. If the result is subsequently used in <say-as> with the interpret-as value vxml:digits, it will be spoken as a sequence of digits appropriate to the current language. In the above example, the TTS engine speaks 123456 as 1 2 3 4 5 6. Note: Use this type instead of the number type
if you require very high recognition accuracy for your numeric input.
|
number | Users can say natural numbers (that is, positive
and negative integers and decimals) from 0 to 999,999,999,999 as well
as the words (to indicate a decimal point) and (to indicate a negative number). Users can also provide DTMF input using the numbers 0 through 9 and optionally the * key (to indicate a decimal point), and must terminate DTMF entry using the # key. Note: Only positive
numbers can be entered using DTMF.
The return value sent
is a string of one or more digits, 0 through 9, with a decimal point
and a + or - sign as applicable. If the field is subsequently spoken
in <say-as> with the interpret-as value vxml:type,
where type is the type number you want to specify, then it is spoken
as that type number appropriate to this language. The TTS engine
speaks 123456 as Use <say-as interpret-as="vxml:digit"> to have the number said as a string of digits. |
phone | Users can say a telephone number, in 10 or 11 digits,
including the first digit “0”. Users can also provide DTMF input using the numbers 0 through 9 and optionally the * key (to represent the “extension”), and must terminate DTMF entry using the # key. The return value sent is a string of digits without hyphens. The return value sent includes an x if an extension was specified in DTMF input's case. If the field is subsequently spoken in <say-as> with the interpret-as value vxml:phone, then it is spoken as a phone number appropriate to this language. Note: For
tips on minimizing recognition errors that are due to user pauses
during input, see Using the built-in phone grammar.
|
time | Users can say a time of day using hours and minutes
in either 12- or 24-hour format, as well as the word . Users can also provide DTMF input using the numbers 0 through 9. The return value sent is a string in the format hhmmx, where x is a for a.m., p for p.m., h for 24 hour format, or ? if unspecified or ambiguous; for DTMF input, the return value will always be h or ?, since there is no mechanism for specifying a.m. or p.m. If the field is subsequently spoken in <say-as> with the interpret-as value vxml:time, then it is spoken as a time appropriate to this language. |