User talk:Waddie96

When making significant changes to the wording of warning templates, please seek community consensus. It appears that you are making changes based on personal judgment. Shirayuki (talk) 12:28, 27 September 2024 (UTC) Reply

It’s copyediting, and does not change the interpretation of the content but rather the ease of reading for the reader. What significant changes to wording are you referring to particularly? Waddie96 (talk) 13:20, 27 September 2024 (UTC) Reply

From the perspective of a translation administrator, generally speaking, commonly used templates are translated into many other languages, and changes or reverts to the wording will undoubtedly affect the workload of translators, so changes should be made cautiously.

Significant changes include Template:ObsoleteExtension, where your change from "You are advised against using this extension on a live site." to "It should not be used with current versions of MediaWiki." has increased the strength of the warning. Shirayuki (talk) 14:05, 27 September 2024 (UTC) Reply

Understood. Waddie96 (talk) 17:47, 27 September 2024 (UTC) Reply

I’m open to hearing and explanation of your point of view, as I would not want to be bold and not consider my community and I am open to learning. I thought consensus would not be required if grammatical corrections and copyediting are done, as long as the final message conveyed remains the same or becomes clearer—the latter being my goal. Waddie96 (talk) 13:24, 27 September 2024 (UTC) Reply

Ping @Shirayuki In case you’re not subscribed/following convo Waddie96 (talk) 13:25, 27 September 2024 (UTC) Reply

About these edits, please do not remove translation unit markers. This ensures that translators can effectively utilize existing translations when making updates. Shirayuki (talk) 14:46, 5 January 2025 (UTC) Reply

Oh, my understanding was when you changed the text/updated it you had to remove the T1 or T2 etc marker so the software knew the text needed to be re-translated? See Help:Extension:Translate/Page translation administration#Changing the source text: If you do minor changes to an existing translation unit, keep the marker. If you change a whole paragraph, delete the marker. So I made changes to entire paragraphs hence I removed the unit markers.

As a side, it also states Before marking the new version of the page for translation, and I've always wondered after making changes does the software automatically mark the page for translation or must I do it myself? And if the latter, how do I do that? Waddie96 (talk) 14:58, 5 January 2025 (UTC) Reply

My interpretation of the following from Help:Extension:Translate/Page translation administration#Changing the source text:

Changing unit text. Changing is the most common operation for translation units. You can fix spelling mistakes, correct grammar or do other changes to the unit. When re-marking the page for translation, you will see the difference in the unit text. The same difference is also shown to translators when they update their translations. For simple spelling fixes and other cases where you don't want the existing translations to be highlighted on the translated pages, you can avoid invalidating them: translators will still see the difference if they ever update the translation for any reason.

Is:

• small changes that keep unit markers will result in invalidating them, i.e. the unit won't be re-marked for translation
• large changes that mean you remove the unit markers, re-marks the page for translation.

Is this interpretation correct? Waddie96 (talk) 15:04, 5 January 2025 (UTC) Reply

Your edits include some changes that modify entire paragraphs; however, they retain the structure of the original translation units, allowing for the possibility of reusing existing translations.

Leaving markers:

• Highlights changes to translation units in the translation administrator's interface, even for minor edits.
• Enables translation administrators to compare changes and decide whether to invalidate existing translations.

Removing markers:

• Treats modified units as entirely new, making it harder to compare changes in the translation administrator's interface.

Shirayuki (talk) 22:06, 5 January 2025 (UTC) Reply

