This post in my community is in German, but it’s not being translated.
I tried forcing a translation, but it didn’t seem to work.
I’m curious what happens if I select German here. Does that force a language to be “set”?
Yes, that is exactly what it does.
It is mixed between English and German, with the titles being all in English, so it’s a tricky one. No wonder the LLM is saying English, as titles carry more importance usually.
Setting it manually is the way to go indeed.
I did this and waited about 20 minutes, but no translation populated. Even after selecting the Translate post option.
I manually added a translation, but now I don’t see a way to provide a translated title. Any tips?
I’ve come across this problem too. The solution was to select the language option first, and then add the title and content. That’s how I managed to sort it out.
If the new language you’ve added still isn’t visible, then you’ll need to delete the language option and recreate it as I’ve described.
Ya know what.. It is giving me an error about the title being missing. My guess is it’s related to using a post template:
Actually, the situation is quite clear. There is an issue with the theme you are using. The title information disappears when you select a language. I would recommend trying a preview with a different theme. If you can see the title in the preview, there is a missing field in the language settings of the theme you are using.
I checked on my own system, and I started getting the same error too. I think the changes made in the latest updates caused this. It seems the changes made to the discourse-ai system are preventing manual edits. I was able to perform these actions yesterday, but after today’s updates, I can no longer do so.
For your information @nat
That can’t be. Those 2 commits above have nothing to do with the translation feature itself.
Meta is still translating fine.
What LLM are you using? Gemini? Please note there are deprecations for some models - https://ai.google.dev/gemini-api/docs/deprecations
Coincidentally, we were in the middle of switching Claude plans, and our translator was using an old API key. When I switched our translator back to CDCK’s LLM, and I viewed the topic shortly after, the title was translated.
I think it all stemmed from some back-end user error on our part. I think we’re good now!
I do not use any AI to translate or write anything into my forum. I just found these pulls related localization issue which effect my forum after the updates. It might be composer part too but I could not find any pull related with it.
These may not create problem but I started to face the issue after April 14, 08:00 PM. If you help to find the issue I would be grateful because I cannot use any AI to translate in my forum (it is academic).
The dropdown to choose the language was moved into the composer toolbar
Before:
Now:
The change happened in UX: move post language selector to toolbar, deprioritize for AI by awesomerobot · Pull Request #39208 · discourse/discourse · GitHub
Good to know, thanks! I don’t think our site has updated to that yet.
Albeit, I actually prefer the older positioning 
I’d like to help. Can you create a new topic to reiterate your issue please, given this one’s now solved? (feel free to @ me there).
Thank you for your efforts. @Moin has clarified the situation.
As academics cannot tolerate even a single incorrect word, we need to leave the work to them without using machine translation. I apologise for taking up your time with this matter.
Also, I too prefer the old position, like @putty . It looked more visually appealing 