@hosam: Can you take a look at the results now? We should be sorting by the first release date now.

@matt: Sorting by original_title.desc would is sorting Z-A, so you would indeed see the foreign chars first. If you're looking for A-Z, that would be original_title.asc. This is just sorting by the UTF-8 character bytes so things like punctuation have a lower code than numbers, which are lower than letters. See here.

Cheers.

yup the results now are back to normal. I think it is even bit better. Thanks man!

I understand why it's sorting Unicode first because of the character codes being higher, but because the translated title is what's being displayed it looks out of order. I'm guessing the system is not capable of sorting by translated title? My app let's you sort by title, date, and rating when browsing a genre, and the title sort looks broken to users. I've been debating the best way to handle it, and taking into consideration what users in other countries would see. I apologize for all of the questions - I am not the original author of this app, but it was turned over to me because the author didn't have time to update to the new API version. Not having ever seen the responses from the old version, I have no idea whether I'm seeing new behavior or not.

We only just added sorting by title, so it's a brand new feature that didn't exist until ~2 weeks ago.

Our search server is not able to sort by the translated title. There's no connection to a requested language and a result until it's further down the line, after the response has already been returned by search. We can only sort on static fields, hence it being original title.

Cheers.

Rats, that's what I thought. Thanks.

Hi guys, the Discover API is still broken. When you add the sorty_by=release_date all filters release_date.gte and release_date.lte are totally ignored. Here's my issue discussion: https://www.themoviedb.org/talk/58106900c3a3687477004f4f