Skip to Content

Changes for page UTF-8 Encoding Tips

Last modified by Ray Kiddy on 2022/01/11 21:36
From version 7.1
edited by Antoine Berry
on 2012/09/20 10:32
Change comment: Migrated to Confluence 4.0
To version 19.1
edited by Ramsey Gurley
on 2013/06/12 13:30
Change comment: Migrated to Confluence 5.3

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.aberry
1 +XWiki.ramsey
Content
... ... @@ -7,7 +7,6 @@
7 7  The database needs to be storing values in UTF-8. If it isn't, then all your effort is wasted. For example, on MySQL that means a db url like
8 8  
9 9  {{noformat}}
10 -
11 11  jdbc:mysql://localhost/Example?capitalizeTypenames=true&zeroDateTimeBehavior=convertToNull&useUnicode=true&characterEncoding=UTF-8
12 12  
13 13  {{/noformat}}
... ... @@ -21,7 +21,6 @@
21 21  Different fonts may not have all the characters to display the different characters. If you're using a default stylesheet, then the browsers may be displaying differently simply because of fonts. Speaking of stylesheets, you probably want to encode that in UTF-8 also. Start your stylesheet with something like
22 22  
23 23  {{noformat}}
24 -
25 25  @charset "UTF-8";
26 26  @import url("reset.css");
27 27  
... ... @@ -38,7 +38,6 @@
38 38  I think this goes without saying but: **Use Wonder**. Set encoding in the properties file. Notice it is UTF-8 with a hyphen. It it always UTF-8 with a hyphen... well, except with the MySQL image above because they excel in doing things differently
39 39  
40 40  {{noformat}}
41 -
42 42  # Project Encoding
43 43  er.extensions.ERXApplication.DefaultEncoding=UTF-8
44 44  
... ... @@ -47,7 +47,6 @@
47 47  == Set encoding in your page wrapper ==
48 48  
49 49  {{noformat}}
50 -
51 51  <?xml version="1.0" encoding="UTF-8" standalone="no"?>
52 52  <!DOCTYPE html PUBLIC
53 53   "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN"
... ... @@ -57,7 +57,7 @@
57 57  
58 58  == Localizable strings should be in UTF-16! ==
59 59  
60 -Localizable.strings should be encoded in UTF-16. The localizer can detect UTF-16 without error, where it can confuse UTF-8 with other encodings. Pascal says use UTF-16LE if you want to be explicit about things... Especially if you are editing your strings files in an external editor like BBEdit or whatnot. I use the eclipse editor and UTF-16 myself and all seems to work fine for me. So to each his own.
56 +Localizable.strings should be encoded in UTF-16. The localizer can detect UTF-16 without error, where it can confuse UTF-8 with other encodings. Specifically, you should be using UTF-16 BE with no BOM if you are using an external text editor instead of eclipse.
61 61  
62 62  == Build your files in UTF-8. ==
63 63  
... ... @@ -64,7 +64,6 @@
64 64  If you have some special characters in your code (like '€' for exemple), then you will need to specify which encoding you want when you build your application. To do that, you have to modify your "build.xml" file by adding the property "encoding="utf-8" into your <wocompile> statement.
65 65  
66 66  {{code language="xml"}}
67 -
68 68  <wocompile srcdir="Sources" destdir="bin" encoding="utf-8">
69 69  
70 70  {{/code}}