OpenCms 6.0 documentation :: Encoding Test 5: JSP without 'content-encoding' or 'pageEncoding' set

OpenCms 6.0 interactive documentation:

Encoding Test 5: JSP without 'content-encoding' or 'pageEncoding' set

[Alkacon Documentation]

Flex examples 3

Contents

Exception: Cascade two levels

Exception: Cascade one level

Cascade: JSP top

Cascade: XML top

Cascade: JSP sub

Cascade: XML top (no JSP subelements)

Cascade: XML sub

Include: Tag usage variations

Encoding: default 'content-encoding'

Encoding: 'content-encoding' ISO-8859-1

Encoding: JSP with 'content-encoding' ISO-8859-1

Encoding: JSP with 'pageEncoding' UTF-8

* Encoding: JSP without encoding

Encoding: XML template with default encoding

Encoding: XML template with encoding 'UTF-8'

[Source of this page]


� � � 
� � � 
� � � 
+ + +

This page should display a set of german umlauts and plus signs.

Note: If you run OpenCms in a default encoding other then "ISO-8859-1",
this page actually might display garbage characters.
The reason for this is that neither the property content-encoding of the file is set,
nor has the <%@ page pageEncoding="..." %> JSP directive been used.
In this case the JSP will be written in the system default encoding to the disk, but
the JSP compiler (eg. Jasper) does not now about this because his default
is set to "ISO-8859-1". To avoid such problems, set this properties.