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 cfprocessingdirective tag to set pageEncoding
Using cfprocessingdirective
/views/main/example.cfm
<h1>Über uns</h1>
​
​
​
Incorrect encoding example
/views/main/example.cfm
<cfprocessingdirective pageEncoding="utf-8">
<h1>Über uns</h1>
​
​
​
Correct encoding
Likewise, umlauts in routes would need for the config/routes.cfm file to have the correct encoding:
config/routes.cfm
<cfprocessingdirective pageEncoding="utf-8">
<cfscript>
    mapper()
        .get(name="about", pattern="/über-uns", to="pages##about")
        .root(to="wheels##wheels", method="get")
    .end();
</cfscript>
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

Displaying Views to Users - Previous

Creating Custom View Helpers

Next - Database Interaction Through Models

Object Relational Mapping

Last modified 4mo ago

Export as PDF

Copy link

Edit on GitHub

Outline

Page Encoding Issues

Using cfprocessingdirective

Using file encoding

Localizing CFWheels Helpers