Jump to content

User talk:RAdimer-WMF

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 1 month ago by RAdimer-WMF in topic Special:Diff/29903418

Well played

[edit]

MPourzaki (WMF) (talk) 20:02, 31 March 2023 (UTC)Reply

Clarification

[edit]

Hi, as I am translating the APP, I was wondering if this sentence was correct; I expect that one 2023-2024 should actually be 2024-2025. Regards, XanonymusX (talk) 15:03, 14 April 2024 (UTC)Reply

Hi XanonymusX! Thanks for asking about this. I've asked internally and will make the change to the source page when I find out. Best regards, RAdimer-WMF (talk) 15:37, 14 April 2024 (UTC)Reply
XanonymusX, yep, the first one was intended to be 2024-2025. I've made the edit and marked the page for translation. RAdimer-WMF (talk) 14:42, 16 April 2024 (UTC)Reply
Hi, another remark regarding the APP (finally completed the German translation): there seems to be a mistake in the navigation menu of Wikimedia Foundation Annual Plan/2024-2025/Goals/Effectiveness. I fixed it for the original version, but all the translations still show the wrong navigation item (2 instead of 4). Maybe you can check, I guess only translations admins can fix this. Regards, XanonymusX (talk) 15:43, 18 April 2024 (UTC)Reply
XanonymusX, eep, thanks for catching that. I've marked the page for translation, fortunately it doesn't affect translations. RAdimer-WMF (talk) 16:14, 18 April 2024 (UTC)Reply
Great! :) XanonymusX (talk) 16:53, 18 April 2024 (UTC)Reply

Interest of templates

[edit]

Dear RAdimer,

I saw you edited {{Human Rights Team/header}}, then edited all pages which transclude it.

If you ever use {{my template}} as Hello {{my_template}} Thank, you should probably include “Hello” and “Thank” words into my_template content: this is much quicker to edit, and this minifies page wikitext.

In your case, rather than wrapping each use of HRT/header into WMF_Menu_2Row, you should instead wrap it only once directly inside HRT/header template. That’s the purpose and the interest of templates.

By the way, please also note template parameter names for translatable values must be explicit:
we have to use {{my template|1=<translate>Hello</translate>}}
instead of {{my template|<translate>Hello</translate>}}.

-- Pols12 (talk) 21:07, 26 June 2024 (UTC)Reply

Hi Pols12! Though every current use of {{Human Rights Team/header}} is inside {{WMF Menu 2Row}}, at least for now I'm going to keep it as-is. In our current setup, it's easier to have the transcluded page simply be the list of links.
Re: explicit template parameter names, which template are you referring to? The {{WMF Menu 2Row}} calls all use named parameters. Best regards, RAdimer-WMF (talk) 21:55, 26 June 2024 (UTC)Reply
Thank you for your answer. 🙂 For second issue, I spoke about Wikimedia Foundation/Legal/Community Resilience and Sustainability/Human Rights/Impact of the war in Gaza and Israel where you added {{WMF Heading1|<translate><!--T:1--> Impact of the crisis in Gaza and Israel</translate>}}. I have fixed it. -- Pols12 (talk) 22:15, 26 June 2024 (UTC)Reply
Ohhhhhh. Ok, thanks for fixing it :) RAdimer-WMF (talk) 22:23, 26 June 2024 (UTC)Reply

Wikimedia Foundation Bulletin June Issue 2 Special:LintErrors

[edit]

