WOSlinker

Series of image renames

Hi, I noticed that you submitted 20 images or so for rename. This will require about one hour of work to execute while we have a backlog of close to 700 images. So it might take some time before they are renamed. You might be interested in reading User_talk:Foroa#Renaming_maps to learn about other ways of achieving your objectives in a faster and more efficient way. Best regards. --Foroa (talk) 09:50, 14 July 2010 (UTC)

Thanks. I wasn't aware that redirects worked. I've read on and will do the rest later on today. Perhaps the documentation at Commons:File renaming should be updated to mention that it's easier to add redirects that request renames for aim #6. -- WOSlinker (talk) 11:28, 14 July 2010 (UTC)

Agree, but it is very recent and has not been implemented on a larger scale and in various conditions. I prefer to have several working implementations before trying to get rules changed. --Foroa (talk) 12:06, 14 July 2010 (UTC)

Do these still need to be renamed or are things now settled? If they are settled, can the rename tags be removed?  — billinghurst sDrewth 04:24, 21 July 2010 (UTC)

Renaming in no longer needed. I'll remove the tags. -- WOSlinker (talk) 21:34, 24 July 2010 (UTC)

TUSC token 4828b3464ce1f25ea9b654cb24e63850

I am now proud owner of a TUSC account! -- WOSlinker (talk) 12:49, 5 September 2010 (UTC)

Thanks...

... for the Rare species location template. Lycaon (talk) 16:19, 15 September 2010 (UTC)

Google Code-In 2019 is coming - please mentor some documentation tasks!

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 22:05, 23 November 2019 (UTC)

Italics

Hi. I undid this edit because the italics were not broken.   — 🇺🇦Jeff G. ツ _{please ping or talk to me}🇺🇦 11:11, 27 October 2022 (UTC)

Jeff G., there is something broken on that template as there is a missing italics. See the lint error list. So if you think my edit didn't fix it properly, could you suggest an edit that would fix it? -- WOSlinker (talk) 12:19, 27 October 2022 (UTC)

Linter fixes

I see that we are both working on fixing a bunch of Linter errors in templates. I have scrubbed through many of the template categories, but I haven't done much work in Missing End Tag or Obsolete HTML yet. You are likely to find many templates in those lists with 1000+ transclusions.

You might find this sort of page useful. I created it by copy/pasting from the Linter report, then using some find and replace patterns to make the list. It's an easy way to click through a bunch of transclusion counts to see which pages will reduce the Linter count by the most.

There are also User subpages that have many transclusions. I find it easiest to find those by paging through the Linter error lists in File space, 500 at a time, and looking for common transcluded pages in the right column of the table. Have fun! Jonesey95 (talk) 13:09, 29 October 2022 (UTC)

Greetings

.....thank you very much for your great work here. Best greetings. Orchi (talk) 16:30, 6 February 2023 (UTC)

br tag

Hey, firstly thank you for all your hard work here! I appreciate it. I was thinking that the paragraph tag is more appropriate in my descriptions because they literally denote a new paragraph. I’m not just breaking the line. Does this make sense? - Chris.sherlock2 (talk) 13:24, 10 June 2023 (UTC)

Paragraph tags are fine but should be used slightly differently to br tags. You have to do <p>Paragraph 1</p><p>Paragraph 2</p> rather than Paragraph 1<br>Paragraph 2 in those cases. -- WOSlinker (talk) 15:08, 11 June 2023 (UTC)

Thanks! I’ve done this now. - Chris.sherlock2 (talk) 21:24, 15 June 2023 (UTC)