[TYPO3-english] RealUrl: enableAllUnicodeLetters VS. specCharsToASCII

[Stephan Schuler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Christian.


Thank you for your response.
But Chinese is working just fine currently. It's the Russian urls that aren't the way I want them.

I expected the "enableAllUnicodeLetters" flag to use the Unicode letters wherever possible. But currently they're only used for those languages that don't come with ASCII character mapping.

Essentially, I want the site to behave consistent through all languages. But additionally, I don't want to have all English page titles but original ones.
So, using the "languageExceptionUid" flag doesn't match my customers needs, unfortunately.


Regards,


Stephan Schuler
Web-Entwickler

Telefon: +49 (911) 539909 - 0
E-Mail: Stephan.Schuler at netlogix.de
Website: media.netlogix.de


- --
netlogix GmbH & Co. KG
IT-Services | IT-Training | Media
Andernacher Straße 53 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: info at netlogix.de | Internet: http://www.netlogix.de

netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
Umsatzsteuer-Identifikationsnummer: DE 233472254
Geschäftsführer: Stefan Buchta, Matthias Schmidt



- -----Ursprüngliche Nachricht-----
Von: typo3-english-bounces at lists.typo3.org [mailto:typo3-english-bounces at lists.typo3.org] Im Auftrag von Christian Hennecke
Gesendet: Montag, 22. Oktober 2012 14:16
An: typo3-english at lists.typo3.org
Betreff: Re: [TYPO3-english] RealUrl: enableAllUnicodeLetters VS. specCharsToASCII

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
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 3.2.1 (Build 4869)
Charset: utf-8

wpUDBQFQhUa5pp0IwsibV8MBCDbmA/40p+4ij+2wNUv5gJFQsh66oDGJpFNEG8PZ
Bfg/mqmmQj1PjaaNxf+RTVHyG8alUM8wtrMyrlACDetc/KzXmfbEWrd5ncD54yNI
JGt2IohkiPmyhy5jlpTNEeybZQLOIw3ftLV93mLP58+rU9uAVf9v+cOzNTpReg3y
zJ5JCKNgsg==
=YCei
-----END PGP SIGNATURE-----