User talk:Zinnober9

Archives Archive 1 (2017 - 2019) Archive 2 (2020 - 2022)

I thank you greatly for fixing the small tags that had gotten messed up on my AWB run -- I thought I had gone back and caught them all. Are you working off a database report, or some tool that provides a list of all broken tags? If so, I would like to see it as well; I've been making a shitload of edits on back issues today and I am not sure that I have caught all the errors.

By the way, if you are interested in doing a large volume of fairly boring (but necessary) edits, I have a treasure trove of them. jp×g 04:53, 9 January 2023 (UTC)[reply]

@JPxG If the messed up tags were selfclosing smalls (<small/>), then they are all repaired and weren't but a few (Selfclosing tags are not infrequent, but are a well maintained error; usually none to very few running across the site, and they don't last long with various editors pouncing on them quickly).

I have a few links for you it seems! :)

WP:LINT (the project's page)

The "lint" errors listed on Wikipedia (max count of each type of error per article page caps out at 21)

The main page I use is https://fireflytools.toolforge.org/fireflytools/linter/enwiki which is just the errors listed in the previous link, but broken down by namespace for a condensed, more exact, count of each error type (updates every 15 minutes). This is how I spotted the three Signpost errors you speak of.

I also utilize the Page Information of various pages (link under Tools on the left side of the site) in conjunction with these, since many pages have multiple types of errors, and I like to clear a page in preferably one edit. If there are any errors, there will be a "Lint errors" section like this at the bottom with a count of each type. If there are errors, then I use the last link, Lint errors on page, in the External Tools section just below it for the listout of all errors of all types on this specific page, along with some extra info, (obsolete font, missing end tag (b), etc). Most I can find with Ctrl+F while editing a page, but some errors get sneaky, and the link to the error it provides (I'd open it in a new tab) helps me find some the location on page of some things. The listout also serves as safety net/check for me after I've edited a page.

I'd be interested in knowing what sort of things you have. While I am content with the focuses of lint I've been cleaning so far, I do enjoy some variation, and need a change of task/scenery/etc every so often. Zinnober9 (talk) 07:58, 9 January 2023 (UTC)[reply]

These errors were probably all cleaned up before you started your de-linting work. See the last bullet at mw:Help:Lint_errors/bogus-image-options for invalid options in gallery tags. – Jonesey95 (talk) 01:30, 13 January 2023 (UTC)[reply]

The replacements for User:Kaiba in this edit did not work. The opening span tags were missing a quote mark, the closing tags were missing a >, and a font size of 3 pt should probably have been replaced with small, not medium. Are you using scripts or just typing? If the latter, you need to inspect your results very carefully for typos, and make sure to use LintHint before your save. – Jonesey95 (talk) 14:17, 8 February 2023 (UTC)[reply]

I hadn't gotten LintHint to work in attempts past, but I figured it out today and it's working for me now. Will utilize that in my edits as an added safeguard. I had unexpected interruption and I messed up last night. I appreciate you catching those. Zinnober9 (talk) 20:16, 8 February 2023 (UTC)[reply]

I'm glad you got it working. It doesn't work for every single error, but it is helpful for catching remaining errors and highlighting typos that I have made before saving. It is also helpful for highlighting the text containing an error, unless that text is wrapped in a template like {{archive top}} or similar, in which case you need to depend on the syntax highlighter or Special:ExpandTemplates. Isn't this fun? – Jonesey95 (talk) 20:35, 8 February 2023 (UTC)[reply]

Yeah, I've gotten so that if something is in a wrapper and isn't something I immediately spot, or is something I suspect there are multiples of (since they tend to only flag the first within the wrapper) I copy that potion of the text minus the wrappers to my sandbox and figure it out in the sandbox. Zinnober9 (talk) 20:58, 8 February 2023 (UTC)[reply]

Hey! This is just a reminder that, when adding the {{center}} template, you need to be careful about how you implement it. Center can only take one argument, being the input text, and any other arguments it receives are essentially lost (not displayed). Some text can have an = in it, such as inside a html tag. This means that when you attempt to do something like {{center|<span style="color:#ABC">Test</span>}}, the software attempts to treat this as you saying the arg <span style= has the value "color:#ABC">Test</span>. The template doesn't know how to handle that, and so nothing gets displayed. To fix this, you should put 1= at the start. For a visual example of the effect this has, compare this section before and after 1= was added.

Generally, the main times this becomes a concern is when the equals is part of a link (E.g. [https://example.com?a=b]), html tag (see above), or just regular text. Any equals sign that is inside of a sub-template shouldn't be a problem. If you aren't sure if something needs it, hit Show Preview and look for any preview warning messages where the center templates are or for the Pages using center with no arguments category. Don't worry, I've already cleaned up any cases of this before, so there's no need to go back. This is just a note for the future. Aidan9382 _(talk) 08:58, 12 February 2023 (UTC)[reply]

Yep, thanks. I run across that every now and then, but infrequently enough that it catches me offguard at times. Thanks for the correction, sorry for the error. Zinnober9 (talk) 09:23, 12 February 2023 (UTC)[reply]

	The Special Barnstar
	Thanks for all you do on talk pages! I especially like seeing you remove WP:NOTAFORUM violations. Zoe Trent Fan🎤💍 21:27, 23 February 2023 (UTC)[reply]

An article you recently created, List of 2023 MNL statistics, is not suitable as written to remain published. It needs more in-depth coverage about the subject itself, with citations from reliable, independent sources in order to show it meets WP:GNG. It should have at least three, to be safe. And please remember that interviews, as primary sources, do not count towards GNG. Please see WP:NOTSTATS.(?) Information that can't be referenced should be removed (verifiability is of central importance on Wikipedia). I've moved your draft to draftspace (with a prefix of "Draft:" before the article title) where you can incubate the article with minimal disruption. When you feel the article meets Wikipedia's general notability guideline and thus is ready for mainspace, please click on the "Submit your draft for review!" button at the top of the page.Onel5969 ^{TT me} 12:11, 21 March 2023 (UTC)[reply]

@Onel5969 I have zero personal interest in the page and do not want the draft. I found that 2023 Myanmar National League was overrun by that weekly statistical data, and that for the 2022 season, it had a similar standalone page for the weekly breakdown with similar level of sourcing, so I moved it out to its own page in the hopes that the people interested in the subject would complete the page to satisfaction.

If the only thing needed is two more sources, I could attempt to find two sources to meet GNG, but otherwise I have no further interest in the page, and only created it for the page overflow need. The main thing that I do not want to see is this weekly breakdown of data returning to the 2023 Myanmar National League page.

Otherwise if the page needs more work than that, I'm happy to release the page to a public draft, or you may give it to User:Vilnae867 since they worked on and updated the page quite a bit. Zinnober9 (talk) 15:38, 21 March 2023 (UTC)[reply]

Your edit of 03:51, 24 January 2023 (UTC) of Template talk:Did you know/Tapis (Indonesian weaving style) may have resulted in a stripped </div> tag in Template talk:Did you know daily log/2011 August 6. ExpandTemplates with the markup

{{Template talk:Did you know/Tapis (Indonesian weaving style)}}

results in very little output and includes the stripped tag. —Anomalocaris (talk) 19:11, 21 April 2023 (UTC)[reply]

I was aware of that at the time, but had since forgotten. Thank you. I wasn't sure why it did that (and I feel like it was just as broken appearing before I changed things). At the time, I had looked at other similar pages appearing on that August page for the IF statement format used and applied it to Tapis since it was missing. Since it fixed Tapis, and left August in better condition than when I found it, I moved on thinking to come back later if I had an idea, or if someone else found a solution before I did.

Out of curiosity just now, I removed a set of inner noincludes that weren't appearing in other cases, and that has cleared the div error on August, and the entry is appearing on August as others do, so I think this works. While I don't fully know why that fixed it, my guess is that the inner set of noincludes were messing with the noincludes in the IF statements. Hopefully this adjustment hasn't caused something else. It's comforting that it looks like the other entries in both places though. Zinnober9 (talk) 20:06, 21 April 2023 (UTC)[reply]

Right, I don't think <noinclude>...</noinclude> should nest inside <noinclude>...</noinclude>, so removing the inner ones makes sense. Thank you for taking care of this. —Anomalocaris (talk) 22:47, 21 April 2023 (UTC)[reply]

A discussion is taking place as to whether the article List of 2023 MNL statistics is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/List of 2023 MNL statistics until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.

Robert McClenon (talk) 00:15, 26 May 2023 (UTC)[reply]

@Robert McClenon As I've stated previously, (three sections above here), I have zero interest in this page. I created it out of necessity to move this overwhelmingly long content out of 2023 Myanmar National League, as it swallowed up the page. I saw that 2022 season had a similar setup page, so I moved the 2023 content to a new page. That's it. End of story. Stop messaging me about this page.

@Vilnae867 is the major contributor to this page and has the interest. I do not. If there is a way to relinquish whatever "creatorship/ownership" of this page to them, I'm happy to do so.

Zinnober9 (talk) 00:47, 26 May 2023 (UTC)[reply]

User:Zinnober9 - Yes. We know. We know. I get such messages from time to time saying that my drafts are about to be deleted, and I didn't create the drafts, but only renamed them. I am sure that User:Onel5969 gets similar stupid messages. The messages are generated automatically by Twinkle, which semi-automates all sorts of notification tasks, and usually gets them right. If the messages really bother you, you can delete them, or you can move them to the user page of User:Vilnae867. Twinkle gets the originator right more often than it gets it wrong; you can ridicule them if you want to. Robert McClenon (talk) 01:01, 26 May 2023 (UTC)[reply]

Thank you. Not frustrated with you, just frustrated by this one page and it's progress since. I appreciate your reply, and hope you have a wonderful weekend. Zinnober9 (talk) 01:12, 26 May 2023 (UTC)[reply]

I spent my time to register this Statistics. Do you think it is easy to register? Who is scored, who is assist? Why so serious? I just tried to find the source. aright you are genius. Vilnae867 (talk) 12:06, 2 June 2023 (UTC)[reply]

you deleted all my data ......f Vilnae867 (talk) 12:08, 2 June 2023 (UTC)[reply]

I deleted nothing. Reread the above. I moved existing content (changing nothing) to a new page, it got new page reviewed and failed to pass due to lack of sources and was nominated by the reviewer for deletion. Discuss with them, as I have no personal interest in this topic, and no interest in the discussion about keeping or removing these stats. Zinnober9 (talk) 23:44, 3 June 2023 (UTC)[reply]

Well, I certainly don't want any lint errors on my talk page! Thank you for cleaning that up for me, I guess. I really don't see much difference, but then I am not versed on what a lint error is...anyway, have a great rest of your day! Cuprum17 (talk) 01:02, 31 May 2023 (UTC)[reply]

WP:Lint are minor syntax errors, or use of older code that is not HTML5 compliant, and most of the time correcting these errors won't change anything visually. Correcting lint would be the equivalent to dotting the "i"s and crossing the "t"s. Some visually noticeable errors I can think of off the top of my head are dropped italics/bold tags, or an unclosed text color/font/size that unintentionally changes everything after it.

The tidy font error though, which is how I discovered your page, is when links (usually signatures) are written in the <font>[[link]]</font> format with the color specified outside of the link. Browsers don't agree on how to display the colors written this way, and some browsers display it with the specified colors, others defaulting back to the standard link blue. This would have been the only possible issue I adjusted on your page that would have been visually possible to see, since the other things I adjusted were updating the outdated <center> to some HTML5 compliant alternatives. Zinnober9 (talk) 08:26, 31 May 2023 (UTC)[reply]

Hi Zinnober9. I recently saw you corrected a mistake I had made on series of page creations, * ]] *.

I've somehow missed that you were making all these corrections until now. I am currently going through the pages before I move them from draft to article, and checking if I have more of these errors.

However I just wanted to thank you for having corrected the errors, and wish you a nice evening :) Thomediter (talk) 23:19, 8 June 2023 (UTC)[reply]

I saw one set on Draft:Aakirkeby (Nomination district) (that I just took care of) but otherwise I don't see any other tracked syntax issues in the series, so I think what you've released so far should be all fine syntax-wise. Sorry if I sounded frustrated earlier, I just was surprised at how many there were, and had a few IRL things I was mulling over while editing. Thank you for your kind message, and I hope you have a great weekend! Zinnober9 (talk) 00:22, 9 June 2023 (UTC)[reply]

Hi there! Nice to make your aquaintance and many thanks for helping me out with the signature. I was thinking I might try lower case letters... lol might as well give it a go!

thanks again friend! : ) ΤΕΡΡΑΣΙΔΙΩΣ(^Ταλκ) 12:24, 9 July 2023 (UTC)[reply]