Perfectly understood. Thanks for the explanation. I’ve updated the guideline (Help:Extension:Translate/Page translation administration#Changing the source text) to reflect this, see my changes here. Do you mind checking them to see if they explain clearly the concept and they are correct? Thanks in advance @ Shirayuki. Waddie96 (talk) 05:08, 6 January 2025 (UTC) Reply

Greetings,

Can you clarify your intention with adding clear there? That seems to break the top of the page no matter my viewport’s width (at least using Firefox 140). Chealer (talk) 02:58, 7 July 2025 (UTC) Reply

@Chealer Hey, ah damn. On my side {{Extension-Translate }} and the {{ambox}} overlap. So {{clear}} fixes that on macOS Safari Version 18.5, and on macOS Google Chrome Version 138.0.7204.49. The issue was there on both before whereby {{ambox}} doesn't cut itself off and wrap. But possibly it's because {{Extension-Translate}} floats? Lemme try fiddle and check. Waddie96 (talk) 10:52, 7 July 2025 (UTC) Reply

@Chealer Corrected now! Issue was with {{TOCright}}. Waddie96 (talk) 11:37, 7 July 2025 (UTC) Reply

Thank you, I see your change’s effect, but am not sure that’s much better, since the ToC displays below the "Documentation for Extension:Translate" box, which pushes it so down that it's almost completely out of my (huge) monitor when the viewport is at the top, at default zoom level. I consider the ToC more important than that box, so I consider the way it displayed in previous versions better (although still far from ideal). Chealer (talk) 16:19, 29 July 2025 (UTC) Reply

I noticed this warning text is duplicated across multiple pages. Please create a single translatable template for it, so it can be maintained and translated in one place.-- Shirayuki (talk) 06:26, 10 August 2025 (UTC) Reply

Ok Waddie96 (talk) 06:43, 10 August 2025 (UTC) Reply

@Shirayuki Just don't know how to get rid of < tranlsate> tags in Template:Security warning feature. Waddie96 (talk) 06:57, 10 August 2025 (UTC) Reply

When a translation admin marks the template for translation with the translation-aware transclusion option (default: true) enabled, the ‎<translate> tags will no longer be exposed when the template is transcluded.-- Shirayuki (talk) 07:15, 10 August 2025 (UTC) Reply

Cool thanks Waddie96 (talk) 07:17, 10 August 2025 (UTC) Reply

Which editor a user uses varies from person to person. Please avoid making the source more complicated by changing it to your own style. Shirayuki (talk) 02:10, 14 August 2025 (UTC) Reply

Oh. I thought everyone seems the same syntax highlighting in VE and source editor 2010 and 2017. Cause I do? @Shirayuki Waddie96 (talk) 02:57, 14 August 2025 (UTC) Reply

Regarding the Template:Deprecated OOUI feature you edited, it isn’t a redirect—what were you trying to do? Shirayuki (talk) 12:00, 14 August 2025 (UTC) Reply

wanted to just transclude it. but if you want r/d it's done Waddie96 (talk) 13:52, 14 August 2025 (UTC) Reply

wanted to just transclude it. but if you want r/d it's done Waddie96 (talk) 13:52, 14 August 2025 (UTC) Reply

Regarding Template:Extension code in wiki:

• Please do not remove the translation unit markers (<!--T:N-->) if the translation units are still similar to the original. Removing them prevents reusing previous translations.
• Please refrain from merging multiple translation units into one. Doing so removes previous translations from the translation interface and makes them impossible to reuse.

Shirayuki (talk) 22:02, 19 August 2025 (UTC) Reply

Ok so if I leave them, then it will only change the meaning in English, and all already-translated languages will remain like they were? And only new translations of new languages will ever translate that new meaning?

So what if, I want it to be translated? I actually know this because Help:Extension:Translate/Page translation administration was so messy I copyedited it like twice. Also added some of the oddly specific stupid syntax things it demands.

For point two, I have NO idea what this 'translation interface' looks like or how it works. It might be best to add more information regarding this including screenshots so the editor who is not a translation administrator could have some idea of what it looks like and how it functions so we could best reduce your admin load when having to review changes.

I've been editing translation pages for ages, and I still get it wrong. Despite our translation extension being SO buggy and finicky, it's also got very poor help pages, or actually detailed because it's so demanding. But mostly it's just so specific about the syntax it requires that honestly it's prohibitive for the typical editor. Like silly things like how it gives you an unhelpful error message if you don't leave a space between a translation unit and the text; like oddly specific yet the error message produced is so non-specific and unhelpful! Translation unit markers in unexpected position. is unhelpful.

Whether the benefit for the non-English reader outweighs the frustration to the average editor is debatable. Anyway, rant over. Waddie96 (talk) 22:14, 19 August 2025 (UTC) Reply

@Waddie96: When the content of a translation unit is changed, translation administrators can choose whether to invalidate the corresponding translations. If a translation is invalidated, it will be marked as fuzzy. (On translation pages, it will be shown with a pink background.)

In the translation interface, the previous English text, the updated English text, and the existing translation are all displayed, allowing translators to compare the changes and reflect them accurately in the translation. Shirayuki (talk) 11:01, 20 August 2025 (UTC) Reply

It would be great if you could add this to the translation extension help documentation: Help:Extension:Translate/Page translation administration for clarity, and probably in simpler terms in the simple tutorial so it helps people edit translations correctly. That is a central feature of pages that are translated. It should be intuitive and user-friendly. But it's not, so a good reference page would be helpful.

Please consider adding this to both beginner and advanced help pages. I would but I do not have access to this interface. @Shirayuki Waddie96 (talk) 12:12, 20 August 2025 (UTC) Reply

@Shirayuki Is it this on Help:Extension:Translate/Page translation administration?

Invalidation. If changes are made to the translatable page source, the translation administrator will be given the option to "Require updates to the translation" for each section. If a section is invalidated, then the translated languages will get a pink background color for those sections, and a clock icon will be shown to translators in the translation interface. If a section is not invalidated, then no changes will be visible to readers of the translated pages, and translators will have to examine the section within the translation interface in order to see the changes.

If you could edit that section to clarify the fact that invalidating the translation FORCES the admin. to have the TU remarked for translation, whereas leaving the TU in place gives the admin the OPTION to choose to keep the current translation or invalidate it. If I'm correct in my understanding?

Make it clear what invalidates a TU: Removing the TU comment only? What else? And how to keep a TU, keep the TU immediately after the translate tag and only edit the source wikitext. Because obviously my main goal is to of course not invalidate it so it FORCES you to invalidate it, with this fuzzy pink bg thing. (Screenshot?)

Thanks Waddie96 (talk) 12:29, 20 August 2025 (UTC) Reply

@Waddie96: If you think adding an explanation is necessary, please take care of it yourself using Project:Village Pump. Shirayuki (talk) 13:30, 20 August 2025 (UTC) Reply

@Shirayuki Sorry this was such an unnecessary rant and attack on you. Waddie96 (talk) 06:44, 20 August 2025 (UTC) Reply

It seems that you are repeatedly making edits with Template:OOUI replaced without checking how they will be rendered. Such edits are better done on the corresponding sandbox page. Shirayuki (talk) 01:27, 24 August 2025 (UTC) Reply

Yes, I mistakenly Cmd-Enter to Publish but I think it switches tabs before it detects keyboard shortcut. Will be more careful. Waddie96 (talk) 04:22, 24 August 2025 (UTC) Reply

@Shirayuki By the way, as a sysadmin, may you please delete my userpage User:Waddie96. It's blanked but I want it to reflect my meta page rather. I couldn't find the DRV equivalent here. Thanks in advance. Waddie96 (talk) 04:27, 24 August 2025 (UTC) Reply

Re what do you think @Novem? Diff. I think everything between the template and the documentation should probably be deleted. Right now it's looking a bit like an article rather than a template. –Novem Linguae (talk) 17:58, 28 August 2025 (UTC) Reply