User talk:Sapphaline: Difference between revisions

Line 186: Line 186:

::<code><nowiki><tr></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-tr-element], <code><nowiki><th></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-th-element] and <code><nowiki><td></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-td-element] don’t require an end tag; that’s also why my comment is clean of linter errors. Also, what’s wrong with nested <code><nowiki><ins></nowiki></code>? [[user:sapphaline|<span class=”skin-nightmode-reset-color” style=”color:#c20;text-decoration:underline”>sapphaline</span>]] ([[user talk:sapphaline|<span class=”skin-nightmode-reset-color” style=”color:#236;text-decoration:underline”>talk</span>]]) 08:17, 3 February 2026 (UTC)

::<code><nowiki><tr></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-tr-element], <code><nowiki><th></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-th-element] and <code><nowiki><td></nowiki></code>[https://www.w3.org/TR/2021/SPSD-html52-20210128/tabular-data.html#the-td-element] don’t require an end tag; that’s also why my comment is clean of linter errors. Also, what’s wrong with nested <code><nowiki><ins></nowiki></code>? [[user:sapphaline|<span class=”skin-nightmode-reset-color” style=”color:#c20;text-decoration:underline”>sapphaline</span>]] ([[user talk:sapphaline|<span class=”skin-nightmode-reset-color” style=”color:#236;text-decoration:underline”>talk</span>]]) 08:17, 3 February 2026 (UTC)

::: In Html pages, you are correct, they do not. Wikicode is not an Html page. If you want to do it your way, I can’t stop you. I’ve told you what happens when you do, I’ve give you a working alternative that is also simpler to code and easier for non-Html coders to understand. What you do now, is up to you. [[User:Mathglot|Mathglot]] ([[User talk:Mathglot|talk]]) 10:48, 3 February 2026 (UTC)

::: In Html pages, you are correct, they do not. Wikicode is not an Html page. If you want to do it your way, I can’t stop you. I’ve told you what happens when you do, I’ve give you a working alternative that is also simpler to code and easier for non-Html coders to understand. What you do now, is up to you. [[User:Mathglot|Mathglot]] ([[User talk:Mathglot|talk]]) 10:48, 3 February 2026 (UTC)

== Юбилей ==

Уже 20 раз. Сколько я смогу? [[Special:Contributions/&#126;2026-89502-2|&#126;2026-89502-2]] ([[User talk:&#126;2026-89502-2|talk]]) 13:50, 9 February 2026 (UTC)

It seems so rude and careless to make me, a person with thoughts, ideas, humor, contradictions and life experience to read something spit out by the equivalent of a lexical bingo machine because you were too lazy to write it yourself.

Do you not enjoy the pride that comes with attaching your name to something you made on your own? It’s great!

No, don’t use it to fix your grammar, or for translations, or for whatever else you think you are incapable of doing. Make the mistake. Feel embarrassed. Learn from it. Why? Because that’s what makes us human!

Hi Sapphaline! I noticed your contributions and wanted to welcome you to the Wikipedia community. I hope you like it here and decide to stay.

As you get started, you may find this short tutorial helpful:

Learn more about editing

Alternatively, the contributing to Wikipedia page covers the same topics.

If you have any questions, we have a friendly space where experienced editors can help you here:

Get help at the Teahouse

If you are not sure where to help out, you can find a task here:

Volunteer at the Task Center

Happy editing! JackFromWisconsin (talk | contribs) 14:31, 14 June 2025 (UTC)[reply]

Hello, Sapphaline

Welcome to Wikipedia! I edit here too, under the username Sophisticatedevening, and I thank you for your contributions.

I wanted to let you know, however, that I’ve proposed an article that you started, List of missing aircraft/styles.css, for deletion because it meets one or more of our deletion criteria, and I don’t think that it is suitable for inclusion in the encyclopedia. The particular issue can be found in the notice that is now visible at the top of the article.

If you wish to contest the deletion:

1. Edit the page
2. Remove the text that looks like this: {{proposed deletion/dated...}}
3. Click the Publish changes button.

If you object to the article’s deletion, please remember to explain why you think the article should be kept on the article’s talk page and improve the page to address the issues raised in the deletion notice. Otherwise, it may be deleted later by other means.

If you have any questions, please leave a comment here and prepend it with {{Re|Sophisticatedevening}}. And remember to sign your reply with ~~~~. Thanks!

(Message delivered via the Page Curation tool, on behalf of the reviewer.)

Sophisticatedevening^(talk) 13:20, 2 August 2025 (UTC)[reply]

I can’t tell from code, and nocachein’g the js file didn’t seem to matter? Thanks for trying to help keep it all clean. The talk is a circus. — Very Polite Person (talk/contribs) 16:19, 12 September 2025 (UTC)[reply]

I don’t use it so I don’t know. Perhaps manual archiving is the only possible way here. Sapphaline (talk) 16:19, 12 September 2025 (UTC)[reply]

I bet it’s reading the archive config and it’s set for a max size of 512k:

https://en.wikipedia.org/w/index.php?title=Talk:Killing_of_Charlie_Kirk/Archive_2&action=history

That’s not there yet. — Very Polite Person (talk/contribs) 16:24, 12 September 2025 (UTC)[reply]

Fixed. Sapphaline (talk) 16:26, 12 September 2025 (UTC)[reply]

Ha, ok, turning down the archive size works too. I figured that was default, I just had turned it from 3d (excessive for current situation) to 12h. I guess we’ll see next one. — Very Polite Person (talk/contribs) 16:30, 12 September 2025 (UTC)[reply]

Actually archive 2 is still below the threshold. — Very Polite Person (talk/contribs) 16:31, 12 September 2025 (UTC)[reply]

Looks like we got it sorted:

Good eye on that for what you saw. — Very Polite Person (talk/contribs) 16:44, 12 September 2025 (UTC)[reply]

Nevermind, now I have no idea. — Very Polite Person (talk/contribs) 16:46, 12 September 2025 (UTC)[reply]

It’s gotta be, only logical thing unless the volume/caching/EC’s are that busted. Let them roll to archive 2, for now. — Very Polite Person (talk/contribs) 16:26, 12 September 2025 (UTC)[reply]

https://en.wikipedia.org/w/index.php?title=Talk%3AKilling_of_Charlie_Kirk&diff=1311153953&oldid=1311153701 FYI. — Very Polite Person (talk/contribs) 19:07, 13 September 2025 (UTC)[reply]

There’s currently a Misnested tag with different rendering in HTML5 and HTML4 linter error on this page related to the <q> somewhere in the code, which template:tq produces. Sapphaline (talk) 19:08, 13 September 2025 (UTC)[reply]

I’d suggest posting a new comment section to ask for experienced editors to look rather than editing others content, or ask on the tq talk page. — Very Polite Person (talk/contribs) 19:09, 13 September 2025 (UTC)[reply]

(edit conflict) (talk page watcher) Editing others’ comments to fix lint errors is fine, its pretty common. They didn’t change what they said at all, just the formatting. Tenshi! (Talk page) 19:10, 13 September 2025 (UTC)[reply]

Where are you all even seeing those? I use monobook skin? It just looked like a plain old tq quote. — Very Polite Person (talk/contribs) 19:13, 13 September 2025 (UTC)[reply]

special:pageinfo/Talk:Killing of Charlie Kirk. Sapphaline (talk) 19:13, 13 September 2025 (UTC)[reply]

— Tamzin^{[cetacean needed]} (they|xe|🤷) 11:51, 6 October 2025 (UTC)[reply]

Hello; please take a moment to read over WP:INVOLVED. It’s important editors don’t close discussions they started that have ongoing discussion or involve possibly contentious matters such as at ANI. An uninvolved admin will close the thread when appropriate. Best, CoconutOctopus talk 12:22, 6 October 2025 (UTC)[reply]

I have reverted your changes to Template:ArbComOpenCase. This follows a dedicated format (including the height of subheadings) as approved by the Committee. Changes should be run through the clerks and/or the Committee, who will make changes to these templates themselves. Thanks, Daniel (talk) 09:30, 8 October 2025 (UTC)[reply]

Any place where I can discuss my changes? Sapphaline (talk) 09:32, 8 October 2025 (UTC)[reply]

The Clerks noticeboard. Daniel (talk) 09:33, 8 October 2025 (UTC)[reply]

Hello. This is a message to let you know that one or more of your recent contributions, such as the edit(s) you made to Template:IndyLB roster, did not appear to be constructive and have been reverted. Please take some time to familiarise yourself with our policies and guidelines. You can find information about these at our welcome page which also provides further information about contributing constructively to this encyclopedia. If you only meant to make test edits, please use your sandbox for that. If you think I made a mistake, or if you have any questions, you may leave a message on my talk page. Please test changes in the /sandbox version of templates, then use the /testcases page to test your edits. Check the “Page information” page of the /testcases page for Linter errors. Only after these steps should those changes be moved to the live template. – Jonesey95 (talk) 18:20, 27 October 2025 (UTC)[reply]

• What do you mean by “not constructive”??? That </ul> was intentional because the previous list wasn’t closed otherwise. sapphaline (talk) 18:25, 27 October 2025 (UTC)[reply]

  You left behind a stray </ul> tag that did not have a corresponding opening tag, and you inserted {{ubl}} in a place where it caused div tags to be unmatched, all without doing any testing in the sandbox or on the testcases page. All of this in a live template that is transcluded in 110 articles, causing Linter errors to appear in all of those articles. Please be more careful. – Jonesey95 (talk) 18:58, 27 October 2025 (UTC)[reply]

  Here we are again. You pulled the same stunt at Template:Vertical bar chart, causing Linter errors in dozens of articles. Edit in the sandbox first, then use the testcases page to check for errors. If you are unable to follow this basic procedure, I will request that your template editor privileges be revoked. – Jonesey95 (talk) 19:50, 28 December 2025 (UTC)[reply]

  Why do you think anyone’s going to ban me from editing templates over 2 (minor) mistakes made in a time span of 2 months? sapphaline (talk) 09:35, 29 December 2025 (UTC)[reply]

  And you could just fix it yourself instead of biting me. sapphaline (talk) 09:52, 29 December 2025 (UTC)[reply]

  It sounds like you need to re-read the template editor guidelines. Please do so. – Jonesey95 (talk) 14:48, 29 December 2025 (UTC)[reply]

Template:Nonstandard list has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. — GhostInTheMachine ^{talk to me} 10:38, 29 October 2025 (UTC)[reply]

Hello Sapphaline.

In your partial reversion of one of my edits to Demographics of Germany you were good enough to provide an edit summary, which said, “these are not row headers though”. You removed scope="row" from the left-hand cells on several tables. But of course they are row headers. To find the life expectancy by period for 1960–1965, one looks in the Life expectancy in years for Germany, 1950–2015, by five-year period table for the row headed “1960–1965”, and on that line we see “70.0” (the data in the Life expectancy column).

I did make at least one mistake with a column heading in another table; thank you for correcting it to !scope="col"| Life expectancy. But the widespread removal of scope="row" seems incorrect to me. How can they not be headers? — JohnFromPinckney (talk / edits) 22:27, 31 October 2025 (UTC)[reply]

they are row headers – how so when the “1960-1965” cell in your example is already named by the “Period” column header? sapphaline (talk) 10:42, 1 November 2025 (UTC)[reply]

The “Period” column header is the header for the column containing “1960-1965”. The “1960-1965” row heading is the heading for the row containing “70.0”. — JohnFromPinckney (talk / edits) 22:19, 3 November 2025 (UTC)[reply]

It appears that your proposed split has gained consensus. Once you have finished with all the splitting etc., the new pages will all need to be protected per WP:CTOP. Either ping me or post a request at WP:RfPP. FWIW, I think the split is overdue. –Ad Orientem (talk) 04:26, 4 November 2025 (UTC)[reply]

Hello Sapphaline. I’m just letting you know that I closed the split proposal you started a month ago with consensus to split. Feel free to start splitting the article. {{being split}} didn’t display properly, so I left {{split}} in place. Chess enjoyer (talk) 04:40, 4 November 2025 (UTC)[reply]

Whoops, didn’t see @Ad Orientem‘s post! Chess enjoyer (talk) 04:48, 4 November 2025 (UTC) [reply]

@Chess enjoyer No worries. –Ad Orientem (talk) 04:50, 4 November 2025 (UTC)[reply]

Done. sapphaline (talk) 09:59, 4 November 2025 (UTC)[reply]

Thanks for carrying out the split. Your edit summaries at the new child articles are probably compliant with the Wikimedia Terms of Use for copying content, but just to make sure, why not follow our WP:Copying within Wikipedia guideline next time, and use these words when copying content (large or small) to other articles, in order to fulfill the required attribution to the original authors:

Copied content from [[Page name]]; see source page's history for attribution.

No need to add additional attribution to the edit summaries of the child pages at this point; just something to keep in mind for next time. Thanks, Mathglot (talk) 05:35, 10 November 2025 (UTC)[reply]

PLEASE make sure you use edit summaries, particularly when you are modifying someone else’s comment as you did here. I totally understand why you moved their comment… But without an edit summary, that can be concerning. Zackmann (^{Talk to me}/_{What I been doing}) 18:31, 15 December 2025 (UTC)[reply]

Mind explaining why you did this edit on my talk page without a reason? Freedoxm (talk · contribs) 15:12, 16 January 2026 (UTC)[reply]

Because this emoji overlaps page action buttons in Monobook, and I wanted to hide it in my common.css.Also, edits can’t be “unauthorized”. sapphaline (talk) 15:15, 16 January 2026 (UTC)[reply]

Because this emoji overlaps page action buttons in Monobook even if it overlaps it, it’s not your talk page, and you shouldn’t have done that. A better option would have been telling me to do the edit instead. Freedoxm (talk · contribs) 15:17, 16 January 2026 (UTC)[reply]

+1 Mind explaining this new edit as well? As above, you could have just requested the edit via communicating with me on my talk page. I’m going to ask you to disengage from further edits without requesting me (even if it was done in WP:GF). If you continue with such behavior, I’m afraid I will have to bring this to ANI. ^NeoSyria\Freedoxm (talk · contribs) 02:53, 24 January 2026 (UTC)[reply]

Please read Wikipedia:Ownership of content. sapphaline (talk) 07:22, 24 January 2026 (UTC)[reply]

WP:OWN has nothing to do with any talk page; No one, no matter what, has the right to act as if they are the owner of a particular article (or any part of it) My talk page is my talk page, it is not your talk page, it is not yours to hold responsibility, and it is not an article. ^NeoSyria\Freedoxm (talk · contribs) 07:26, 24 January 2026 (UTC)[reply]

“it is not an article” –

Wikipedia offers wide latitude to users to manage their user space as they see fit. Nevertheless, they are not personal homepages, and are not owned by the user. They are still part of Wikipedia and must serve its primary purposes; in particular, user talk pages make communication and collaboration among editors easier. These functions must not be hampered by ownership behavior.

sapphaline (talk) 07:36, 24 January 2026 (UTC)[reply]

These functions must not be hampered by ownership behavior Nevertheless, I haven’t ever declared to be the “owner” of my talk page, even if you think I implied; I’m not tolerant of people randomly editing someone else’s talk page beyond discussion that in some cases, are unexplained, even with WP:OWN. Disengaging. ^NeoSyria\Freedoxm (talk · contribs) 07:43, 24 January 2026 (UTC)[reply]

It doesn’t seem to affect more than today’s account, and seems like it might affect someone unrelated, too… ~Lofty abyss 09:22, 18 January 2026 (UTC)[reply]

Could you revoke their talk page access then? sapphaline (talk) 09:23, 18 January 2026 (UTC)[reply]

@Lofty abyss: special:contributions/~2026-40194-5. sapphaline (talk) 10:24, 19 January 2026 (UTC)[reply]

See Template:Textdiff. Polygnotus (talk) 15:19, 1 February 2026 (UTC)[reply]

Sapphaline: I was going to post about this, but I see Polygnotus beat me to it. Nevertheless, I will expand on it. When you raised WP:VPP § Proposal #2, you included a Current Text – New Text comparison. Bravo; that is a great way to show what you want changed. However, the method you chose to do the side-by-side comparison—a home-brew Html table—was a big headache, as the code had numerous errors which screwed up syntax highlighting for the entire rest of the discussion (and for all subsequent discussions on the page). There were multiple problems, including doubly-embedded <ins> tags, unterminated Html tags, invalid sequencing (nesting order) of Html end tags, and others. (Note that if you are used to dropping final <tr>, <th>, or <td> tags on Html pages, this is very fragile on mediawiki Talk pages, so if you *must* use Table Html in wikicode, please make sure you end every Html tag, and in proper nesting sequence. And don’t nest <ins> tags.

I made one attempt to fix it (diff), and it did fix the highlighting problem, but somewhere I screwed up the indentation, and it was just too squirrely to spend any more time on, so I self-reverted. So now, the bad code is back again, and that page will continue to have broken syntax highlighting until the Rfc is finally archived, who knows when.

In the future, as Polygnotus said much more briefly, please use Template:Text diff. Thanks, Mathglot (talk) 23:24, 2 February 2026 (UTC)[reply]

@Mathglot Why is broken html actually important on a discussion page? It doesn’t bother my computer; the page loads just fine. Even if it doesn’t, I’ve seen the result of linter errors – and they tend to just make the page harder to read? But it’s trivial to workaround. I’m not sure what relevance syntax highlighting has – it’s a wonderful convenience for those who chose to use it, sure, but not, overall, that big of a deal when it breaks, especially given that it’s just a discussion page. And, obvs, if it’s not breaking the archive, it hardly seems worth caring about. Hardly headache worthy! GreenLipstickLesbian💌🧸 06:05, 3 February 2026 (UTC)[reply]

<tr>[1], <th>[2] and <td>[3] don’t require an end tag; that’s also why my comment is clean of linter errors. Also, what’s wrong with nested <ins>? sapphaline (talk) 08:17, 3 February 2026 (UTC)[reply]

In Html pages, you are correct, they do not. Wikicode is not an Html page. If you want to do it your way, I can’t stop you. I’ve told you what happens when you do, I’ve give you a working alternative that is also simpler to code and easier for non-Html coders to understand. What you do now, is up to you. Mathglot (talk) 10:48, 3 February 2026 (UTC)[reply]