This is an old revision of this page, as edited by DePiep (talk | contribs) at 11:08, 28 September 2014 (→Hatnote templates: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 11:08, 28 September 2014 by DePiep (talk | contribs) (→Hatnote templates: new section)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
|
Barnstar
The Working Man's Barnstar | |
Your contributions to the finer details of Wiki markup on various articles, at a rapid rate, is noticed and appreciated by others. Leep up the good work! MezzoMezzo (talk) 06:25, 5 February 2014 (UTC) |
- Thank you! Sardanaphalus (talk) 10:44, 5 February 2014 (UTC)
Forcing line breaks
see this screenshot for an example of why it's a bad idea to assume everyone is using the same web browser. note, I am referring to the floating dot. Frietjes (talk) 16:29, 6 July 2014 (UTC)
- I don't assume everyone uses the same web browser. I do assume, however, that "em" units are, relatively speaking, the same (or very nearly the same) for everyone. That's probably a mistake. Does the floating dot occur regardless of zoom level? Sardanaphalus (talk) 18:08, 6 July 2014 (UTC)
Template:Parameter names example
Hi Sardanaphalus. I'm a bit curious as to why you created Template:Parameter names example. Now that we have Lua, we really shouldn't be writing templates that go {{#if: {{{1|}}} | foo1 }}{{#if: {{{2|}}} | foo2 }}{{#if: {{{3|}}} | foo3 }}...
This kind of thing is easy to do in Lua, and a lot more efficient. — Mr. Stradivarius 14:07, 15 July 2014 (UTC)
- If that's an offer to convert it into Lua, then yes please, I suppose – especially as {{str letter/trim}} trims numbers from the parameter names as well as spaces and newlines (I suppose the clue is in its name). I'd have to leave the implementation/development of possibilities such as those mentioned in the initial and incomplete documentation I've just added to yourself and/or other Lua speakers, though. In the meantime, do you know if there's a template I've missed that strips spaces and newlines from the end of a string but not numbers? Regards, Sardanaphalus (talk) 10:02, 17 July 2014 (UTC)
- If you're still wanting to do things in templates and not in Lua, then the most efficient way is by using
{{#if: 1 | {{{1|}}} }}
. The #if statement will always be true, so it can be confusing from a logic standpoint, but that will strip whitespace the most efficiently of any template markup that I know. But it's not too hard to do this in Lua; for example, if you use Module:Arguments, it will trim the whitespace for you automatically. — Mr. Stradivarius 10:13, 17 July 2014 (UTC)
- Thanks for the speedy response!
- Regarding
{{#if:1 |{{{1|}}} }}
, are you suggesting that each|{{{N|}}}=''{{str letter/trim|{{{N|}}}}}''
- becomes
|{{{N|}}}=''{{#if:1 |{{{N|}}} }}''
...? (for each N = 1 to 61)
- Taking on Lua (in order to use Module:Arguments etc) seems a sea-change compared with a gradual accumulation of wiki, CSS and HTML experiences. I can see, though, that the time may come when I'll need to decide whether to invest the energy required to become conversant in it, otherwise forgo template editing. Sardanaphalus (talk) 11:37, 17 July 2014 (UTC)
- Well, I decided to go ahead and convert it to Lua - take a look at Module:Parameter names example. Now the template can handle an unlimited number of parameters - but it will only process as many as were specified, so it will be faster than the template version too. If you want to know how any bits of the code work, just let me know, and I'll be happy to help. Also, if you want to add any other display styles, that will be easy now, so feel free to get creative. Best — Mr. Stradivarius 13:39, 17 July 2014 (UTC)
- That was quick. I imagine that what's likely to arise first is a case where overriding the default parameter's-value-is-its-name would be useful, i.e. for the template to be able to handle something like
{{Pnex |A |B |C=(some text) |X |Y ...}}
. Display-wise, though, a combination of braces and italics comes to mind, or, perhaps better still, braces and/or CSS styling (i.e. wrapping each parameter value in the Lua equivalent of a<span>...</span>
?). On the other hand, perhaps that might be too open-ended. Thanks for your work. Sardanaphalus (talk) 20:16, 17 July 2014 (UTC)
- That was quick. I imagine that what's likely to arise first is a case where overriding the default parameter's-value-is-its-name would be useful, i.e. for the template to be able to handle something like
- If you were going to add named parameters, couldn't you just call the template itself with the arguments you want? (See example below.) It seems a bit strange to use a template to call another template when you could just call that template directly. — Mr. Stradivarius 23:26, 17 July 2014 (UTC)
This is an image (kind of) | |
The first label | The first data field |
---|
- I agree, although I'm imagining an override to be occasional rather than common. But it does start to undermine the point of the template. Adding means to include a <pre>-style list of the parameters beside/near the template (for e.g. the sake of a "Syntax and generic example" section on a /doc page) may redeem it, but ideally, I think, {{Pnex}} would work without needing parameter names as its own parameters – or, at least, only needing those to be overridden (so that the code above, for example, would be
{{Pnex |C=(some text)}}
rather than{{Pnex |A |B etc etc}}
). Is it possible for Lua to do anything like that..? Sardanaphalus (talk) 09:10, 18 July 2014 (UTC)
- I agree, although I'm imagining an override to be occasional rather than common. But it does start to undermine the point of the template. Adding means to include a <pre>-style list of the parameters beside/near the template (for e.g. the sake of a "Syntax and generic example" section on a /doc page) may redeem it, but ideally, I think, {{Pnex}} would work without needing parameter names as its own parameters – or, at least, only needing those to be overridden (so that the code above, for example, would be
I'm afraid not - we have to supply the parameter list manually. I have added support for custom parameter names though - have a look at the updated template documentation to see exactly what's changed. I figured that it can't hurt to add one or two custom values to an otherwise automatically generated template. — Mr. Stradivarius 10:27, 18 July 2014 (UTC)
- I've created a testcase and all looks in order – thanks for implementing/updating. I'm intending to start using the template on a few /doc pages soon, so look forward to seeing what happens. Sardanaphalus (talk) 11:37, 18 July 2014 (UTC)
- PS Perhaps some future version of Pnex might mine TemplateData entries for the parameter names..? Sardanaphalus (talk) 12:08, 18 July 2014 (UTC)
Nomination for deletion of Template:If not
Template:If not has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. — Mr. Stradivarius 14:20, 15 July 2014 (UTC)
Military portals browsebar
I believe your edits to {{Military portals browsebar}} have broken formatting at Portal:American Revolutionary War, by making the display box extremely wide, at least on Firefox (it seems to display OK on Chrome). Magic♪piano 19:17, 15 July 2014 (UTC)
- Thanks for your alert. I suspect you're correct, although the Firefox-based browser (Palemoon) I'm using here seems to display it without problem. I'll check the formatting and reformat or revert if nothing seems amiss. Sardanaphalus (talk) 12:33, 16 July 2014 (UTC)
- I've now reformatted and restored the Military portals browsebar at the Revolutionary War portal – hopefully all okay..? Sardanaphalus (talk) 22:32, 17 July 2014 (UTC)
- Yes, it looks much better now. Thanks! Magic♪piano 12:42, 18 July 2014 (UTC)
- Glad to hear it. And thanks for your "thanks" notification. Sardanaphalus (talk) 10:48, 19 July 2014 (UTC)
- Yes, it looks much better now. Thanks! Magic♪piano 12:42, 18 July 2014 (UTC)
What is the purpose...
... of changing instances of the t template to tl, when they're the same thing? It's particularly weird to do this in a closed discussion no one will ever look at again . You've done this on a dozen pages on my watchlist alone, and it seems like a pointless exercise that clogs up watchlists and article histories for no reason at all that I can see. Please explain. EEng (talk) 01:19, 8 August 2014 (UTC)
- Hello – it's so that Template:Tlpad may become to Template:Tlpad what e.g. Template:Tlpad is to Template:Tlpad, i.e. amended to produce a plain link without braces or the "Template:" prefix. Hope that makes sense and seems less pointless. Regards, Sardanaphalus (talk) 08:58, 8 August 2014 (UTC)
- I'm preparing to edit Template:Tlpad so it produces a link to a template in the same manner that Template:Tlpad produces a link to a category,
- i.e. so that Template:Tlpad produces
]
- just as Template:Tlpad produces
]
.
- just as Template:Tlpad produces
- Hopefully that makes more sense now..? Sardanaphalus (talk) 15:21, 8 August 2014 (UTC)
- 1,000,000..? I'm seeing only twenty or so uses of Template:Tlpad remaining...? Sardanaphalus (talk) 18:12, 8 August 2014 (UTC)
- Just picking two random pages, there are 32 instances on WP:MOSNUM and 17 on WP:MOS, so there seems to be something wrong with whatever you think you're doing. In any event, I ask again: are there other editors you've discussed this project with? EEng (talk) 18:22, 8 August 2014 (UTC)
- My mistake – after some head-scratching, I realized I'd looked for instances of Template:Tlpad while the namespace was set to "Template" rather than "all". So, I guess that's the end of that idea. Thanks for querying. Sardanaphalus (talk) 22:53, 8 August 2014 (UTC)
Talkback
Hello, Sardanaphalus. You have new messages at Template talk:Infobox prepared food.Message added 06:25, 9 August 2014 (UTC). You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.
Requesting input regarding problems with the infobox. NorthAmerica 06:25, 9 August 2014 (UTC)
Unbalanced braces
Hi, in this edit you added unbalanced double braces, which I have fixed. This is not the first time that I have come across this problem; please go back through your recent related edits to ensure that any similar mistakes have also been fixed. Because the issue is inside the <includeonly>...</includeonly>
, it is not visible on the doc page, but on the template which transcludes that doc page.
Also, please don't change headings like "Usage" from level 2 to level 3. Freshly-created template doc pages use level 2, because (i) there is no previous level 2 heading and (ii) that is what has been agreed (see e.g. Template talk:Documentation/Archive 7#Heading fix redux). Accordingly, that is what is coded into Template:Documentation/preload; existing doc pages should therefore not be altered so that they no longer conform. --Redrose64 (talk) 21:50, 27 August 2014 (UTC)
Re: Template rename
- https://en.wikipedia.org/search/?title=Template%3ARemove_file_prefix&diff=620869767&oldid=615939411
(Hydrargyrum moved page Template:Remove File prefix to Template:Remove file prefix over redirect: conform to Misplaced Pages template "sentence case" naming convention)
- What would the purpose be of adding a colon or quotation marks? The move didn't cause a conflict, and adding punctuation to the template name just makes it harder to remember and harder to type. — Quicksilver 21:13, 1 September 2014 (UTC)
- I was thinking that "Remove file prefix" suggested something more generic than its (current) scope – and although, yes, "Remove File:/"File:" prefix" would be more tricky, "Remove File/file prefix" would still redirect to it for as long as it wasn't e.g. reassigned to something more generic. Thanks for your response, Sardanaphalus (talk) 09:28, 6 September 2014 (UTC)
Recent changes to Template:Infobox company
Your recent changes to Template:Infobox company seem to be effecting headquarters field. See Northrop Grumman, Grumman, and probably others. --Svgalbertian (talk) 21:57, 1 September 2014 (UTC)
- Thanks for the alert. I think (hope) all is in order now – it was a couple of missing conditionals. Regards, Sardanaphalus (talk) 22:06, 1 September 2014 (UTC)
WP:Template documentation
Hi, I had to revert your addition, because it had an extra <!-- in it, and if you would place a category there, it would categorize any "other" page into the category, which may not work with certain transcluded pages, for example, if it's on a Misplaced Pages or Help page, and not just a template page. Funandtrvl (talk) 15:06, 2 September 2014 (UTC)
- Understood – thanks for catching. Sardanaphalus (talk) 09:30, 6 September 2014 (UTC)
Some baklava for you!
Hi sardanaphalus you have some good history and it is nice thanks for doing history and making it look nice. hope we can be friends thanks jalyn.. Jlynn13 (talk) 20:39, 13 September 2014 (UTC) |
- Thanks, jalyn. If/when you can't seem to find something here, I can try to help – or direct you somewhere or to someone who should be able to help. Enjoy, Sardanaphalus (talk) 22:33, 13 September 2014 (UTC)
Hi-hat, hi hat, high hat and high-hat
A tag has been placed on Hi-hat, hi hat, high hat and high-hat, requesting that it be speedily deleted from Misplaced Pages. This has been done under the criteria for speedy deletion, because it is a redirect from an implausible typo, or other unlikely search term.
Please do not remove the speedy deletion tag yourself. If you believe that there is a reason to keep the redirect, you can request that administrators wait a while before deleting it. To do this, affix the template {{hangon}}
to the page and state your intention on the article's talk page. Feel free to leave a note on my talk page if you have any questions about this. Steel1943 (talk) 12:49, 17 September 2014 (UTC)
- We already have a clutch of redirects for each individual term. We simply do not do pages, not even redirects, with multiple variants all together. And we do not contest deletion on (article) pages - we use the talk pages. — RHaworth (talk · contribs) 13:21, 17 September 2014 (UTC)
- @RHaworth: To be fair, the generic
{{subst:Redirtypo-warn}}
message (as used above) is ambiguous - it says "affix the template{{hangon}}
to the page", which is exactly what Sardanaphalus did; it just wasn't clear that the talk page was the place that the{{hangon}}
should have been put. --Redrose64 (talk) 14:01, 17 September 2014 (UTC)
- @RHaworth: To be fair, the generic
- Apologies. The mistake was not putting it in the wrong place but recreating the page with just an {{hangon}} tag when it had already been deleted. Once a page has been speedied, the correct place to challenge is DRV. — RHaworth (talk · contribs) 15:38, 17 September 2014 (UTC)
Nomination for deletion of Template:Tanakh
Template:Tanakh has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. JudeccaXIII (talk) 19:54, 21 September 2014 (UTC)
- I withdrew the nomination because of a redirect error that had me confused with another template. Sorry about that nomination. -- Cheers -- JudeccaXIII (talk) 19:29, 22 September 2014 (UTC)
Hatnote templates
Hi. After your moves, there is a circularity in the redirects (and not all are named /doc). Could you take a look? -DePiep (talk) 11:08, 28 September 2014 (UTC)