![]() Archives |
|
---|---|
|
|
Threads older than 365 days may be archived by MiszaBot II. |
Contents
election commission of india
please change the chief election commissioner to Syed Nasim Ahmad Zaidi . Anusreeraj32 (talk) 16:28, 21 April 2015 (UTC)
- @Anusreeraj32:
Not done: this is the talk page for discussing improvements to the template
{{About}}
. Please make your request at the talk page for the article concerned. --Redrose64 (talk) 16:36, 21 April 2015 (UTC)
Template talk:About/doc redirects to Template talk:About? Why?
Can anyone tell me why Template talk:About/doc redirects to Template talk:About?
I would like to discuss the documentation - in particular apparent lack of specification of the actual parameter names in the TemplateData subsection, as well as the inclusion of Default and Example fields, all of which are empty, I believe, taking up screen space. Both make it a lot more difficult to mentally put together a line of syntax. Perhaps this code generated documentation?
Thanks, Peacedance (talk) 20:58, 20 August 2015 (UTC),
- @Peacedance: Templates often have subpages - the normal ones are /doc, /sandbox, and /testcases. It is common practice for all of the subpages to have their talk pages redirect to the talk page of the template proper, this is so that discussion can be kept in one place. So Template:About/doc is discussed at Template talk:About. --Redrose64 (talk) 22:01, 20 August 2015 (UTC)
-
- @Redrose64: Thank you - that makes sense. I wasn't sure if the redirection was a mistake or what. I will re-post my point with a an appropriate header (tomorrow). Peacedance (talk)
Comma as well as "and"
This needs to support ||
or |,|
as input to generate a comma, as well as presently-supported |and|
to generate the word "and", so that this:
{{About|humans as a species|other uses|Human (disambiguation)||Humanity (virtue)||Human nature|and|Human condition}}
works. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼
Readability fix
For readability, it would be nice if |and|
would output:
- ", and "
not just:
- " and "
[Quotation marks added for clarity.] This would more clearly separate two articles linked in series. Many of our article titles contain the word "and", while already visited links have a color close to that of unlinked text; together this can make something like "Earth, Wind and Fire and War and Peace" difficult to visually parse (visit both, the come back and reload this page and you'll see). Even unvisited, it's not that easy to distinguish, without a comma, for anyone with blue color-blindness. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 03:49, 6 September 2015 (UTC)
Named link impossible?
{{about|the tasty edible thing|Fruit#Orange|the article on fruit}}
Doesn't seem to be work? Best I can do is:
{{about|the tasty edible thing|[[Fruit#Orange|the article on fruit]]}}
Can't get the brackets to go away. W3ird N3rd (talk) 20:38, 14 September 2015 (UTC)
- You may want to use
{{!}}
instead of a pipe inside of the template. E.g., {{about||the tasty thing|Fruit#Orange{{!}}the article on fruit}}For the tasty thing, see the article on fruit. - older ≠ wiser 21:11, 14 September 2015 (UTC)
- Thanks, that's exactly what I needed! W3ird N3rd (talk) 09:25, 15 September 2015 (UTC)
Alternate syntax isn't documented?
I notice that the page Stingray has the hatnote:
- This article is about the fish. For the phone tracker, see Stingray phone tracker. For other uses, see Stingray (disambiguation).
The source reveals: {{about|the fish|the phone tracker|Stingray phone tracker|other uses|Stingray (disambiguation)}}
.
I don't see the documentation for this format, which appears to be:
{{About|USE1|USE2|PAGE2|USE3|PAGE3}}
→
Should this be included in this documentation? I do see examples of this (with uses up to USE5) in Template:About/testcases.
Should that page have instead used the following?
{{About|USE1|USE2|PAGE2|other uses}}
→This page is about USE1. For USE2, see PAGE2. For other uses, see About (disambiguation).
The above format is also shown in Template:About/testcases, although only with both USE2 and USE3. But it, too, is not included on this documentation page. Should it be documented?
I also note that this documentation page promises, "For more options, find "{{About}}" in the text below." However, you won't find "{{About}}" anywhere in the text below.