Zhang Weiwu - 2010-08-28

This issue is a bit complicated.

- there is no encoding convert in singapore, so only when filesystem encoding is the same as langauge charset that the webpage (with both filenames and UI) doesn't produce junk text.

I am doing:
- if there is no mbstring features, the system work as is, the old way.
- if there is mbstring feature,
1 adding configuration parameter default_encoding for encoding of filesystem encoding.
2 convert both language translation encoding (A) and file system encoding (B) to UTF-8 in the final page output.
so that always output page content in UTF-8
3 remove "default_charset" option in configuration to avoid confusion. It is not needed anyway because all languages define their charset.

Today on my local copy. I just did 1, 2.A. TODO: 2.B and 3