Supporting translation in our CMS - Charsets are now all utf-8
Complex characters such as those in Japanese, Korean and Arabic require more memory in order to be stored in a database and displayed on the screen. Behind the scenes all our documents are encoded with some kind of standardized format based on how many and which characters the document contains. See more about character encoding on wikipedia.
When implementing internationalized features into software, most developers choose the UTF-8 charset aka unicode. Our CMS was previously storing all the data in latin-1 charset. As of right now, our database and web pages fully support UTF-8.
We still need to continue modifying our applications to take advantage of this and to support alternate versions of text for pages / error message / forms, etc.
For now, below is a live demo of this blog page (generated by our CMS) showing the same text in different languages. Translations courtesy of Google Translate.
Our web sites support other languages.
웹 사이트는 다른 언어를 지원합니다.
مواقع على شبكة الإنترنت دعم لغات أخرى.
Bookmark & Share
Popular tags on this blogPerformance |
Most Popular Articles
- Mass virtual hosting security tip when using a reverse proxy to connect to other servers
- Solution for MariaDB Field 'xxx' doesn't have a default value
- How to lock Windows immediately upon smart card removal
- Stop using sleep mode with Windows Bitlocker for better security. Learn how to use hibernate in Windows 8.
- Is Google Public DNS actually better then your ISP?
- Planning a system to visually create responsive data-driven web page layouts & widgets in the Jetendo CMS browser interface
- Pros and Cons of CFML vs PHP and other languages
- Run Windows Guest in CentOS 6 Linux Host using Virtualbox 4 via the command line