MediaWiki talk:Cx-source-page-selector-no-suggestions
Latest comment: 2 years ago by Xaosflux in topic Protected edit request on 6 February 2022
Protected edit request on 6 February 2022
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hello, administrators, interface editors, and others who can edit the MediaWiki namespace…
Per MOS:CURLY, the curly apostrophe in "You don’t need to be an expert to create a great translation" should be changed to a straight apostrophe.
So, in wikitext, it should look like this: Think of any topic of your interest. You don't need to be an expert to create a great translation.
Thank you. — 3PPYB6 — TALK — CONTRIBS — 18:26, 6 February 2022 (UTC)
- On hold - this should get fixed upstream. — xaosflux Talk 21:01, 6 February 2022 (UTC)
- Not done in favor of fixing upstream, request phab:T301090 has been opened. Thank you for letting us know, @3PPYB6:! — xaosflux Talk 21:15, 6 February 2022 (UTC)
- @Xaosflux — I already subscribed to the thread, but, for clarification, does this mean that it'll be fixed via Phabricator? — 3PPYB6 — TALK — CONTRIBS — 03:32, 7 February 2022 (UTC)
- @3PPYB6: that's the plan. There are actually 4 of these with the same issue, and it is a problem on every project (worldwide) that uses ContentTranslation - so it is best to fix it in the software, if we fix it by editing this message that will put a "local override" in that has to be locally maintained. The phab route is "slower" but ultimately better. If this was causing some sort of urgent impact on out editors, we'd do it anyway - but in this case it is a minor cosmetic, so I don't see a reason to add local technical debt here. Good catch on finding it though! — xaosflux Talk 11:08, 7 February 2022 (UTC)
- @Xaosflux — I already subscribed to the thread, but, for clarification, does this mean that it'll be fixed via Phabricator? — 3PPYB6 — TALK — CONTRIBS — 03:32, 7 February 2022 (UTC)
- Not done in favor of fixing upstream, request phab:T301090 has been opened. Thank you for letting us know, @3PPYB6:! — xaosflux Talk 21:15, 6 February 2022 (UTC)