Commit | Line | Data |
565c0f31 |
1 | =head1 NAME |
2 | |
5c818114 |
3 | Reaction::Manual::Unicode - Unicode support in Reaction |
565c0f31 |
4 | |
5 | =head1 DESCRIPTION |
6 | |
7 | This document gives you notes about using Unicode in Reaction. |
8 | |
9 | =head1 Working with Catalyst |
10 | |
11 | Catalyst has a plugin which is named L<Catalyst::Plugin::Unicode>, It decodes |
12 | the request parameters to utf8 when preparing parameters, and decodes the |
13 | response body after the request is finalized. Since, Reaction uses utf8 by |
14 | default, and does this already. So, you should avoid using the |
15 | L<Catalyst::Plugin::Unicode>. |
16 | |
17 | =head1 Note about LayoutSet |
18 | |
19 | LayoutSet files B<MUST> be in utf8, since ASCII is a subset of utf8, You don't |
20 | need to worry about anything if you are using plain ASCII. But people who uses |
21 | CJK, must be sure to configure your editors to save files in utf8. |
22 | |
23 | =head1 Note about Database |
24 | |
25 | If you don't see the correct result. Be sure to double check the database |
26 | related configuration (connecting parameter or database server side config for |
27 | example). Database B<MUST> be configured to use utf8. Reaction won't decode or |
28 | encode anything. It just return the data as it is from database. |
29 | |
30 | =head1 SEE ALSO |
31 | |
32 | =over |
33 | |
34 | =item * L<Reaction::Manual> |
35 | |
36 | =item * L<utf8> |
37 | |
38 | =back |
39 | |
40 | =head1 AUTHORS |
41 | |
42 | See L<Reaction::Class> for authors. |
43 | |
44 | =head1 LICENSE |
45 | |
46 | See L<Reaction::Class> for the license. |
47 | |
48 | =cut |