Current status
We got a new hook in the parser, because the hook we were planning to use is deprecated. The new hook is also more flexible. We (Language team) are implementing a mechanism to enable this feature without breaking pages that rely on the existing behavior. We have identified one bug where the translation pages do not update when expected (see case 2 in T47096#6708905). Cause of that is not clear.
Original report
(I'm assuming that Special:MyLanguage is part of the Translate extension.)
I think it would be helpful if it was possible to transclude Special:MyLanguage. For example, if a template is translated, the correct language version needs to be the one that is used, but one can't just input {{Special:MyLanguage/TemplateName}} to get it to work.
At some point https://www.mediawiki.org/w/index.php?title=Module:Template_translation&oldid=716205 was created which, used on the translatable template page, automatically fixed all transclusions (AKA transcluding pages, callers). The main goal of a built-in solution should probably be this: make it possible for a template to become translatable without requiring edits to all transcluding pages.
See Also:
- T63695: Selecting a different language should switch the language of the content served
- T59603: Create a {{PAGELANGUAGE}} magic word
- https://translatewiki.net/wiki/Thread:Support/Identical_messages_in_the_translation_tool (another use case)
Expected outcome
Translatable templates are usable on translatable pages with the normal syntax for transclusion.