Hallo RAdimer, you have delivered this message, it contains some lintErrors for example Special:LintErrors/misnested-tag because the small-tag should not be spanned over lists. Also there is a missin taf bold ''' Special:LintErrors/missing-end-tag please do not deliver masseges with such errors. They all have to be fixed, like this de:Spezial:Diff/246410212 Lómelinde (talk) 04:36, 3 July 2024 (UTC)Reply

Lómelinde, thanks for the message. I've fixed it in the main issue page and will have time to go around and fix the others early next week, hopefully Monday. RAdimer-WMF (talk) 13:33, 3 July 2024 (UTC)Reply
Also noting that, in the future, I'm going to check issues for lint errors prior to sending them out. RAdimer-WMF (talk) 13:42, 3 July 2024 (UTC)Reply
Ok, I think we got all of the lint errors and duplicates (with the help of Quiddity and Trizek :D). RAdimer-WMF (talk) 16:52, 3 July 2024 (UTC)Reply
Thank you --Lómelinde (talk) 04:12, 4 July 2024 (UTC)Reply

Bulletin with translation tags

[edit]

Not sure what happened here ? I got the bulletin a second time, but now with translation tags in it. —TheDJ (talkcontribs) 09:52, 3 July 2024 (UTC)Reply

TheDJ, that's very odd. This is my first time using MassMessage so I'm not sure what the cause is. Quiddity, any thoughts?
Some observations:
  • There's only one log for my sending the message to the subscribers list, and the second message you received was sent 8 hours after the initial send.
  • Clicking around the subscribers list, every recipient on Meta-Wiki received only the first message, and every recipient on other projects received both. Maybe it's a job queue/repeated work issue?
RAdimer-WMF (talk) 13:42, 3 July 2024 (UTC)Reply
Made a phab ticket. RAdimer-WMF (talk) 14:33, 3 July 2024 (UTC)Reply

FYI – Double send of the new Bulletin?

[edit]

Hey! As per the logs, I can see that you only wanted to send one message, but somehow I received it twice en:User_talk:Nadzik? Just letting you know. Cheers! Nadzik (talk) 13:29, 16 August 2024 (UTC)Reply

Thanks for the message Nadzik. I've added a note in phab:T369179 and removed all duplicates, save for zhwiki (where I hit a filter) and frwiki (where Salebot reverted it). RAdimer-WMF (talk) 14:56, 16 August 2024 (UTC)Reply

New Board of Trustees page

[edit]

Hey Rae, I really liked your and ELappen's new BoT page redesign :) However, some strings that are being duplicated by {{tunit}}s do not work on gendered languages. Apart from tunits 129 and 150, could you make them separate translation strings? I'm asking you because I'm not a translation admin, so while I'm able to remove the tunits, I cannot create <translate> tags. Eduardogobi (talk) 05:21, 9 May 2025 (UTC)Reply

Hello @Eduardogobi! Thanks for your edits, and for raising this point. I've now made each their own translation unit. Best, RAdimer-WMF (talk) 20:59, 12 May 2025 (UTC)Reply

Capacity Exchange: New Design, Features & Ways to Connect!

[edit]

Hello RAdimer-WMF!

Our platform has undergone several updates and has a new design and brand-new features available. We would like to invite you to explore the tool and give your feedback to help us make it even better.

Also, call your wiki-friends to Join for the Exchange.

If you experience any difficulty navigating the tool, here is our User Guide with a step-by-step tutorial on how to use each feature.

To interact with the CapX team, share your feedback, or offer a suggestion, you can use the Bug Reports feature in the tool or email capx(_AT_)wmnobrasil.org.

For quick questions and suggestions, we've set up a Telegram channel. We also invite you to add the {{CapacityExchange}} template and the {{CapXsupporter}} userbox to your user page to express your support.

Finally, we created a newsletter channel for those interested in receiving regular updates about the tool and the Capacity Exchange project - click here to subscribe.

See you exchanging around!

You are receiving this message because you have registered on Capacity Exchange.

Sincerely,
AJurno (WMB)
MediaWiki message delivery (talk)
13:02, 19 August 2025 (UTC)Reply

Join us for “Many Tongues, One Movement: Voices Across Languages”!

[edit]

Hello RAdimer-WMF,

We’re excited to invite you to an inspiring global virtual gathering: the first Capacity Exchange Translat-a-thon.

Together with Language Diversity Hub, the Capacity Exchange (CapX) team will host its first Translation Marathon dedicated to ensuring linguistic equity in access to this amazing tool aimed to connect Wikimedians.
If you enjoy contributing to Wikimedia projects through translating and adapting content into different languages, this event is for you! Join us in the celebration of the multilingual spirit of the Wikimedia Movement at an event where communities that contribute in diverse languages will be able to share local knowledge and collaborate across borders.
Many Tongues, One Movement: Voices Across Languages

  • Date: December 6, 2025
  • Time: 12 PM (UTC) - Check the event page for your local timezone
  • Location: Online (Meta-Wiki + live session links)

If you can’t join the live event, you can still contribute to the translations! Edits will be counted for two weeks, until December 20th. And everyone who participates will receive a special badge to display on their CapX profiles.

Strengthen your collaboration through CapX

[edit]

We invite you and your community to join the Capacity Exchange (CapX), a Wikimedia community-built platform for connecting, collaborating, and exchanging skills with peers across the movement.

CapX helps Wikimedians and organizations find each other, share expertise, and build stronger, more connected communities.

Whether you’re an individual contributor, a user group, a community initiative or an affiliate, CapX helps you grow through knowledge exchange.

More information

[edit]

→ Explore the CapX platform: capx.toolforge.org
→ Read: User Guide & FAQ
→ Watch: Meet the Capacity Exchange video
→ Join our Telegram community chat: CapX Telegram Group

If your community, usergroup or affiliate would like to have a CapX organization profile, please reach out at capx@wmnobrasil.org, and we’d be delighted to support you.

With warm regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange ProjectWikimedia Brasil

MediaWiki message delivery (talk) 14:55, 13 November 2025 (UTC)Reply

~2025-37439-13 (talk) 02:41, 2 December 2025 (UTC)Reply

Special:Diff/29903418

[edit]

Good day. Your edit here broke pages that transclude the template as {{tunit}} has a default parameter that uses the translation unit it is transcluded at instead of what is used at the template itself. i.e. {{tunit|11|Birthday card}} is using translation unit 11 of Wikipedia 25 when transcluded there. --Min☠︎rax«¦talk¦» 02:22, 17 January 2026 (UTC)Reply

@Minorax: Eeep, thanks for letting me know (and for fixing it), I misremembered the parsing order. RAdimer-WMF (talk) 20:39, 17 January 2026 (UTC)Reply