• View
• Edit
• History
• Print
• Backlinks

UTF-8

Summary: Enabling UTF-8 Unicode language encoding in your wiki.

UTF-8 supports all languages and alphabets, including Asian languages and their character depth. It is a widely supported and flexible character encoding.

It's fairly simple to enable UTF-8 on your wiki pages. Current Pm Wiki versions have the UTF-8 file which is enabled by default in the sample-config.php.

Enabling UTF-8 on a new wiki

If you start a new wiki in any language with the latest Pm Wiki version, it is highly recommended to enable UTF-8. In the future, Pm Wiki will change to use the UTF-8 encoding by default, so if you already use it, you will not need a complex "migration" to UTF-8 later.

To enable UTF-8 for a new wiki, add this line near the beginning of config.php (the docs/sample-config.php file has this line already):

include_once("scripts/xlpage-utf-8.php");

This line should come before a call to the XL Page?() function in international wikis.

Save your config.php file encoded as UTF-8 (NO BOM). That allows entry of UTF-8 encoded characters in it. Make sure your editor does support this, and test by adding some non-ANSI UTF-8 characters, to see them in the text editor ¹.

With UTF-8 thus enabled you also got use of classes rtl and ltr, which offer setting of the text direction to right-to-left, or left-to-right. This is useful for inclusion of right-to-left scripts like Arabic, Farsi (Persian), Hebrew, Urdu and others.

Enabling UTF-8 on existing wikis

Currently, this is possible only if your group and page names, as well as upload names, don't contain international characters. The names of wiki pages are used as file names, and we don't have yet an easy way to rename the disk files.

If your wiki doesn't have international page/file names, first upgrade to the latest Pm Wiki version. To enable UTF-8, add these lines near the beginning of config.php:

include_once("scripts/xlpage-utf-8.php"); $DefaultPageCharset = array(''=>'ISO-8859-1'); # see below

These lines should come before a call to the XL Page?() function in international wikis.

The $DefaultPageCharset line is there to fix and correctly handle some pages with missing or wrong attributes, created by older Pm Wiki versions.

• Most wikis in European languages are likely to be in the ISO-8859-1 encoding and should use:
  $DefaultPageCharset = array(''=>'ISO-8859-1');
• Wikis in Czech and Hungarian language are likely to be in the ISO-8859-2 encoding, they should use this line instead:
  $DefaultPageCharset = array(''=>'ISO-8859-2', 'ISO-8859-1'=>'ISO-8859-2');
• Wikis in Turkish language are likely to be in the ISO-8859-9 encoding, they should use this line instead:
  $DefaultPageCharset = array(''=>'ISO-8859-9', 'ISO-8859-1'=>'ISO-8859-9');

You should also delete the file wiki.d/.pageindex. This file contains a cache of links and words from your pages and is used for searches and pagelists. Pm Wiki will rebuild it automatically with the new encoding.

Support for RTL right-to-left languages

Languages like Arabic, Hebrew, Farsi (Persian), Urdu and others are written in script flowing from right to left. Classes rtl and ltr can be used to specify direction of text independently of the general text direction within a page, for example:

>>rtl<<
يتدفق هذا النص من اليمين إلى اليسار
>>ltr<<
This text flows left to right.
>><<

To set text direction for a wiki generally to RTL, you could add to config.php a line like:

$HTMLStylesFmt['rtl'] = " body { direction:rtl; }"

but the skin you use may need other modifications, for instance to swap the search box and the page actions to the other side etc.

Some skins have full support for RTL, see for instance Amber.

Notes

• You need to save your config.php file in the UTF-8 encoding, and "Without Byte Order Mark (BOM)". See Character encoding of config.php.
• This page concerns the most recent versions of Pm Wiki. See Cookbook:UTF-8 for tips on older versions.
• In the case your Pm Wiki installation displays wrong encoding, or save an UTF-8 page to an other encoding without explanation, you can double check your custom .htaccess settings at the root of your served pages.