The discussion revolves around an issue with content localization in Discourse 3.5 where translated text is not displayed when changing the locale, despite the HTML language attribute updating correctly. monty25 reports that translations are set up (e.g., Dutch to English (UK)), but the content remains unchanged after locale selection, even with the tl=en parameter. While the hreflang links are absent (noted as a known gap), the HTML lang attribute does switch from nl to en-GB. nat suggests checking the post’s original language setting and mentions a new experimental feature, content_localization_crawler_param, which is not available on the stable branch. Moin confirms that this feature is too new for Discourse 3.5’s stable version. tobiaseigen asks if the issue was resolved, emphasizing that the translation features are still in development and require the latest version, not the stable release.
We have a new experimental feature that’s behind a hidden site setting – content_localization_crawler_param which can serve translated content to Google.
We’re still in testing phase, but I’ve seen some optimal results so far.
@monty25 האם הצלחת לפתור את הבעיה שלך? כפי שמציין מוין, עבודת התרגום היא די בחזית הטכנולוגיה ואם אתה רוצה להשתמש בה, תרצה להיות על הגרסה העדכנית ביותר, לא על הגרסה היציבה.