There are a number of considerations for deploying CAS in a locale other than en-US, some of which are discussed here.
The Localization page describes how to switch from the default en-US locale to any of a number of supported locales, as well as instructions for adding support for a locale not provided out of the box.
Supporting character sets other than ASCII will be a primary concern for many international deployments. The following steps are required to support end-to-end UTF-8 character set encoding in CAS.
Ensure pageEncoding of all JSP views is UTF-8. (This is the default for most if not all views packaged with CAS)
Ensure the Content-Type header specifies UTF-8 encoding:
- Set the character set encoding to UTF-8 for both the request and response as early in the processing stage as possible. The most convenient solution for this is defining a servlet filter that sets
HttpServletResponse#setCharacterEncoding() to UTF-8. Recent versions of CAS provide this functionality by default using