Take a look at your lintfix of List of viceroys of New Spain. You didn't account for the rowspan. I was working on the page at the same time, so I overwrote your version. —Anomalocaris (talk) 02:26, 23 October 2023 (UTC)[reply]

Wikitables are so damn easy to mess up that they get even the best of us... Thanks for catching that. Zinnober9 (talk) 02:31, 23 October 2023 (UTC)[reply]

(edit conflict) When fixing fostered content lint errors, always look at the page history and find out what caused it. Just putting in a cell pipe or a table close might be the answer, but it might not. Gotta find out what went wrong first. Same is true for table tags to be deleted. —Anomalocaris (talk) 02:35, 23 October 2023 (UTC)[reply]

Hello, Zinnober9,

Please do not tag expiring drafts early. We go by the time and date of the last human edit to the page and we're pretty strict about it because we have several admins and editors dealing with expiring drafts and we need to have some system to coordinate our efforts. We actually have a list we work with, User:SDZeroBot/G13 soon that is generated by a bot so nothing falls through the cracks. Thanks though for your help. Liz ^{Read! Talk!} 04:51, 4 November 2023 (UTC)[reply]

Hey Zinnober9, I'm the AfC reviewer who tagged that page under CSD G6. I've accepted the draft due to the significant improvements that were made after the declines. With that in mind, I'd ask you to self-revert your removal of the tag so I can make the page move. Thanks! —TechnoSquirrel69 (sigh) 02:17, 26 November 2023 (UTC)[reply]

