Wikipedia talk:Manual of Style/Self-references to avoid

	This page falls within the scope of the Wikipedia:Manual of Style, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the Manual of Style (MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.Manual of StyleWikipedia:WikiProject Manual of StyleTemplate:WikiProject Manual of StyleManual of Style
	This page falls under the contentious topics procedure and is given additional attention, as it closely associated to the English Wikipedia Manual of Style, and the article titles policy. Both areas are subjects of debate. Contributors are urged to review the awareness criteria carefully and exercise caution when editing.
	For information on Wikipedia's approach to the establishment of new policies and guidelines, refer to WP:PROPOSAL. Additionally, guidance on how to contribute to the development and revision of Wikipedia policies of Wikipedia's policy and guideline documents is available, offering valuable insights and recommendations.

Archives

Archive 1	Archive 2	Archive 3
Archive 4

This page has archives. Sections older than 90 days may be automatically archived by when more than 4 sections are present.

Sagan standard

It's not as cut-and-dried as you make it sound, and you'd do better to join the discussion at WT:Manual_of_Style#Hatnotes_from_Mainspace_to_Wikipedia, raising this specific example. E Eng 05:13, 10 May 2021 (UTC)[reply]

Will do, and thanks for the feedback. It was more surprising that even after they acknowledge reading this page that they still chose to restore it naked without any {{selfref}} wrapper or using the selfref= parameter for {{for}}... nevermind that our readers don't likely understand why we'd be putting a link like that front and center. Thank you for the pointer to that other discussion. =) —Locke Cole • t • c 05:24, 10 May 2021 (UTC)[reply]

Is explaining terminology of the article permissible?

Can, or should, an article use phrasing such as "To simplify matters, the referents of wa and ga in this section are called the topic and subject respectively" (as seen in Japanese grammar)?

In other words, can an article decide or explain the terminology that the article will proceed to use thereafter?

Whether the answer is "yes/no/it depends", I'd propose that such an explanation should be added as a section in this "Manual of Style/Self-references" page. — JKVeganAbroad (talk) 02:38, 21 June 2021 (UTC)[reply]

Well, at MOS:CONVERSIONS the example is given that an article on American football should not tiresomely convert every measurement in yards to metric, but instead just explain in a note what a yard is and leave everything in yards. But then our article American football tiresomely converts everything from yards to meters, so go figure. Certainly there will be math articles that explain notational conventions (though I can't name any just now), but of course math articles take a somewhat unusual narrative approach ("Suppose that XYZ and ABC; then JKL must be ...").
So in summary I don't really have an answer for you, other than to say I think some editors are much too huffy about the "presumption" of addressing the reader, and that you should just do what you think best and see how other editors respond. There's probably some hatnote template you're supposed to use for that, but if there is I can't find it. Maybe David Eppstein knows. EEng 21:03, 21 June 2021 (UTC)[reply]
- I've definitely seen mathematics articles that say something similar about what convention they'll be following in situations where there is more than one reasonable choice — if this is something you care about, there's a new move-discussion at Talk:Trapezium and Trapezoid that you might want to participate in, without much need for mathematical expertise. But I don't know of any hatnotes for that purpose. —David Eppstein (talk) 21:12, 21 June 2021 (UTC)[reply]
It's a very common thing in technical writing. I'd expect that many editors who know specialist subject material will use that style of specifying conventions practically by instinct. Thinking about sections and whole articles as structured prose with a logical flow of ideas, rather than as line-by-line pileups of facts, is a good thing that we should encourage. Moreover, it doesn't run into the problems that actually make self-references bad. It doesn't get in the way of reusing the content on another site, and it makes just as much sense when printed on paper as when read on a screen. XOR'easter (talk) 18:05, 22 June 2021 (UTC)[reply]
- Overall, this seems like an acceptable practice. Thanks for the community response! — JKVeganAbroad (talk) 00:53, 23 June 2021 (UTC)[reply]

Discussion of allowing self-reference in list article criteria

I reverted the addition of an exception to WP:SELFREF for list article criteria, and have started a discussion here. Feel free to join the discussion! — hike395 (talk) 13:08, 28 July 2022 (UTC)[reply]

There is a new proposal on the table for resolving a contradiction between MOS:SELFREF and WP:SALLEAD. Please feel free to join in the discussion here. Thanks! — hike395 (talk) 11:56, 13 August 2022 (UTC)[reply]

Referencing in-article images

At this revision of Judeo-Malay, a list of the numbers from 1 to 6 are given along with their romanized names in Judeo-Malay (along with a claim that they're also given in Malay, which they weren't, but I fixed that in a later revision). The list is introduced with "Below are the numbers of Judeo-Malay or Malay written in Hebrew characters by Rahamim Jacob Cohen." But the numbers "below" aren't written in Hebrew characters, their names are romanized. However, in the infobox is an image of the notebook page that is written in Hebrew characters and that is the source of the names that are romanized in the list.

My current revision is this. I've created a table and added the Standard Malay names of the numbers for comparison. The introduction is "Below are the numbers 1–6 in Judeo-Malay, transcribed from Cohen's notes, and in Standard Malay:". I'd like to specify that the numbers are romanized from the notebook page but I don't know how to reference it in a way that's in the spirit of avoiding self-references. I could write "romanized from the forms in Hebrew characters in the image in the infobox", but should the article give the an impression of being aware that is has an infobox?

I could remove the image from the infobox and put it in that section of the text. But then how would I refer to it? I can't write "the image to the right" because on a small mobile device it's going to be below, and I can't say "the image below" because on a desktop monitor it's probably going to be to the right. Largoplazo (talk) 22:10, 9 July 2023 (UTC)[reply]

Postscript: I just found MOS:SEEIMAGE. It says "Don't refer to image orientation such as left, right, above, or below. Image placement varies with platform and screen size, especially mobile platforms, and is meaningless to screen readers. Instead, use captions to identify images." So it seems to be telling me I can't refer to it at all. The third sentence is weird, because, given the previous two sentences, I thought it was going to go on to advise as to handle a situation where one needs to refer to the contents of an image, but the sentence instead offers the platitude that's applicable in any circumstances, that images should have captions. Well, maybe it does help: I've now amplified the information given in the caption so that the reader has a chance of putting two and two together, in this revision. Largoplazo (talk) 22:14, 9 July 2023 (UTC)[reply]

Note that ..., It is important to ..., Surprisingly ..., Of course ...

I noticed that the subsection was added several years ago but I disagree with "Neutral cross-references (See also Cymric (cat). are permissible". In fact, I don't think they are ever permissible and are always better reworded. Are there any supporters? Iterresise (talk) 08:03, 6 October 2023 (UTC)[reply]