[TYPO3-english] RealUrl: enableAllUnicodeLetters VS. specCharsToASCII

Christian Hennecke christian.hennecke at wunderknaben.com
Mon Oct 22 14:16:08 CEST 2012


Am 22.10.2012 13:25, schrieb Stephan Schuler:

Hi Stephan,

> For a site with several languages (such as Chinese, Korean, Polish,
> German and English) I enabled enableAllUnicodeLetters to have urls
> reflecting the real page names. Especially for Chinese and Korean
> this is relevant, because there is no ASCII-mapping table for those
> languages.
>
> When it comes to e.g. Russian or Polish where a ASCII mapping table
> exists, this kind of conflicts with enableAllUnicodeLetters because
> page titles are translated to ASCII strings instead of using the
> url_encoded version of the page title.

[snip]

> Am I the only one being confused why those there’s this kind of
> inconsistent behavior?
>
> I would use the specCharsToASCII only if enableAllUnicodeLetters is
> set. Or do I miss something?
>
> What about all the other multi language guys, especially from
> Thailand? How do you handle speaking urls?

I've never been able to get Chinese URLs to work properly, even with 
enableAllUnicodeLetters enabled. Instead I'm using the 
languageExceptionUid statement to fall back to English URLs.

Cheers,
Christian


More information about the TYPO3-english mailing list