Basic configuration for Cyrillic support
How to configure Foswiki 1.1.2 to support Russian language (WikiWords, URLs, etc.)?
I got Foswiki to understand Russian language with the following configuration:
The following is set up in foswiki/bin/configure
Internationalisation -> Languages:
{UserInterfaceInternationalisation} = 1
{Languages}{ru}{Enabled} = 1
Internationalisation -> Locale:
{UseLocale} = 0
{Site}{Locale} = ru_RU.utf8
{Site}{CharSet} = windows-1251
{Site}{LocaleRegexes} = 1
{UpperNational} = ÀÁÂÃÄŨÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖרÙÚÛÜÝÞß
{LowerNational} = àáâãä叿çèéêëìíîïðñòóôõö÷øùúûüýþÿ
Such configuration makes correct creation of
WikiWords as topic names in Cyrillic and proper linking of
WikiWords in Cyrillic. But still there are some issues. E.g., when you attach a file with Cyrillic name and force to create a link, Foswiki automatically creates an encoded link, so that the name of the file is not readable (like foswiki/pub/Sandbox/%d2%e5%f1%f2%ee%e2%e0%ff%d1%f2%e0%f2%fc%ff1/%d0%e5%e3%e8%f1%f2%f0%e0%f6%e8%ff.txt)
In this case you should use
%ATTACHURL%/%ENCODE{"file_name.txt"}%: comment
Bugs with WysiwygPlugin and TinyMCEPlugin
Due to the encoding of the topics and webs names,
WysiwygPlugin and
TinyMCEPlugin don't provide available insert links when you Manage Attachments as there is no attachments to the topic (it is discussed in
Foswikitask:Item9973 ) and attachments are not uploaded correctly. Current release of
WysiwygPlugin (1.1.1) and
TinyMCEPlugin (1.1.7) fix these problems, but still when you insert a link to the file with name in Cyrillic it appears to be broken. You still need to use %ENCODE{""}% macro.
--
IlyaEremeev
Thank you for this
FAQ!
For those who are interested, we need to get
Tasks.Item10230 fixed so that WYSIWYG works properly for international filenames. Patches welcome. Add your name to that task if you want to help with testing (I don't have any changes needing testing yet, however).
--
PaulHarvey - 09 Apr 2011
I would recommend using UTF-8 rather than windows-1251. UTF-8 is a global standard that supports all the characters that windows-1251 does.
See also:
InternationalizationSupplement
--
CrawfordCurrie - 03 Oct 2011