Help talk:Section: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
m Reverted 2 edits by 69.132.190.208 (talk) to last revision by Ojorojo (TW)
→‎Thanks: new section
Tags: Mobile edit Mobile web edit
Line 91: Line 91:
:{{replyto|Ojorojo}} Anchors must be unique within a page. If the same anchor is used two or more times, only the first one is recognised. This is a fundamental feature of HTML (the {{tlx|anchor}} template makes an <code>id=</code> attribute, so see HTML 5.1 spec [https://www.w3.org/TR/html51/dom.html#the-id-attribute section 3.2.5.1. The <code>id</code> attribute]) and is built into all modern web browsers, we cannot change that behaviour. All I can suggest is that you add some distinguishing characteristic, such as {{tlx|anchor|1940sA}}, {{tlx|anchor|1940sB}} or similar. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 16:27, 11 July 2019 (UTC)
:{{replyto|Ojorojo}} Anchors must be unique within a page. If the same anchor is used two or more times, only the first one is recognised. This is a fundamental feature of HTML (the {{tlx|anchor}} template makes an <code>id=</code> attribute, so see HTML 5.1 spec [https://www.w3.org/TR/html51/dom.html#the-id-attribute section 3.2.5.1. The <code>id</code> attribute]) and is built into all modern web browsers, we cannot change that behaviour. All I can suggest is that you add some distinguishing characteristic, such as {{tlx|anchor|1940sA}}, {{tlx|anchor|1940sB}} or similar. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 16:27, 11 July 2019 (UTC)
::I figured as much, but thanks for confirming it. —[[User:Ojorojo|Ojorojo]] ([[User talk:Ojorojo|talk]]) 17:20, 11 July 2019 (UTC)
::I figured as much, but thanks for confirming it. —[[User:Ojorojo|Ojorojo]] ([[User talk:Ojorojo|talk]]) 17:20, 11 July 2019 (UTC)

== Thanks ==

Will follow your advise always. Thanks boss [[User:Pankaj verma 23|Pankaj verma 23]] ([[User talk:Pankaj verma 23|talk]]) 16:48, 18 July 2019 (UTC)

Revision as of 16:48, 18 July 2019

WikiProject iconWikipedia Help NA‑class High‑importance
WikiProject iconThis page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.
NAThis page does not require a rating on the project's quality scale.
HighThis page has been rated as High-importance on the project's importance scale.

mediawiki - Sections HTML code convertion problem

Greetings ... im havving a REALLY annoying problem. I have my wiki in a local server and in an server somewhere else.

The CSS are exacly the same BUT, on my local wiki the sections text are in blue (correct) and in the outside server are in black (wrong). even if i modify the main.css in the outside server in wont change to blue. if i apply any other stype, line background color, or underline, etc .. it will apply, but the color it refuses to change. i even tryied to use "!importante" and nothing (locally the the !import works just fine).

I looked into the generated page code to try to figure it out and this is that i found:

In my local server, the section generated code looks like this

<h1>
	<span class="mw-headline" id="Overview"> Overview </span>
</h1>

In the other end ... on my external server the section generated code looks like this

<h1>
	<span class="mw-headline" id="Overview">
		<a style="text-decoration:none;color:black" name="Overview"> Overview </a>
	</span>
</h1>

So.. i am almost sure that the problem is the style defined in the anchor. the question is .. why is that there??? i also found something interesting that may be a clue (for someone but not for me)

I found 2 wikis refering to "Help:Section"

http://en.wikipedia.org/wiki/Help:Section
in this one (the one we are right now), they say that section work like in my local wiki
http://meta.wikimedia.org/wiki/Help:Section
in this one it says that it works like on my external server


Is this any clue to anyone?

Thanks in advance for any help you can give me.

- Miguel (17-02-2011 14:34)

Notice of RfC on single subsections

An issue related to single subsections, which watchers of this page may be interested in, is now up for discussion in an RfC which can be found at Wikipedia talk:Manual of Style#RfC on single subsections. Feel free to come and participate. - adamstom97 (talk) 00:21, 26 August 2018 (UTC)[reply]

Adding an anchor point to the TOC

Is there a way to add an anchor point (with defined text) which will be shown in the TOC, without actually creating a header? In other words, if I have a huge table, how do I link parts of the table in the TOC, without actually breaking the table into parts so as to accommodate section headings? Rehman 09:15, 21 March 2019 (UTC)[reply]

Yes, but it's nasty and causes WP:ACCESSIBILITY problems so I'm not going to describe it. --Redrose64 🌹 (talk) 17:41, 21 March 2019 (UTC)[reply]
Hi User:Redrose64. The table in question is at Template:Infobox_power_station#Parameters. What I'm trying to improve is the ease of directly going to the subsections such as "Geothermal power stations", etc. So technically, contrary to what I said above, there are headings, but they are not necessarily wrapped with ==xx==. It is possible to include those headings in the table, such as "Geothermal power stations", in the TOC? Rehman 02:39, 22 March 2019 (UTC)[reply]
Making anchors is easy, for instance with the row
|-
| colspan="3" style="background-color:#FFFFE6;text-align:center;" | '''Lead section''' (used by all power station types)
you can add the attribute id="Parameters Lead section" either directly after the |- marker for the new row, or somewhere between the two pipes on the next line. Such anchors won't show in the TOC. You could make a pseudo-TOC, as has been done at Template:Convert/list of units (see Template:Convert#All units). Alternatively, you could mark them up as actual headings, see for example Template:Infobox settlement#Parameter names and descriptions - here, the orange-background rows like "Name and transliteration" are ===level 3 headings=== and they do show in the main TOC. --Redrose64 🌹 (talk) 14:58, 22 March 2019 (UTC)[reply]
Thanks User:Redrose64. Making it lvl 3 or 4 seems like the best way. It generates a bit of extra space before the header, but it isn't too much of a problem. Cheers. Rehman 14:12, 25 March 2019 (UTC)[reply]

Semi-protected edit request on 21 April 2019

Change Owen Benjamin lives in Saranac Lake to Owen Benjamin lives in Washington State. 67.249.173.160 (talk) 19:05, 21 April 2019 (UTC) : Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate.  Not done: this is the talk page for discussing improvements to the page Help:Section. Please make your request at the talk page for the article concerned.Please state the page the edit should be made on RhinosF1(chat)(status)(contribs) 21:47, 21 April 2019 (UTC)[reply]

@RhinosF1: This isn't a {{subst:ESp|xy}} situation, it's one for {{subst:ESp|mis}}. --Redrose64 🌹 (talk) 07:42, 22 April 2019 (UTC)[reply]
Redrose64, I didn't see that in the options on edit protected helper RhinosF1(chat)(status)(contribs) 07:43, 22 April 2019 (UTC)[reply]
 Changed RhinosF1(chat)(status)(contribs) 07:45, 22 April 2019 (UTC)[reply]
Eh? It's there, and has been since it was added with the rest of the responses back in February 2014. --Redrose64 🌹 (talk) 16:03, 22 April 2019 (UTC)[reply]

Reasons to use or not to use TOC

This help page doesn't explicitly state when __TOC__ should or shouldn't be used. It states that using __TOC__ can force the table of contents to appear if fewer than four sections appear. It states that __TOC__ can aid positioning the ToC. It states __TOC__ can cause accessibility problems (but it doesn't state how).

For example, is it correct, incorrect, or debatable to add __TOC__ when three or fewer lengthy sections exist on an article or talk page, to assist clarity of page content? Thank you, A145GI15I95 (talk) 01:57, 22 April 2019 (UTC)[reply]

It intentionally does not lay down explicit rules because there are always going to be situations when a rigid rule is unsuitable. As for the accessibility problems, the actual phrase used at WP:TOC#Positioning the TOC is if there is any text at all between the TOC and the first heading, this will cause problems with accessibility, which is not at all the same as saying that __TOC__ can cause accessibility problems. In short, text between the TOC and the first heading is not read out by screen reader software, so it's as if it is completely hidden. --Redrose64 🌹 (talk) 07:51, 22 April 2019 (UTC)[reply]
What's included here is what we were able to reach consensus on in this recent discussion. Everything else is debatable. ~Kvng (talk) 13:39, 30 April 2019 (UTC)[reply]

Sony crakel

I had a pyramid with a line could not watch show so I deleted it now I can't get it back Karen sweetnam (talk) 09:36, 28 June 2019 (UTC)[reply]

Multiple Template:Compact ToC on the same page

This version of the List of blues musicians [1] was set up with a {{Compact ToC}} for each of the first two sections (tables with the necessary anchors). The first ToC works fine, but when a letter is clicked on the second ToC, it links to that letter in the first section table and not the second. I've removed them for now, but is it possible to direct the second ToCs to the second section table? —Ojorojo (talk) 19:06, 10 July 2019 (UTC)[reply]

@Ojorojo: Anchors must be unique within a page. If the same anchor is used two or more times, only the first one is recognised. This is a fundamental feature of HTML (the {{anchor}} template makes an id= attribute, so see HTML 5.1 spec section 3.2.5.1. The id attribute) and is built into all modern web browsers, we cannot change that behaviour. All I can suggest is that you add some distinguishing characteristic, such as {{anchor|1940sA}}, {{anchor|1940sB}} or similar. --Redrose64 🌹 (talk) 16:27, 11 July 2019 (UTC)[reply]
I figured as much, but thanks for confirming it. —Ojorojo (talk) 17:20, 11 July 2019 (UTC)[reply]

Thanks

Will follow your advise always. Thanks boss Pankaj verma 23 (talk) 16:48, 18 July 2019 (UTC)[reply]