Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Include the slug transliteration plugin into the core of GS
#17
Zegnåt Wrote:
yojoe Wrote:
mvlcek Wrote:include two strings TRANSLIT_FROM and TRANSLIT_TO in the language files and don't need to define an extra array.
This makes customization much easier and uses the standard i18n features of GetSimple:
Code:
...
'TRANSLIT_FROM' => 'äöüÄÖÜ',
'TRANSLIT_TO' => 'aouAOU',
...
It also disables some languages from using the transliteration function. Japanese, Korean, Chinese, et al. come to mind. These languages need multiple Latin characters per symbol, which is impossible when you are just matching 2 strings.

These strings would be UTF-8, thus all languages are supported. The transliteration function would need to split the string with mb_substr (or similar) to create the arrays needed for strtr (or whatever). As this splitting is only done when saving pages, there is no performance hit.
I18N, I18N Search, I18N Gallery, I18N Special Pages - essential plugins for multi-language sites.


Messages In This Thread
Include the slug transliteration plugin into the core of GS - by mvlcek - 2011-06-15, 03:47:52



Users browsing this thread: 1 Guest(s)