Multi-byte character strings immediately after language prefix cause a 404 about silverstripe-languageprefix

[Martimiz]

First of all - can you confirm that it works without the languageprefix module, so with translatable only? It looks like a bug either way.

Second: would the following url work:
http://asia.mysite.com/thailand/th/page-name-th/page-name(in thai)/page-name(in thai)

Trying to find out if it's only that the urlsegment after the language prefix cannot be in thai. Also I have no experience with non-roman sites/languages. If this is actually a languageprefix issue, could you, say, build a very simple testsite in 3.1 in thai that has these issues and then send me a copy of the database?

[sasargen]

Thanks for your reply. First, I guess this is a translatable bug. I made a fresh install of SS 3.1 with translatable only and the same bug occurred. Just going to the Home page prompted a 404 when the URL used พันธกิจ instead of Home.

Second, I can confirm that the Thai language URLSegments are working normally after the first one. I have tested using Thai in the second and third level down from the common webroot.

I have a simple 3.1 site prepared (just home page, 404, and 500 in English and Thai). It is in a mySQL database. If you would like me to send it to you, please let me know what format is best and where I should send it.

[Martimiz]

Ok, If this is indeed a Translatable bug (and it doesn't occur in a default 3.1 install without Translatable installed) you should probably start by reporting the issue here, if someone didn't already:

https://github.com/silverstripe/silverstripe-translatable/issues?state=open

Others might face this as well and maybe someone already has a solution..?