Sorry, misread the situation. I thought on initial glance that you were the draft's main author and thought it was just a new editor being a bit premature trying to delete the current redirect when draft was still in incubation. I see now that you are a well respected reviewer, and didn't realize this was a normal step in this process (had thought it was a one click multi process thing).

I've reverted myself, sorry about that. My main focus of the page had been the weird Multiline HTML table in list syntax error that was somehow created by having those two templates following after each other. Since the page will be replaced soon, I can live with that error existing for a little while. Zinnober9 (talk) 02:37, 26 November 2023 (UTC)[reply]

Happy New Year!

Zinnober9,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
Abishe (talk) 13:59, 1 January 2024 (UTC)[reply]

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Abishe (talk) 13:59, 1 January 2024 (UTC)[reply]

I appreciate it and hope to figure out how to avoid it in the future.

HansWobbe

@HansWobbe: You are welcome. The table errors you had were fostered content issues due to the missing closers </td></tr> and the few missing |. All opening tags in a <table> style table need a paired closing tag. And for the {| style of table, |- creates a new row for the table, but | creates a cell to allow that content to exist in that new row. All very easy things to drop or miss one. Cheers, Zinnober9 (talk) 00:33, 14 January 2024 (UTC)[reply]

Hi, regarding editing my sandbox, please do consult me before doing any changes as I do not like it being so messy and like to know what changes are done beforehand. Hope you understand my position on the matter. Suomi2023 (talk) 07:31, 18 February 2024 (UTC)[reply]

While I do respect your position, if I were to contact every user with syntax errors beforehand, the fixing of the 3 million remaining errors would be much slower and more difficult. Its been easier to edit first and ask for forgiveness later if an editor objects. Generally few editors interact when asked beforehand, and few editors interact after a correction, be it an objection, comment, or a thanks. While I thought my corrections were keeping your content more or less identical in display, and reduced some of the messiness in my eyes, the multiple unclosed bolding tags made a few placements a best guess and I'm sorry if any adjustments were not your intent. Sorry for the inconvenience, and if I come across any other pages of yours that have any syntax errors, I'll try to contact you first. Best wishes to you, Zinnober9 (talk) 13:56, 18 February 2024 (UTC)[reply]

Z – after a few editors expressed surprise or dismay at User-space edits, I changed my default User-space edit summary to "Fix Linter errors. I hope you don't mind this minor cleanup edit in your user space." It has worked very well, resulting in fewer complaints/reverts and numerous thank-yous. You might try it. – Jonesey95 (talk) 15:06, 18 February 2024 (UTC)[reply]

Jonesey95 — I don't get much interaction either way with my current edit summaries, though I certainly get more thank yous than questions/complaints/reverts.

While I have been stating in my summaries the Linter link and the type of error(s) that was the reason for the edit so far (ex "Fixed Lint errors on this page (table tag errors)"), I certainly see the benefit of adding a little something like yours. Will consider. Zinnober9 (talk) 18:34, 18 February 2024 (UTC)[reply]

I see. I thank you for responding nicely on the matter and thank you for clarifying with me. I totally appreciate the efforts involved. Suomi2023 (talk) 16:19, 18 February 2024 (UTC)[reply]

No problem, thanks for asking. Zinnober9 (talk) 18:35, 18 February 2024 (UTC)[reply]

Anyway, let me just inform you info on my sandbox is just for practice so do not have to worry if info is different from actual visa policy. Suomi2023 (talk) 01:47, 19 February 2024 (UTC)[reply]

Wasn't worried about that at all, and hardly noticed. Linter only permits us wikignomes to edit the syntax issues anyway, so wasn't focused on the content itself and was only focused on the wikimarkup syntax around it. Also, I've come across lots of various sandboxes with various purposes, and have used my own sandbox as a test place for hundreds of things, so well aware that sandboxes (and other user subpages) are a respected content space to test out stuff like basketball scoring tables for Oprah vs Mozart if you so wanted to.

Unless the content is clearly vandalism or egregiously WP:NOT content, I tend not to pay attention to the content that much. And if I did spot a content issue, then I'd certainly ask about it or mention it to you. Best wishes,

Zinnober9 (talk) 04:26, 19 February 2024 (UTC)[reply]

Hello,

I was going through the url=value drafts and saw that you had moved this one from mainspace. I get why - the translated page's citations aren't placed inline correctly. I'll try to fix that, but this is actually a duplicate posting. The article already exists in English, just not as detailed as this.

The other en page: Al-Nabi Yunus Mosque; the ar page that was translated: جامع النبي يونس It's in the language drop downs on that mainspace en page.

I don't know how to request a merge in draft space (I don't think I can) since @Loukus999 did all the work on the translation. How do I request this to be fixed so there isn't a duplicate article once the citation issue is rectified? OIM20 (talk) 14:27, 26 February 2024 (UTC)[reply]

