Work in progress
This chapter is still being constructed...
Generally speaking, if you try and add Unicode characters such as umlauts into templates, you may well come across display issues. This is easily fixable, but requires one of the following:
For the template cfm file to be saved in the correct encoding for the language being displayed
Or use of the cfprocessingdirective
tag to set pageEncoding
Incorrect encoding example
Correct encoding
Likewise, umlauts in routes would need for the config/routes.cfm
file to have the correct encoding:
If you're actively trying to avoid the use of cfprocessingdirective
, you can resave the template or route file with UTF-8-BOM
. Your local text editor should provide this facility; here's an example in Notepad++ (windows)
// Example using monthNames args in dateSelect() Coming soon