Speak the language
For an RDC, the aritfacts affected by internationalization from a VUI perspective are its grammars and prompts.
Components pull in the required grammars and prompts from resource bundles. These are found in the <rdc-home-dir>/src/org/apache/taglibs/rdc/resources directory. The first step to using RDCs in a locale of your choice is to check if the appropriate resource bundle is available. If its isn't, you will need to translate the artifacts you want to use and provide the appropriate resouce bundle.
If no action is taken by the application author, the default locale is en-US.
The locale can be set on a per application deployment basis and overridden on a per component basis. To set the locale for all RDCs within an application, define the language, country and variant init params as needed, for the RDCFilter within your application deployment descriptor, such as:
<filter>
<filter-name>RDCFilter</filter-name>
<filter-class>org.apache.taglibs.rdc.RDCFilter</filter-class>
<init-param>
<param-name>language</param-name>
<param-value>en</param-value>
</init-param>
<init-param>
<param-name>country</param-name>
<param-value>US</param-value>
</init-param>
<init-param>
<param-name>variant</param-name>
<param-value>IBM</param-value>
</init-param>
</filter>It is recommended that the variant be used the define the speech application deployment platform (in the above example, the variant IBM is used for deployment on WVR/WVS).
Further, it is possible for an individual RDC to override the locale set via the application deployment descriptor. This is done by specifying the locale via the locale tag attribute of that component, as shown below:
<rdc:date id="myDate" locale="fr-CA" />
The above instance overrides the locale specified using the application deployment descriptor, if such a locale has been specified. This also means it is possible to host RDCs using different locales within the same JSP.