Template talk:En

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Apart from seeming thoroughly pointless, on the English Wikipedia, every use of it I have found is mistaken: people generally assume that it redirects to something like {{en icon}}, [ (English) ]. As (eg) {{it}} and {{fr}} do just that [ (Italian), (French) ], I would suggest that this does the same. —Ian Spackman 22:36, 8 December 2006 (UTC)

I'm currently using WP:AWB to replace instances of {{fr}} with calls to {{fr icon}}, specifically so that {{fr}} can act the same as {{de}} does (providing a link to the French Wikipedia, for fr). I'm doing the same to several other similar templates at the same time. — OwenBlacker (Talk) 20:33, 21 October 2007 (UTC)

Edit request on 18 August 2013[edit]

Add

{{subst:Tfm|En icon|heading=Ar and En|type=inline}}

Lfdder (talk) 00:22, 18 August 2013 (UTC)

Done --Redrose64 (talk) 07:50, 18 August 2013 (UTC)

Edit request on 20 February 2014[edit]

Replace

{{being deleted}}

with a less confusing notice, such as

{{tmbox|type=move|text=This template is only for use in File namespace, when moving files between here and Commons.}}

I don't know which type would be more appropriate: move, delete, notice, style or content.

This template was discussed at Wikipedia:Templates for discussion/Log/2013 August 18#Template:En and closed as delete. This was then disputed. The resolution was to keep the template for use only in File space. There was no real consensus on what the template should contain, so it was left as is, with the deletion notice. This sparked a question at Wikipedia talk:Templates for discussion#TFM in limbo, prompting this edit request to avoid future confusion. —PC-XT+ 11:39, 20 February 2014 (UTC)

Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. Once this is done and looks good, I'll request the protection level on this template lowered to Padlock-pink.svg Template editor so that I can process this request. — {{U|Technical 13}} (tec) 13:38, 20 February 2014 (UTC)
There's not even any testcases here. — Lfdder (talk) 16:44, 20 February 2014 (UTC)

I've added the new notice to the doc subpage. {{being deleted}} can simply be removed from the template. — Lfdder (talk) 16:44, 20 February 2014 (UTC)

Done I've replaced {{Being deleted}} with {{Tmbox|type=move|text=This template is only for use in File namespace when moving files between here and Commons.}}{{U|Technical 13}} (tec) 17:42, 20 February 2014 (UTC)
So now we have two of the same. — Lfdder (talk) 18:21, 20 February 2014 (UTC)
@Technical 13: please address this. — Lfdder (talk) 21:30, 20 February 2014 (UTC)

Followup edit request[edit]

Changes are in the sandbox

By the same reasoning as the above edits, I have removed/replaced all transclusions of this template in many namespaces. The sandbox should remove non-commons usage and add namespace detection. —PC-XT+ 05:48, 23 February 2014 (UTC)

