Changes for page UTF-8 Encoding Tips

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,10 +1,10 @@
1	1	= UTF-8 Encoding Tips =
2	2
3		-Encoding questions are asked frequently on the mailing list. This is just a collection of tips for using UTF-8. It's a checklist of sorts. Make sure you've done all the things specified here before pitching your computer into the ocean
	3	+Encoding questions are asked frequently on the mailing list. This is just a collection of tips for using UTF-8. It's a checklist of sorts. Make sure you've done all the things specified here before pitching your computer into the ocean :-)
4	4
5	5	== Check your database ==
6	6
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
	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	10
...	...	@@ -14,11 +14,11 @@
14	14
15	15	And setting your default charset and collation in your my.cnf file
16	16
17		-[[image:attach:options.png]]
	17	+[[image:options.png]]
18	18
19	19	== Fonts & CSS ==
20	20
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
	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	24
...	...	@@ -31,11 +31,11 @@
31	31
32	32	== Set eclipse encoding ==
33	33
34		-[[image:attach:preferences.png]]
	34	+[[image:preferences.png]]
35	35
36	36	== Use Project Wonder ==
37	37
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
	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	41
...	...	@@ -55,9 +55,9 @@
55	55
56	56	{{/noformat}}
57	57
58		-== Localizable strings should be in UTF-16! ==
	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.
	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.
61	61
62	62	== Build your files in UTF-8. ==
63	63