Bug 38119 - I18N - examples setup only for en encoding/charset
Summary: I18N - examples setup only for en encoding/charset
Status: RESOLVED WORKSFORME
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Webapps:Examples (show other bugs)
Version: 5.5.9
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-04 16:21 UTC by Radko Najman
Modified: 2006-12-25 05:12 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Radko Najman 2006-01-04 16:21:09 UTC
JSP files in Tomcat examples should have set encoding to UTF-8 (<%@page
pageEncoding="UTF-8"%>). This will help the the users, who want to modify the
sources, to add multibyte characters. If pageEncoging is not set default
iso-8859-1 is used and multibytes characters are not shown correctly.
Comment 1 Yoav Shapira 2006-12-25 05:12:48 UTC
I actually like using the SetCharacterEncoding filter for this purpose: it's
cleaner (modify one file, web.xml, instead of every JSP) and thus serves as a
better example by showing the power of filters.  The SetCharacterEncoding filter
ships with the Tomcat examples: no coding is needed.  It's even pre-defined for
you in the exmaples web.xml, you just need to comment in the filter-mapping
element (and pick the encoding you want, e.g. UTF-8 in your case).