PC-XT, one of us is confused. I've synced the sandbox with the live template (which should alway be done before you start hacking in on the code) and am wondering if you would be so kind as to make your changes to that. I think you are missing the fact that the code that it appeared you wanted removed isn't in the template anymore. Lfdder, perhaps you could chime in here as well and we can get this template properly situated to everyone's needs. Thanks. — {{U|Technical 13}} (tec) 14:22, 23 February 2014 (UTC)
Getting the notice removed/replaced was a stepping stone. It said that this tpl's getting deleted, which is/was no longer true. This tpl's only meant for use in descriptions of files copied over from Commons. This latest change is for getting rid of {{en icon}} and displaying an 'error' that this template should only ever be used in the File namespace in all other instances. There is (as far as I can tell) consensus for these changes (see PC-XT's explanation and the links at the top of this thread). — Lfdder (talk) 14:37, 23 February 2014 (UTC)
Yes, the first edit was simply to remove the notice, not handle the File namespace. I pasted the template into the sandbox, then edited it. Are you saying I should have substituted it in the first edit, before making changes? (I used sandbox diff to compare, and didn't think to make an extra first edit.) The main links are: TfD, File namespace discussion and template followup discussion including this sandbox. Sorry for the confusion. —PC-XT+ 21:15, 23 February 2014 (UTC)
Also note that the other two templates in that last discussion, ({{ar}} and {{de}},) were deleted and WP:SALTed. This one was only spared for use in File namespace because of its relationship with Commons, which has a similar template. We felt an error was in order, and this is more informative than the red template name. (The commons version has a different error handling method, using categories, but so far nobody has suggested that such is needed, here, though it could easily be added.) Suggested testcases: try it on some Files (preview) to see no change between sandbox and current version, then try it anywhere else for the error message from the sandbox. —PC-XT+ 21:43, 23 February 2014 (UTC)

I understand if template editors would like to have an RfC or something, to better define the sandbox before making the edit. It could consider such questions as how closely we want to support the commons template, what we want the error message to be in other namespaces (possibly allowing the text to be visible, for instance), whether we should have a second message for empty content instead of simply allowing the display of {{{1}}}, or possibly other matters that may rise. Or, would it be better to make the requests in smaller stages, so template editors can easily see what is changing? (This has 2 changes in it. We could separate them into two edit requests, if it would simplify things...) —PC-XT+ 11:33, 26 February 2014 (UTC)

I've changed the tpl in the sandbox to use Module:Namespace detect and set up some testcases. @Technical 13: what do you think? — Lfdder (talk) 12:12, 26 February 2014 (UTC)
Done{{U|Technical 13}} (tec) 15:53, 26 February 2014 (UTC)
Thanks. You need to purge the tpl for the doc changes to take effect. — Lfdder (talk) 16:05, 26 February 2014 (UTC)
Never mind, it seems us peasants can also purge. — Lfdder (talk) 19:19, 26 February 2014 (UTC)
Any user can WP:PURGE a page. There's been a "[purge]" link at the top of template doc boxes since 18 March 2009‎ - longer than I've been around. --Redrose64 (talk) 19:51, 26 February 2014 (UTC)
I can't purge fully-protected templates. — Lfdder (talk) 19:55, 26 February 2014 (UTC)
Yes you can; Redrose64a (talk · contribs) has just tried it, and if they can do it, so can any user who is not blocked. Please note that a WP:PURGE is not the same as editing a page and saving it - that's a WP:NULLEDIT. --Redrose64 (talk) 20:09, 26 February 2014 (UTC)
Right then, whatever it is, I can't apply doc changes to fully-protected templates. — Lfdder (talk) 20:11, 26 February 2014 (UTC)
I really don't see why not. The prot level of a template is not inherited by its doc page; and if IP editors (and Redrose64a) can go to a full-prot template, click the "[edit]" link at the top of the green documentation box, edit the doc page, save it, return to the template, click the "[purge]" link at the top of the green documentation box and see an update, there's no reason why you should not be able to do the same. The only difference between the purge action for IPs and for logged-in users is that when an IP clicks the "[purge]" link at the top of the doc page, the purge isn't actioned immediately - instead they get an extra page which reads:
Clear the cache of this page?
Yes
Purging a page clears the cache and forces the most current revision to appear.
But once that "Yes" button is clicked, there is no difference from any registered user. --Redrose64 (talk) 21:10, 26 February 2014 (UTC)
It seems I can apply some changes, but, for example, I've subst'ed Template:Arabicnav in the doc of Template:Lang-ar, but it's still transcluded. — Lfdder (talk) 21:57, 26 February 2014 (UTC)
It's possible that your computer is showing a locally-cached copy. Try a WP:BYPASS; in Firefox, for example, this is Ctrl+F5 --Redrose64 (talk) 23:21, 26 February 2014 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────I did try that earlier; no dice. Anyway, it's fixed itself now. Thanks for looking into it. — Lfdder (talk) 00:07, 27 February 2014 (UTC)