ETA: link to draft: Draft:Prophet Yunus Mosque (Oops! Sorry, didn't realize I hadn't included it initially.) OIM20 (talk) 20:48, 26 February 2024 (UTC)[reply]

@OIM20: Drafts and article creation are not my Wikipedia area of focus, so I'm not the best person to ask. I had come across this page because of a tracked syntax error, then saw it had some critical reference issues, so I Draftified to allow for those to be fixed.

That said, doing a little digging, it looks like WP:PROPMERGE outlines this sort of situation and can be initiated by anyone. My assumption is that it's a type 2 merge given the page names are different, but I don't know for certain and recommend checking either on the Propmerge project's talk page, or at WP:HELPDESK to verify that Propmerge is the correct action to take.

Best wishes, Zinnober9 (talk) 03:12, 27 February 2024 (UTC)[reply]

Thank you! OIM20 (talk) 12:37, 27 February 2024 (UTC)[reply]

Dear Sir, Thanks for your edit to the table I made here - https://en.wikipedia.org/wiki/User_talk:MyNameIsAnthonyGonsalves I had realized immediately, that I had done some mistake. But could not tell what. I compared it with some tables made at other pages [studied their code], but could not discover what mistake I had done. Today, I suddenly found the table corrected by you. I again studied its code, but cannot discover what did you do make it good. In your edit, it says, as below: “Removed table breaking indents (fostered content error)” I cannot understand this. Can you please tell me? Thanks. Otherwise, I would never learn. Thanks. Regards MyNameIsAnthonyGonsalves (talk) 05:34, 4 March 2024 (UTC)[reply]

