Bug: Posters and Titles are not in same language

[marcosschroer]

Example: (Correct poster, wrong title)
https://i.imgur.com/hb8kvvc.png

I think it's because the ones that have PT-PT registered on TMDB will show it correctly but the ones that are not registered (or PT-BR) it will fallback to ENG, so if you could add an option to choose which portuguese the user wants (PT-BR or PT-PT) and then fallback to each other instead of english, i think it would work better, TMDB does that, for everything (posteres, titles, descriptions)

Because there are big differences in these two portuguese language sometimes

[marcosschroer]

Is there any update to this?

[TimilsinaBimal]

Is there any update to this?

I am still looking into it!

Do you have documentations on this. I couldn't find about that fallbacks.

[marcosschroer]

Take a look at the TMDB source code
The getlogo file

[TimilsinaBimal]

I checked and while there is a way to handle this.
I think it can cause serious latency issues on the api endpoints.

Currently the best way I am looking to implement is to fetch both english and PT version and compare both,
if english is present in PT, then simply fallback to english as falling back to PT-BR or PT-PT can cause other complications!

[marcosschroer]

So, basically, it will work? in PT-BR for Brazilians
TMDB does that and I see no latency issues on the elfhosted version (But my understanding of this is very limited)

[TimilsinaBimal]

So, basically, it will work? in PT-BR for Brazilians TMDB does that and I see no latency issues on the elfhosted version (But my understanding of this is very limited)

Fallback can be done in all langauges. But the issue can be how we handle this...

I checked the tmdb addon code and he added fallback only for logos

But here, I am trying to add fallback for all meta (poster, title, overview)

My rough initial solution to this is:

Option 1: Fetch both preferred language meta and english meta, compare them and if preferred language has same values as english, us english one (This can be done with other language fallbacks too): This means we have to call for two metadata for each item so almost double latency on that part only

Option 2:: Call an API to detect language on preferred language meta and if its not in correct language, fallback to another language. But finding language detector API that is free can be challenging here

Option 3: Give user the option to add base url to fetch metadata from. So basically this means you can add tmdb base url as metadata provider and it will use all meta from that only. I think this is the most safe option among all.

[marcosschroer]

I see that Portuguese Brazil is available now but after installing, it still shows me PT portugal content.

[marcosschroer]

Update: It seems to be working now! :)

Just tested here and what I saw was in PT-BR! for Titles and posters

looking really good!!!

[TimilsinaBimal]

Update: It seems to be working now! :)

Just tested here and what I saw was in PT-BR! for Titles and posters

looking really good!!!

Yeah the selected language should work.

But for fallback, I need to really look and find something optimal.

[marcosschroer]

What does that mean exactly?

[TimilsinaBimal]

What does that mean exactly?

So currently, You select one language from UI, and when I call tmdb api, I send that exact language. But what I have seen is they sometimes return content in different language(english) if they don't have that translation in requested language.

This can result in different language poster and Overview/Name.

So, I think we also need to add some fallback on our end, but this can complicate things as I said earlier.

If you find something like that please report.