|
Hi there. I know it's not your intention, but when you're putting <sup>2</sup> inside conversion templates you're actually breaking the templates. It doesn't recognise that as a valid conversion unit and the convertor no longer works. Please stop trying to change 1234 square kilometers (or miles) into a sup number with the conversion template. Also your edit summary is incorrect as you're not correcting typos. Converting "square kilometers" or miles to a sup is a preference, not a typo change. Additionally when you make an edit you should Preview it before saving it in order to check you haven't broken anything. Can you please go back through your recent edits and correct those broken templates. Thanks. Canterbury Tail talk 01:08, 1 April 2024 (UTC)[reply]
- Apologies; I didn't think to make an exception for the conversion template. I'll fix the edits I've made and avoid making the same mistake in the future. CoolieCoolster (talk) 01:51, 1 April 2024 (UTC)[reply]
- Thank you. Canterbury Tail talk 12:04, 1 April 2024 (UTC)[reply]
I've noticed that you have been changing "cm³" to "cm3". This is good and in line with the MOS. But an even better change would to to "cc". This avoids superscripts altogether, making it easier to read for sighted readers, readers with sight issues and those who use screen readers. It also aligns better with the {{convert}} and {{cvt}} conversion templates and general practice recommended by WP:CARUNITS (acknowledging that many articles still do not follow recommended practice). Stepho talk 00:59, 4 April 2024 (UTC)[reply]
- While the covert templates work well, especially in cleaning up an article's wikitext of excessive numbers, they unfortunately seem to use cu for cubic for US customary volume units and 3 for cubic for metric volume units, creating an unnecessary inconsistency. I'll focus on solving other formatting errors for now, but aside from c3 likely being more readily understood than cc, its use results in inconsistency when used alongside other metric volume units, as cubic meters have to m3 to avoid the confusion of cm. CoolieCoolster (talk) 02:03, 4 April 2024 (UTC)[reply]
- 100 cubic metres (3,500 cu ft)
- 100 m3 (3,500 cu ft)
- 100 cubic centimetres (6.1 in3)
- 100 cm3 (6.1 in3)
- 100 cubic centimetres (6.1 cu in)
- 100 cc (6.1 cu in)
- Ah, I think I see what's happening. Using the templates with
|m3= , |cm3= or |in3= will indeed display superscripts. But WP:CARUNITS recommends using |L= , |cc= and |cuin= for engine capacity. And of course I am only recommending this for car articles. Either way, I appreciate your work. Stepho talk 02:26, 4 April 2024 (UTC)[reply]
|
|
The Minor Barnstar
|
| This barnstar is awarded to CoolieCoolster for copy edits totaling between 1 and 3,999 words (including bonus and rollover words) during the GOCE March 2024 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 08:46, 4 April 2024 (UTC)[reply]
|
 Suggestion - Regarding your edit to 10TP, might I suggest you use the preview button before you save your edits in the future; this helps you find any errors you have made, like in this edit to 10TP, which left the infobox looking like this. Don't worry, I've fixed it.
