Fixed 🐛 with Turkish characters such as ö and ü

[ehd]

Thanks for preserving our German Umlaut-romanisation!

 

[Baby Community]

https://xentr.net/resources/xtr-seo-uyumlu-url-ve-link-yapisi.7/

@onurhans53 this is the addon you need

 

[ge66]

Thank you, tested swedish å ä and they also work as ö does.

 

[Onurhan T.]

https://xentr.net/resources/xtr-seo-uyumlu-url-ve-link-yapisi.7/

@onurhans53 this is the addon you need

Yes, but you don't need to use a plugin.

 

[Recep Baltaş]

Thanks for bringing this up guys. It was grinding my gears ever since it's release with like 2.x or sth.

 

[SelamT]

@onurhans53 this is the addon you need

Don't working with Beta 6 version.

 

[Onurhan T.]

@Recep Baltaş, did you open a new site?

Yes, a project called techolay.

 

[Baby Community]

Yes, but you don't need to use a plugin.

I don't like playing with Xenforo's native files. The reason is; Playing with original xenforo files in future updates may cause big problems.

 

[Baby Community]

Don't working with Beta 6 version.

I recommend that you never use xenforo Beta versions. This situation may endanger the project on which you have spent years and money.
Always prefer to use fixed versions of xenforo versions. In fact, I always make this mistake: Wait at least 1 month after a fix xenforo version is released. If there is no problem, install it.

 

[unutKan]

Don't working with Beta 6 version.

We have implemented some changes in Beta 7 to address a number of concerns surrounding romanization/transliteration of strings, some are reflected in this thread, others have been somewhat of an issue for some in different scenarios over time.

 

[Eagle]

That is good news. I'm so glad that problem has finally been solved after a long time. Thank you XenForo.

 

[Baby Community]

That is good news. I'm so glad that problem has finally been solved after a long time. Thank you XenForo.

Unfortunately, I stuck to xenforo2.2.13. It will stay like this for a while. I've been continuing with the addon for a while.

 

[Chromaniac]

So, after update to Beta 7... Convert emoji to text is the option that was set as selected. Just a fyi!

Also, a small typo here... If 'Romanize titles in URLs' and 'Include content title in URLs' options are bothjenabled, you can control the behaviour of emoji used in titles with this option.

 

[Chris D]

So, after update to Beta 7... Convert emoji to text is the option that was set as selected. Just a fyi!

Yes, I think that’s the correct default in most cases. I could have attempted to match roughly the current behaviour but for most cases the text conversion is closest to what romanization should do.

 

[Onurhan T.]

Thank you for finding a solution to the Turkish character problem. It was beautiful. (Beta 7)

 

[HePBiZ]

We have implemented some changes in Beta 7 to address a number of concerns surrounding romanization/transliteration of strings, some are reflected in this thread, others have been somewhat of an issue for some in different scenarios over time.

Let's address the issue in this thread first.

Our previous code was based on a solution we've been using in some way or another for many years. A lot of the code was trying to solve problems and edge cases that at one point didn't have a reasonable native solution. We unraveled a few of the more redundant bits of that code in Beta 6 but for the most part the behaviours were generally unchanged from before.

Specifically code surrounding romanization which is often used in URLs behaved largely the same as it already had done, and it turns out that the approaches were fairly opinionated.

For example ö and ü were transliterated to oeueou

We took a little bit of inspiration here from the amazing work produced by the Symfony team, specifically their String component and we have entirely overhauled the process for both normalizing and transliterating strings. These changes will only apply if you have the intl extension available.

What does this mean in practice? Well, as you can see from the new title I've given this thread, the characters ö and ü are now transliterated to ou

But what about German language forums? Well, the specific rules we use for transliteration are now locale based (based on the default language of the forum).

If our default language on this forum was German, the characters ö and ü would be transliterated to oeue

So, with that, I think we can safely call this fixed. But there's more!

On a semi-related note, over the years customers have sometimes expressed a concern over the appearance of emoji in URLs. There's nothing invalid about emojis being in URLs. Behind the scenes they are URL encoded, and most browsers will display them as the correct emoji icon. This behaviour remains unchanged unless "Romanize titles in URLs" is enabled. In which case, we now have this new option to control how emojis appear in URLs:

View attachment 302553

By default, we will now convert the emoji into a string based on the emoji name. You may also decide to keep the emoji, something that previously wasn't possible when romanization was enabled. Or you may decide to remove the emoji entirely. You can see examples of these in the screenshot above.

And the end result can be seen in the URL of this thread:

https://xenforo.com/community/threads/bug-with-turkish-characters-such-as-o-and-u.221332/

The character is converted to the word bug. And ö and ü are converted to ou

It works very well. Thank you <3