@MyNameIsAnthonyGonsalves: Sure, thanks for asking. You had each line within the table indented with : and doing so deactivates/breaks the wikitable markup, or pipe syntax. Tables should be treated, regardless of number of lines, as one unit, not to be altered or interrupted between the opening and closing brackets, unless it's a new cell or row led with a pipe | . Tables very rarely are indented, since most tables are wider than yours and typically are the width of the page, but on the rare occurrence you do want to, this is one of two ways I can think of to how you'd do it.

As for the fostered content error I made reference to, an example is explained and displayed here.

Best wishes, Zinnober9 (talk) 02:42, 5 March 2024 (UTC)[reply]

Thanks sir for the lucid explanation. I have made a note of it. Thanks again.

MyNameIsAnthonyGonsalves (talk) 09:55, 5 March 2024 (UTC)[reply]

Thank you very much for the following edit.

https://en.wikipedia.org/w/index.php?title=Talk:Lyme_disease&diff=prev&oldid=1211344028

In particular, you removed “|thumb|upright=1.35” from the pair of photos. That made all the difference, and the pair is now in the article itself. FriendlyRiverOtter (talk) 16:51, 4 March 2024 (UTC)[reply]

@FriendlyRiverOtter: You are very welcome. Yeah, Gallery (template or tags) isn't too fond of the individual sizing parameters typically found in Indivdual file syntax, and is something that is a regular trip hazzard. Happy to assist. Cheers, Zinnober9 (talk) 02:58, 5 March 2024 (UTC)[reply]