It is strongly recommended that you use Show preview before saving. Thanks. Isaidnoway (talk) 13:56, 7 April 2024 (UTC)[reply]
Hello and thank you for tidying up our articles. Please bear in mind that, per WP:COSMETICBOT, some editors may take exception to large numbers of edits like this one which do not affect the displayed text, even if done manually. Thanks again, Certes (talk) 21:33, 11 April 2024 (UTC)[reply]
- (edit conflict)Hello friend. Please be careful of WP:COSMETICBOT. Your edits popped up on my watchlist a couple times today. In general, it may not be a good idea to use automated tools to mass add/delete one invisible space, due to the watchlist spam. Hope that makes sense. –Novem Linguae (talk) 21:35, 11 April 2024 (UTC)[reply]
- I concur with the others. It's best to bypass cleanups that involve only the removal of extra spaces or other very cosmetic changes on their own. Think of the situation where many are doing such edits and how they could clutter editors' watchlists, thus disrupting their ongoing work. Thanks for your consideration. Stefen Towers among the rest! Gab • Gruntwerk 00:32, 12 April 2024 (UTC)[reply]
- Didn't realize there was an AWB watchlist; I'll make sure to integrate such edits into more significant edit runs rather than dedicate an edit run to just spacing fixes from now on. CoolieCoolster (talk) 02:07, 12 April 2024 (UTC)[reply]
This edit to the article for Short Hills, New Jersey, seems to do nothing more than remove extra spaces after a period for circumstances that are already handled when a page is rendered. Was there any purpose to this edit beyond removing spaces? Am I missing something? Alansohn (talk) 22:05, 14 April 2024 (UTC)[reply]
- Apologies; my main goal was to replace the article's Unicode superscripts with sup tag superscripts, which was unfortunately missed by the automatic typo filter. Having manually removed the superscripts from the article now, I've also made adjustments to my secondary replacement filters to ensure that no article with faulty superscripts should be missed from now on. CoolieCoolster (talk) 22:13, 14 April 2024 (UTC)[reply]
Hi. Just to make sure, is changing
to
something JWB generally does, or is this a personal addition by you? The reason I'm asking is that since |} is supposed to be at the start of a line, this change is causing linter errors like this:
| Rainbow Warrior (2011) |
missing-end-tag |
div |
Output not from a single template
|
| Rainbow Warrior (2011) |
deletable-table-tag |
table |
Output not from a single template
|
| Rainbow Warrior (2011) |
stripped-tag |
div |
Output not from a single template
|
and it would be wild if a bunch of well-meaning people went around making this change, followed by other well-meaning people changing it back. 🙂
Gamapamani (talk) 09:07, 16 April 2024 (UTC)[reply]
- Sorry, made that change myself, didn't realize it was an error. Won't do that again. CoolieCoolster (talk) 11:17, 16 April 2024 (UTC)[reply]
- No problem, I was just worried this was going to start happening all over, since an automated tool was baing used. Gamapamani (talk) 11:24, 16 April 2024 (UTC)[reply]
Hello. It's good to find things to clean up, but I'm guessing you're not aware of WP:NOTBROKEN, which tells us that It is almost never helpful to replace [[redirect]] with [[target|redirect]]. My watchlist is full of Juventus F.C. → Juventus FC "fixes" which, apart from the very few if any where Juventus F.C. actually appears in the visible text, were actually unnecessary changes that we shouldn't be making. cheers, Struway2 (talk) 07:58, 22 April 2024 (UTC)[reply]
- I'll limit further ones to ones where Juventus F.C. appears in the text. -CoolieCoolster (talk) 08:00, 22 April 2024 (UTC)[reply]
- Thank you. My watchlist is also full of the changes Struway2 brought up. Robby.is.on (talk) 09:23, 22 April 2024 (UTC)[reply]
See Category:Articles with missing files. Cheers, Dawnseeker2000 17:33, 23 April 2024 (UTC)[reply]
- Apologies; I had set the replacement rules to avoid common file formats, but I've now added additional ones. -CoolieCoolster (talk) 23:04, 23 April 2024 (UTC)[reply]
- Thanks for that. Any issues didn't persist for long because there's a small, but dedicated group of editors that watch that category. Almost as soon as I posted the message here, I noticed that it had pretty much been cleared up. Dawnseeker2000 23:29, 23 April 2024 (UTC)[reply]
The edit you made to Mercury (element) inserted a non-breaking space into the middle of a DOI identifier which broke the link to a reference. I fixed it, but I'm worried this might be happening on other pages too. Reconrabbit 18:19, 23 April 2024 (UTC)[reply]
- Sorry for the mistake; I had set my script to avoid replacing replacing test in the, url, title, and archive-url fields but hadn't taken the doi field into account. I've added it to the script and I'll check for other citation fields that should also be included. I also did a search for doi fields with nbsp tags added to them and didn't find any, so the ones you fixed should be the only ones the error occurred on. -CoolieCoolster (talk) 02:15, 24 April 2024 (UTC)[reply]
- Good to know. Thanks very much. Reconrabbit 11:22, 24 April 2024 (UTC)[reply]
I noticed that you changed some instances of "KB" to "kB", etc. According to the Wikipedia Manual of Style, the capital letter should be used. See Wikipedia:Manual_of_Style/Dates_and_numbers. Bubba73 You talkin' to me? 05:52, 27 April 2024 (UTC)[reply]
- Apologies; I'll fix my mistake. -CoolieCoolster (talk) 05:53, 27 April 2024 (UTC)[reply]
- The subsection "Binary prefixes for bytes and bits" Bubba73 You talkin' to me? 05:54, 27 April 2024 (UTC)[reply]
Wikipedia:Manual of Style/Dates and numbers#Binary prefixes for bytes and bits Bubba73 You talkin' to me? 05:56, 27 April 2024 (UTC)[reply]
- Finished fixing them; I'll avoid making the same mistake again. -CoolieCoolster (talk) 06:50, 27 April 2024 (UTC)[reply]
|
