INTRODUCTION
Command Line Tools
Working with CFWheels
Handling Requests with Controllers
Displaying Views to Users
Database Interaction Through Models
External Links
Localization
Work in progress
This chapter is still being constructed...
Page Encoding Issues
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
cfprocessingdirectivetag to setpageEncoding
Using cfprocessingdirective
/views/main/example.cfm
1
<h1>Ãœber uns</h1>
Copied!
​
​​
Incorrect encoding example
/views/main/example.cfm
1
<cfprocessingdirective pageEncoding="utf-8">
2
<h1>Ãœber uns</h1>
Copied!
​
​​
Correct encoding
Likewise, umlauts in routes would need for the
config/routes.cfm file to have the correct encoding:config/routes.cfm
1
<cfprocessingdirective pageEncoding="utf-8">
2
<cfscript>
3
mapper()
4
.get(name="about", pattern="/über-uns", to="pages##about")
5
.root(to="wheels##wheels", method="get")
6
.end();
7
</cfscript>
Copied!
Using file 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)​
​​
Localizing CFWheels Helpers
// Example using monthNames args in dateSelect()
Coming soon
Export as PDF
Copy link
Edit on GitHub