Hi, we’ve noticed this happening a few times, that in one language the translation is cut short, so the whole message is not translated.
E.g. in this post, original Swedish message and translated English and Danish ones are correct, but the Finnish translation lacks the URL link and end of the message. Also in this thread, the header is “NIBE maalämpöpumppujen ja energiatehokkaiden ratkaisujen jättiläinen Ruotsista” originally in Finnish, but in Swedish it’s cut short only as “NIB”. In Danish it’s only “N”
Anyone else noticed similar? Could this relate to hitting the limits, as we’re translating our post history in full speed? One potential fix would be for Admins to have a trigger for retranslating a single post.
I recommend adjusting the translation prompt based on what you’re noticing - see here and AI translation post raw translator persona. I don’t think this has got to do with limits, likely just the chosen LLM not managing the translation well.
Am I stupid as I cannot find a setting to enable that post translation button on our forum? We’re running Discourse 3.6.0.beta1. Content localization allowed groups have admins selected, so shouldn’t be that either
Okay cool, I’ll take a stab at modifying personas and see if that fixes it!
Many admins have tripped over this and @Moin has been consistently reminding folks about the post menu. Perhaps one thing we should do is to automatically add this post menu button when the feature is enabled.
I like that idea. I can’t think of a reason why you wouldn’t want the button in the post menu after enabling the feature. Perhaps it would be nice if admins could still decide whether it should be in ‘post menu hidden items’ or always visible.
Yeah I think that could be logical. I tried to find this on AI and localisation settings, but would be logical if it appeared automatically after enabling the feature.