Around 1500 posts (well, lenght would be more important than amount of posts, but big majority has been relatively short) and to four languages has cost to me close to 50 USD totally so far.
But I started use that option when it was first introduced and at some point I used perhaps a little too expensive model — I’m an OpenAI customer.
One post translated to four languages costs for me perhaps two US-cents.
ai_translation_backfill_max_age_days ist bei 90 und ai_translation_backfill_limit_to_public_content ist aktivert.
Die Beiträge sind auch in einer öffenlichen Kategorie geschrieben. Ich habe gerade auch nochmal 8 Beiträge mit einen Testuseraccount und den Admin Account in 2 verschiedenen Sprachen geführt. Die Beträge weredn generell übersetzt aber der Count steht weiterhin bei 52 Posts.
I see. If it’s stuck at 52 then this might be related to locale detection. If you are able to, there’s a hidden site setting SiteSetting.ai_translation_verbose_logs = true that you can try to turn on. Once you’ve done that, you can check /logs and see if there are errors.
I’d like to register some feedback about only 2 times per day, and also with the (unadvertised?) fact that if more than 2 edits occur, any further edits are not translated - ever (unless another edit happens in the next 24 hour period, I suppose). Or at least that’s my understanding.
We had a situation where a worldwide event was generating continuous feedback over 18 hours or so, and some of that feedback led to updates in a FAQ topic. There were probably 5 or 6 edits of the FAQ during the day.
I can understand the need to throttle existing post edits, but for situations such as this a limit of 2 over 24 hours seems restrictive. As an alternative, I’d like to suggest allowing 1 edited post translation over some period of hours, and if more occur in the same period, whatever the latest edit happens to be is translated at the start of the next period and counts as the translation for that period. How many hours? Ideally one, but if not that, then no worse than 6 hours.
Additionally I’d like to lobby for a moderator/admin feature Translate Now which forces a translation (or re-translation of something edited, bypassing the throttling mentioned above when it’s urgently needed). Having recently started using translations there are topics more than a year old that need to have translations available, but lacking this, I had to set a backfill period large enough to capture those old posts. I could have made do with a much smaller backfill if it were possible to select older posts for translation.
While I like the idea of a “translate now” button (and I’ve cast my vote for it!), it doesn’t resolve the larger concern that was raised: We present translated content that will not be representative of the content in the original language if more than 2 edits have taken place in a single day, and neither the author of the post nor the readers will know this is the case. This makes the translation feature less credible as a tool on our platform.
Examples:
On our own internal site, a “source of truth” OP in a topic may be edited multiple times in a day as replies highlight additional details that need to be added or changed.
On the site I used to manage, it was common for an OP about a trending support issue to be wikified and edited multiple times during a day, providing valuable issue workarounds that were shared in order to offload support requests, saving the company time and money.
And of course, as mentioned above, updates to an event could require multiple edits. Imagine traveling to an in-person event and showing up on the wrong day because the date was changed after the two-day edit retranslation limit had been reached!
Even if the feature to allow site staff to trigger retranslation were available, if the edit is made by someone who is unaware of the limit, they would not know they need to request retranslation, and on a busy site, staff may not notice that the translation is no longer true to the original.
Could the daily limit be a site setting, to empower the site owner to determine their own perfect balance between reliable translations and managing LLM costs?
Could we add a warning about the limit when a user edits a translated post, so they’ll be aware? We warn about other rate limited features.
That could be done, but to be very honest, if the limit is set to X and any user edits it X+1 times, you would face the same issue as well. We would then have developed a solution that doesn’t really solve the problem systematically.
We do have an indicator that shows when a translation may be outdated, it is coloured the same way as post edits indicator
However, when going on the article and switch to the french version of the UI, even with the “machine-learning translation” activated, the original version of the article is displayed
Could there be a setting or something which I could have forgotten to enable, in order to display the localized content ?
As a matter of fact, the localization of the categories works well !
I had a question about localized content - is there any possibility or plan to index the title and content of localized topics in the Discourse search, based on a user’s locale ?