[TYPO3-english] RealUrl: enableAllUnicodeLetters VS. specCharsToASCII

Stephan Schuler Stephan.Schuler at netlogix.de
Mon Oct 22 16:13:44 CEST 2012


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

Hi Dimitry.


Thank you for your answer. As both, a native Russian person and the RealURL guy, your personal comment is exactly what I need.


> Many browsers still show Cyrillic characters as % signs but transliteration is known to everybody and widely acceptable.
That's a good point. I just tried it with German and English Firefox and Chrome browsers (which are fine) and German IE (which is not). But I thought a native Russian IE would do better than the German one. If you know several browsers not acting well with the %-characters, I suggest my customer to skip native urls wherever possible.

> Just keep English letters for Russian. This is more consistent and does not force your readers to switch from language to language when they look at the address bar.
Of course, the content of my Russian pages are all Cyrillic letters, too. So using transliterated URLs is the thing making my readers require to switch languages.


But those two points together make me feel a bit uncomfortable about Chinese and Japanese URLs. There I have all Japanese and Chinese content on my pages and Japanese and Chinese page titles as well. But there's no usable transliteration for those languages, so I'm forced to use "something else".
Without using "enableAllUnicodeLetters" (and without using the "languageExceptionUids" fallback as well) my Chinese and Japanese URLs are mostly empty strings. But using "enableAllUnicodeLetters" drives me into your first problem ("the %-signs of some browsers"), not using it but using "languageExceptionUids" drives me into your second problem ("users are forced to switch languages when switching between content an address bar").

So, what's your suggestion about Chinese and Japanese? Do you prefer using the %-sign-urls with "enableAllUnicodeLetters" (even if that looks ugly in some browsers) or do you prefer using English URLs (even if that requires readers to switch languages)?


This, btw, is concerned to my ticket #41363 on forge.


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 Dmitry Dulepov
Gesendet: Montag, 22. Oktober 2012 15:48
An: typo3-english at lists.typo3.org
Betreff: Re: [TYPO3-english] RealUrl: enableAllUnicodeLetters VS. specCharsToASCII

Hi!

Stephan Schuler wrote:
> ·         The Russian page path gets transformed to “produkty-reshenija” because of specCharsToASCII. This is not what I want. Because of having enableAllUnicodeLetters set, I would like to have the url_encoded version of the original page title here, too.

As a native Russian person, I would not recommend mixing those two. You should use Cyrillic domain name of you want Cyrillic segments. Many browsers still show Cyrillic characters as % signs but transliteration is known to everybody and widely acceptable. Both Google and Yandex know very well how to transliterate back and give the same weight to any of these titles.

Just keep English letters for Russian. This is more consistent and does not force your readers to switch from language to language when they look at the address bar.

This is just a personal opinion, of course.

- --
Dmitry Dulepov

Simplicity will save the world.

_______________________________________________
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

wpUDBQFQhVTEpp0IwsibV8MBCI+6A/9BPGUnjVJwb8/EYADBPmBjM/z6H0ADWN/V
mP6nU4DA1RVs7keWQ4LmdzMrefKPgYKLz+iaaDx+mtVvy4zUD6QaOV6hni5Hyo0g
yNMFZDUTJomMqRm95x1G0ckfGLEiY5e4YJejB9yM3QkLvYo5j8d7QY9OQCTMWDA9
XGE8qxVAOQ==
=V80V
-----END PGP SIGNATURE-----


More information about the TYPO3-english mailing list