Meta:Requests for translation adminship/Thereza Mengs (WMDE)

The following discussion is preserved as an archive of a closed Meta-Wiki request. Please do not modify it.

Thereza Mengs (WMDE) edit

As a part of the Software Development Team at Wikimedia Deutschland, I work within the Technical Wishes Project and will support Johanna Strodt (WMDE) in creating and editing project pages on meta. I would like to be able to mark these pages for translation and hereby request the translation adminship. I already did the tutorial and set up the first project page. Thank you and best wishes -- Thereza Mengs (WMDE) 11:54, 13 November 2023 (UTC)[reply]

Working Waiting About the sample page you provide, considering Meta:Internationalization guidelines:
  • Please use the 2021 tvar syntax (<tvar name="id"></tvar>) rather than the older one (<tvar|id></>).
  • Please use digits for tvar names for internal link targets.
  • You should also wrap your username in a tvar, since it should not be translated; copying it would be a bit painful for translators.
Also, I would be grateful to you for preparing another larger page for translation (with headings, list, or image…). 🙂 -- Pols12 (talk) 22:55, 14 November 2023 (UTC)[reply]
Thank you for the helpful information. I updated the project page and created a test page with more translation. I am looking forward to your feedback. Best wishes -- Thereza Mengs (WMDE) (talk) 13:11, 5 December 2023 (UTC)[reply]
Thank you for the edits.
  • Rather than putting a whole image syntax in a tvar, it is cleaner to fully exclude it from translation closing the translate tag before the image and reopening it before the next translatable content.
  • Closing a translate tag before opening a new one for the next section is totally useless.
  • Tvar names must be unique inside the same unit, not inside the whole page. So we can (actually we should) reuse the same names in each paragraph. From Translate interface, it is much easier to use shortcuts if the first tvar of the unit has the name “1”, rather than 5 (for example).
  • For floating content, we should replace right with {{dirend}} which means “right” in LTR languages, and “left” in RTL languages.
  • I’m not sure why you added a language annotation in the translatable content. If you need it for MassMessage (but I don’t think it is useful), you should exclude it from translatable unit and rather use {{PAGELANGUAGE}}. By the way, for MassMessage, you probably need an other section tag specific for the message heading.
-- Pols12 (talk) 19:56, 5 December 2023 (UTC)[reply]
@Pols12 I am very sorry for this late response, thank you again for all the information. I am wondering what you may need me to provide in order to get the translation rights? I would need them for creating project pages on meta. We at the Technical Wishes Team at WMDE send out messages to villagepumps to inform about new features or changes etc. therefore it is very helpful to have as many translations as possible, so that we can reach out to the people in their own language. I would really appreciate your answer and help. Best wishes and a happy new year. -- Thereza Mengs (WMDE) (talk) 08:56, 3 January 2024 (UTC)[reply]
I actually think you can work without this right: you can prepare pages for translation and request a translation admin to mark them. I understand this is not an ideal solution, especially for staff with sometimes short deadlines, but most requests at Meta talk:Babylon are usually handled in 24 hours. I will be happy to support your TAdminship once you have successfully prepared some pages without segmentation issue.
However I am not a Bureaucrat, my opinion is not decisive, and I don’t veto your granting. -- Pols12 (talk) 14:31, 3 January 2024 (UTC)[reply]
Thank you very much for your comments. Let's leave it as you describe for now, if it doesn't work well in the long term, I'll make a new request. Thereza Mengs (WMDE) (talk) 09:21, 16 January 2024 (UTC)[reply]

Done. --Sotiale (talk) 09:16, 17 January 2024 (UTC)[reply]