Thread

As we all know, when filling out an entry’s Title field, the characters get auto-converted into a URL-friendly format for the URL Title field. However, this only works with Latin characters; when an entry Title is in Hebrew, for example, nothing is placed in the URL Title field, which must be filled out manually.

Is there any way to add custom character to the conversion process? Even better, is there a way to plugin Google Translate to translate the non-Latin-based language title into English, and then convert that translation into a URL-friendly format?

Michael,

What version and build of EE are you using?
Can you give us an example text so I can see for myself please?

Michael,

What version and build of EE are you using?
Can you give us an example text so I can see for myself please?

The version I’m on where I’m missing this capability is 1.6.8, but I’ve tested it on another client’s 1.7.0 site, and the behavior is unchanged.

Here’s some sample text, the welcome message from the Hebrew Wikipedia:

ברוכים הבאים לוויקיפדיה!

Hi, Michael.

That would be a great feature request, or you could look on Devot-ee.com to see if there is something similar for EE1.x or EE2.x.

Is this a site you’re planning on updating to EE2 at some time, or will it stay in 1.x? (The built in method for EE2 hasn’t changed from 1.x to 2.x)

Hi Sue,

It’ll be remaining on EE1 for quite some time, as one of the MSM sites makes very heavy use of SAEF functionality.

I found this add-on on Devot:ee, which allows you to specify latin chars to use when non-latin ones are in the entry title, but it seems somewhat pointless; a main reason for having a decent URL Title is readability/SEO, and replacing non-latin text with latin equivalents will result in nothing but gibberish, as the screenshot for that add-on demonstrates (“mhnin_aeide_qea” is pretty non-sensical and useless).

I’ll submit I’ve submitted my Google Translate idea as a feature request to the author of that add-on, but if someone on the EE team wants to build it in to the core featureset, don’t let that stop you. 😊

Hi, Michael,

You’re welcome to add it as a feature request for the core featureset as well.

You are aware also that SafeCracker is now distributed by EllisLab and is far more powerful than the built-in SAEF? That may end up being a good reason to upgrade to EE 2 for your particular needs. =)

You are aware also that SafeCracker is now distributed by EllisLab and is far more powerful than the built-in SAEF? That may end up being a good reason to upgrade to EE 2 for your particular needs. =)

I am indeed, but as a one-man team who only works part-time for this employer, the prospect of performing the upgrade is quite daunting. 😊

Michael, I completely understand.  You can always try it locally so you’re not under any pressure.

In the mean-time, is there anything else we can help you with?  I’m sorry there isn’t an immediate solution for you on this issue.

Nope, that’s it I believe. 😊 Much grass!

In that case, closing the thread. Feel free to start a new thread if you have any more questions.