Template talk:Translatable template

SUBPAGENAME vs titleparts

{{SUBPAGENAME}} is problematic since it depends on the namespace having subpages enabled. Titleparts doesn't have this problem. – Nikerabbit (talk) 07:05, 7 April 2012 (UTC)

Cf. translatewiki:Template:Langcat. Apart from that, couldn't this template be used for any translatable template rather than just navigation templates? Nemo 18:36, 8 April 2012 (UTC)

Sorry about this really late reply, saw the talk before but forgot about it again.

In this wiki it doesn't matter since subpages are enabled in all namespaces (I think), but using titleparts instead is a great suggestion since it would be valid everywhere.

@Nemo, it can be used for any template that doesn't require named parameters – if needed it could be extended to support X number of unnamed parameters, but if you have any named parameters it would become quite problematic. The name of the template should probably change though, I just couldn't think of any better non-cryptic name when I created it. Even though it doesn't support named parameters, do you think "Translatable template" is a good solution? Jsoby (talk) 09:15, 15 May 2012 (UTC)

Adding tnt to my wiki

How could I add tnt and tntn support to my wiki? I've created tnt template with code from this wiki and module for that. So now it shows only default lang template instead of use its translated version. — Preceding unsigned comment added by 94.45.162.176 (talk • contribs) 14:50, 4 July 2015 (UTC)

Template:Extension

Template:Extension does not work if the namespace= parameter is specified. For example, see Extension:MultimediaViewer.

{{TNT|Extension
|name      = Test
|status    = stable
|namespace = main
}}

Result: Extension

--Shirayuki (talk) 20:53, 10 August 2015 (UTC)

 Done by renaming "namespace" to "tntns"! --Shirayuki (talk) 02:41, 19 December 2015 (UTC)

Breaks Special:TemplateSandbox

Templates included via TNT cannot be mocked by TemplateSandbox. I created User:Tgr_(WMF)/sandbox/hook_names/Template:TNT as a poor attempt of working around it. The template will look broken (the same way it would look without TNT) but will be properly replaced by the sandbox template. --Tgr (WMF) (talk) 16:43, 22 April 2016 (UTC)

Not working

I imported this template along with the module to an external wiki and when I transclude a template using this template, the translation tags are shown on pages where the template is shown. What am I missing? MacFan4000 (talk) 11:36, 30 August 2017 (UTC)

Move documentation back to subpage

{{Editprotected }}

Please revert this template to the 1 October 2019 version. Shirayuki moved part of its documentation to the main template page with the summary “migrate to make translation easier”. However,

• This template contains no human-readable text, therefore it doesn’t need to be translated. Ever.
• Including the documentation directly in the template’s code increases its pre-expand size, which may lead to breaking pages that use it many times.
• It makes the documentation fully protected, making it much harder to edit for non-admins, for no valid reason.

Thanks in advance, —Tacsipacsi (talk) 12:05, 1 September 2020 (UTC)

@Tacsipacsi: Shirayuki appears to have responded to this by marking the template for translation and lowering the protection to semi-protection, rendering this request moot. Also, courtesy ping to DannyS712, who originally protected the template as high risk.

Personally, I've never understood why this wiki stores documentation in the same page as this template generally, but I've tried to respect that convention anyway, and never taken any admin actions relating to it other than restoring deleted history of documentation pages that were recreated to store TemplateData. * Pppery * _{it has begun} 15:22, 1 September 2020 (UTC)

Feel free to revert my actions here if you want --DannyS712 (talk) 15:23, 1 September 2020 (UTC)

Shirayuki already did. * Pppery * _{it has begun} 15:28, 1 September 2020 (UTC)

@Pppery: There is point in storing documentation at the same place as the template code in case of translatable templates—it defeats the performance reason for documentation, but makes it possible to translate the template and its documentation at the same place. However, that’s not the case here—there’s nothing to translate in the template. Shirayuki, if you want to make the documentation translatable, please do so on the /doc page and make it UI language-dependent (|uselang={{int:lang}}). This way the documentation is translatable, while the performance gain of subpaged documentation is kept, and we don’t create translated versions that aren’t used anywhere. (I deactivated the edit request, as no admin assistance is needed now that the template is only semi-protected.) —Tacsipacsi (talk) 20:30, 2 September 2020 (UTC)