Fixed Non-English letters are not lowercasing in URLs.

[Cenk]

Example:

threads/turkish-test-ĞğÜüŞşİıÖöÇç.4816/


It should be:

threads/turkish-test-ğğüüşşiıööçç.4816/

 

[Vincent]

Example:

threads/turkish-test-ĞğÜüŞşİıÖöÇç.4816/


It should be:

threads/turkish-test-ğğüüşşiıööçç.4816/

I'm not into SEO and stuff, but is this to optimize SEO?

 

[Cezz]

I'm not into SEO and stuff, but is this to optimize SEO?

It is about URL normalization, URL's as standard should all be lowercase as well as many other things...

http://en.wikipedia.org/wiki/URL_normalization

 

[Shadab]

Any reason why strtr was chosen over something like utf8_strtolower, for lowercasing the content titles?
(I really hope it wasn't for performance reasons).

 

[Mike]

strtr is actually faster, but it was mostly related to the fact that strtolower respects locales, and we don't want that. I am concerned about the performance of utf8_strtolower (without the mb version), though I haven't done any explicit tests. The link builders can be called a large number of times on a page.

 

[Shadab]

utf8_strtolower (without the mb version)

Definitely slower. I had wrongly assumed that those utf8 helper functions didn't utilize any mbstring functions. I just did a quick profiling and it turns out utf8_strtolower is almost 3 times slower when there are no mbstring functions available to it.

mbstring:

​

No mbstring:

​

 

[Nickolas]

You can modify the UTF-8 Library accent array. Create a plugin and try following code...

        global $UTF8_LOWER_ACCENTS, $UTF8_UPPER_ACCENTS;

        $UTF8_LOWER_ACCENTS = array_merge($UTF8_LOWER_ACCENTS, array(
            'ı' => 'i',
            'ü' => 'u',
            'ö' => 'o'
        ));

        $UTF8_UPPER_ACCENTS = array_merge($UTF8_UPPER_ACCENTS, array(
            'İ' => 'I',
            'Ü' => 'U',
            'Ö' => 'O'
        ));

and you must know that the URL romanization must be active.

And I think you have to override this code:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = false)

replace with:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = true)

 

[James Freeman]

You can modify the UTF-8 Library accent array. Create a plugin and try following code...

        global $UTF8_LOWER_ACCENTS, $UTF8_UPPER_ACCENTS;

        $UTF8_LOWER_ACCENTS = array_merge($UTF8_LOWER_ACCENTS, array(
            'ı' => 'i',
            'ü' => 'u',
            'ö' => 'o'
        ));

        $UTF8_UPPER_ACCENTS = array_merge($UTF8_UPPER_ACCENTS, array(
            'İ' => 'I',
            'Ü' => 'U',
            'Ö' => 'O'
        ));

and you must know that the URL romanization must be active.

And I think you have to override this code:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = false)

replace with:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = true)

Wouldn't that take away meaning to the word. It would be like saying "kat" for "cat" (just an example) I might be wrong there, and the URL is a extremely vital tool for search engines.

 

[James]

and the URL is a extremely vital tool for search engines.

Not exactly. Search engines care more about content than URLs. We had this discussion earlier about the weight of keywords in URLs, and there isn't much weight in them.

 

[yavuz]

You can modify the UTF-8 Library accent array. Create a plugin and try following code...

        global $UTF8_LOWER_ACCENTS, $UTF8_UPPER_ACCENTS;

        $UTF8_LOWER_ACCENTS = array_merge($UTF8_LOWER_ACCENTS, array(
            'ı' => 'i',
            'ü' => 'u',
            'ö' => 'o'
        ));

        $UTF8_UPPER_ACCENTS = array_merge($UTF8_UPPER_ACCENTS, array(
            'İ' => 'I',
            'Ü' => 'U',
            'Ö' => 'O'
        ));

and you must know that the URL romanization must be active.

And I think you have to override this code:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = false)

replace with:

public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = true)

Can someone put a plugin together that accomplish this?

 

[Nickolas]

Wouldn't that take away meaning to the word. It would be like saying "kat" for "cat" (just an example) I might be wrong there, and the URL is a extremely vital tool for search engines.

well yes... That solution not work for every language. But works for Turkish Language... That 's why, I wrote that code.

 

[dbembibre]

I have problems with spanish accents too, this works ? any way to remove non utf-8 from URL ?

 

[Jarod]

Hello,


Same with french accents : ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõöøùúûýýþÿ

 

[agison]

Same with Vietnamese accents. We need to replace all Vietnamese accents with english characters.
a á à ã ă â e é è ê i í ì ĩ o ó ò õ ô ơ u ú ù ũ ư y ý ỳ đ
to:
a a a a a a e e e e i i i i o o o o o o u u u u u y y y d

 

[Stemis]

Have you tried to solve in this way.

 

[agison]

Have you tried to solve in this way.

We knew it and this is a suggestion. New version of Xenforo should have this feature in it's Core.

 

[FabioCesar]

Same with Portugues-Br

 

[FabioCesar]

resolved:

After several attempts, enabled the romanization .. and it worked perfectly .. removed all the special characters ...

Edit library/Xenforo/Link.php

change this
public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = false)

to this
public static function buildIntegerAndTitleUrlComponent($integer, $title = '', $romanize = true)

 

[Mike]

1.2 now exposes options for Romanizing titles in URLs. (And it caches the work to be more efficient so, while it will have performance overhead, hopefully it will be mitigated where possible.)