Community Wishlist Survey 2022/Translation/Make "translate" tags always render correctly

Make "translate" tags always render correctly

Discussion

GeoffreyT2000 (talk) 04:27, 28 January 2022 (UTC)

  • Congratulations for marking all of the affected proposals' "/Proposal" subpages for translation! Now, none of the above seven proposals are affected anymore. But the problem could still affect proposals created in future surveys. GeoffreyT2000 (talk) 05:40, 28 January 2022 (UTC)
    Hehe, as you know by the time voting starts there should be no proposals left for you to use as an example. But thank you for keeping track of this for us! :) There is a more permanent example at User:MusikAnimal (WMF)/Translate example (so long as no one marks the subpage for translation). I'm not that familiar with mw:Extension:Translate internals, but it's possible this is an unavoidable bug. For a moment I thought there was a workaround we could build into our templates, but I see that even transcluding the page directly (and not a /en or /mylanguage subpage as is done with {{dynamite}}), the parser is not recognizing the <translate>...</translate> tags. The thing is, when you view the subpage directly, they are not visible. So this is unique to transclusions. One of the many translationadmins here on Meta may be able to explain this. MusikAnimal (WMF) (talk) 05:41, 28 January 2022 (UTC) MusikAnimal (WMF) (talk) 05:42, 28 January 2022 (UTC)
  • This opt-in behavior of transclusion is intentional to avoid breaking existing templates that rely on the previous behavior. It's possible though that this might change when Translate extension is updated to support Parsoid. Nikerabbit (talk) 18:25, 8 February 2022 (UTC)

Voting