@Zinnober9: Thanks for that tidbit, too! I'll see you around the jungle. FriendlyRiverOtter (talk) 18:58, 5 March 2024 (UTC)[reply]

Hello Sir, We added few reliable sources link to this page to resolve citation issues. I request you to not delete it. Please kindly consider our request. Akhila257 (talk) 08:08, 23 March 2024 (UTC)[reply]

Sir could you please let us know which is copyright violation so we try to remove it? Akhila257 (talk) 14:59, 23 March 2024 (UTC)[reply]

Please let us know which line is copyright violation? Akhila257 (talk) 15:00, 23 March 2024 (UTC)[reply]

I haven't added anything from myDattatreya.com and Amritananda blogpost. Akhila257 (talk) 15:02, 23 March 2024 (UTC)[reply]

You made an edit to my user page without messaging me first and getting consent. Please explain why you think that was ok for you to do. Chrisbrl88 (talk) 04:37, 26 March 2024 (UTC)[reply]

Hello, @Chrisbrl88!

Hope you are doing well. The page WP:Lint gives me permission (with clear boundaries) to make corrections of specific tracked syntax errors on all pages of Wikipedia, and without needing prior permission for pages in userspace. The general summary of these rules are that I can't change the words of other editors (ie the displayed content) or change the page's layout/display (barring the exception that an error is breaking the page's visual layout).

Your page had a fostered content table error (missing a | for "housing" the cell content), and I swapped out the {{boxboxbottom}} tag for |} since it mismatched with the first table opening statement style.

I hope you have a wonderful Easter, Zinnober9 (talk) 00:37, 27 March 2024 (UTC)[reply]

While I DO appreciate the diligent work you do on database cleanup, common courtesy kinda warrants a, "Hey - there's X issue on your user page and I'm gonna take Y action to correct it; just a heads up that you're gonna get an email," message.

It kinda felt like someone moving my couch without asking if I was OK with it. That's all. I hope I didn't come across the wrong way!

And I hope you have a wonderful Easter, as well! Christmas and Easter are the only times my mom makes deviled eggs and her unique macaroni salad. It's a comfort for me 🤣

Chrisbrl88 (talk) 06:53, 27 March 2024 (UTC)[reply]

G'day! (I'm an Aussie, can you tell?)

Thanks for cleaning up some fostered lint on my user page! I've had some weird display probs there for ages, but have been too busy to track them down, so I appreciate your help.

You have an elegantly clean set of userboxen. I just might emulate your style ... if I ever find the time to clean up my user page! ;) yoyo (talk) 08:13, 31 March 2024 (UTC)[reply]

You're welcome! Table errors are pretty frequent an error, real easy to drop a tag.

Thanks! Feel free to copy the layout style. I wanted flexibility with the collapsing and the section headers, and the wikitable style wasn't giving me what I wanted. Zinnober9 (talk) 13:14, 1 April 2024 (UTC)[reply]

