Hi, As roller user guide statements the i18n support, there are some problems related to i18n in 3.0 development branch. Hope these problems can be resolved before RC1 release. 1. Browser show chaotic outputs when using local cached pages if the page contains multi-byte chars I don't know why the info removed from the themes template file. But I know the removal do cause trouble when roller using in a multi-byte charset environment. Without the meta info, the browser can show the page correctly when if it is send back from the server directly. The browser can get encoding indication from the HTTP response content-Type header. When the browser show the same GET response later, it use the local cached page, hence there is no HTTP content-Type header. If the meta info is also missing, the browser will know nothing about the actual page encoding. The browser may guess the page encoding as local codepage such as GB18030, Shift-JIS, etc (depending on the OS and browser environment), leading chaotic outputs. I've filed a JIRA issue (ROL1226) and attached a patch file for reference 2. The velocity template file i18n support problem Following the roller's design, the velocity template file should be utf-8 encoded. But the ThemeManagerImpl class read the template files simply using FileReader, which use default encoding( various depend on the deployment OS environment ). And an implied defect exists: The code assumes the characters contained in the file equals to the byte count of the file size, which is not true in multi-byte environments. The attached patch file http://www.nabble.com/user-files/235894/patch.txt patch.txt can solve this problem.
Regards, Miles. -- View this message in context: http://www.nabble.com/Roller-3.0-i18n-support-problems-tf2231883s12275.html#a6186459 Sent from the Roller - Dev forum at Nabble.com.