Hello! You recently adjusted my user page explaining that there were "lint errors" (which I am completely unfamiliar with). Perhaps there were, but I must undo your edit, as it threw off everything to where the side bar overlaps with everything else, obscuring it. My guess is that my retaintion of the former default desktop layout conflicts with the changes you made. I found the new default to be absolutely horrible, not in the least since it seemed to happen overnight, without sufficient warnings to all users who might protest it. I wouldn't have minded, but man, it was needlessly confusing, and also just looked really bad! But, beauty is in the eye of the beholder, and, after much searching I was able to change it back for my own use without this affecting anyone else.

So, just so you're aware, whatever the lint error changes you made were, they apparently don't have a universally uniform effect on all pages. Mine ended up appearing like one of those pages we sometimes happen upon that haven't been updated since 1999, with everything scrambled over everything else. I know no harm was meant, so please accept that, though it's somewhat irritating, I have no personal issue with you. Please let me know if there's a way to fix lint errors without it scrambling the page. But also know I am no longer up-to-date with all the current jargon as I was in, say, 2012, and will likely be easily confused. I still edit, but no where near at the rate I used to (I might've been making 100-300 edits per day at one point; now it's just a few times a month).

Peace. Hamamelis (talk) 01:11, 23 April 2024 (UTC)[reply]

Zinnober9, I worked on this broken user page for a while and abandoned my edits. I don't know if there is a way to preserve the rather unusual layout while fixing the Linter errors. I'm going to take another look. – Jonesey95 (talk) 04:09, 23 April 2024 (UTC)[reply]

Jonesey95,

Both of the sandbox edits that I came up with this evening (presented in my reply below) preserve it fairly well, (the main difference being the tables with broken syntax being the blue boarders, that appear when corrected), but otherwise keeps the same visual placement/layout of the rest of Hamamelis' content intact. Certainly not one of the more clear cut Wikitable errors I've fixed recently, but certainly one that has a potential for a satisfying, syntax-free solution for both parties. Zinnober9 (talk) 04:28, 23 April 2024 (UTC)[reply]

Thank you for your efforts! Hopefully all will be well now. (Explained in my response to Zinnobef9, below.)

Peace. Hamamelis (talk) 04:56, 23 April 2024 (UTC)[reply]

@Hamamelis No worries, thank you for the kind message. Some corrections aren't as straight forward and take some assumptions, as the way the code is written indicates one way, but displays in another way due to the issues present. I leaned more towards how the Wikitable code presented on yours and missed that the Inline cleanup tags table expanded so big.

Would something like this or (alternately this) satisfy you? Both of these have all the syntax errors corrected and look pretty similar to your current layout. If either does, edit that version's source code, copy in full, and paste into yours to keep it (or I can copy and paste it to yours). Zinnober9 (talk) 04:16, 23 April 2024 (UTC)[reply]

Hamamelis: I have fixed some of the syntax errors on your page, leaving at least two bits of invalid table formatting. One way you can tell that the table formatting is invalid is the two horizontal blue lines to the right of the loon image. Another way is that the userboxes do not form a normal vertical stack. Maybe you could experiment with the formatting to get things to look the way you want them while also providing valid table formatting. The main problem is that you have tables that do not use a pipe (|) character to introduce cells; they just go from the table opening to content. – Jonesey95 (talk) 04:25, 23 April 2024 (UTC)[reply]

Thanks! The alternative version you showed has the identical overlapping problem I wrote to you about originally. However, the first example appears to be perfect! I know from interractions even a long while back that knowing how something looks on one person's screen doesn't tell much about how it looks on other people's.

I think I can do the cut and paste of it as you've described. Thanks again, for your caring and understanding, as well as your efforts. If I may, I'll let you know if I have any questions or difficulties.

Peace. Hamamelis (talk) 04:53, 23 April 2024 (UTC)[reply]

Hi once more! Just checked and wanted to report that your last edit to my user page corrected everything just fine. No need for me to cut and past. So... success!

Thanks!

Peace. Hamamelis (talk) 05:02, 23 April 2024 (UTC)[reply]

That was Jonesey95's edit, and they didn't address the two table errors. Since you liked the first option, I've gone ahead and fixed that part.

Best, Zinnober9 (talk) 10:38, 23 April 2024 (UTC)[reply]