Jump to content

Commons:Translators' noticeboard

Add topic
From Wikimedia Commons, the free media repository
Latest comment: 1 day ago by Revi C. in topic Marking COM:China for translation
 SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 2 days and sections whose most recent comment is older than 300 days. For the archive overview, see Archive/. The latest archive is located at Archive/2025.
Translators' noticeboard
Translators' noticeboard

This is a noticeboard for all matters regarding translation of pages, and a meeting place for the translation administrators. Useful links: Documentation for the translation extension, Tutorial for translators. See also the sisterpage m:Meta talk:Babylon.

Start a new discussion
COMMONS DISCUSSION PAGES

Shortcut: COM:TN


Oldest pages needing changes marked for translation (June/July 2024)

[edit]
Latest comment: 3 days ago18 comments7 people in discussion

Per Aafi's comment above, below is a list of the oldest pages with pending changes that need to be marked for translation, starting from June to July 2024.

  1. Commons:Copyright rules by territory/Niger, since 06 June 2024
  2. Commons:Copyright rules by territory/Federated States of Micronesia, since 09 June 2024
  3. Commons:Copyright rules by territory/Uruguay, since 10 June 2024
  4. Commons:Copyright rules by territory/Yemen (no transclusion support), since 10 June 2024
  5. Commons:Picasa Web Albums files (no transclusion support), since 10 June 2024
  6. Commons:Wiki Loves Earth 2024 in Lebanon, since 14 June 2024
  7. Commons:Wiki Loves Earth 2024 in Palestine, since 14 June 2024
  8. Commons:Wiki Loves Earth 2024 in Syria, since 14 June 2024
  9. Commons:SPARQL query service/queries/examples, since 16 June 2024
  10. Commons:Moving files to Commons, since 17 June 2024
  11. Commons:Upload tools, since 17 June 2024
  12. Commons:Wiki Loves Earth 2024 in Jordan, since 26 June 2024
  13. Commons:Copyright rules by territory/Serbia (no transclusion support), since 29 June 2024
  14. Commons:Guide to layout/Category pages (no transclusion support), since 29 June 2024
  15. Commons:Copyright rules by territory/Italy, since 30 June 2024
  16. Commons:Wiki Loves Monuments 2022/Organizers, since 30 June 2024
  17. Commons:Galleries, since 01 July 2024
  18. Template:Upload campaign header Wiki Loves Earth in Ukraine pre-war pictures warning message/i18n, since 01 July 2024
  19. Commons:Copyright rules by territory/United Arab Emirates, since 02 July 2024
  20. Commons:User-specific galleries, templates and categories, since 02 July 2024
  21. Commons:Wiki Loves Africa 2024/Countries, since 08 July 2024
  22. Commons:Wiki Loves Earth in Albania & Kosovo 2024/Winners, since 11 July 2024
  23. Template:Iranian currency/i18n (no transclusion support), since 14 July 2024
  24. Commons:Copyright rules by territory/Hong Kong (no transclusion support), since 15 July 2024
  25. Commons:Free media resources/Map, since 15 July 2024
  26. Commons:Copyright rules by territory/Mauritania, since 16 July 2024
  27. Commons:How to detect copyright violations, since 16 July 2024
  28. Commons:Tribal Culture Photography Competition, since 19 July 2024
  29. Commons:Copyright rules by territory/Portugal (no transclusion support), since 20 July 2024
  30. Commons:Use of gender neutral language, since 22 July 2024
  31. Commons:Wiki Loves Earth/WLE Resources Center, since 25 July 2024
  32. Commons:Non-copyright restrictions, since 27 July 2024
  33. Commons:Copyright rules by territory/Qatar (no transclusion support), since 28 July 2024
  34. Commons:Copyright rules by territory/Senegal, since 30 July 2024
  35. Commons:User access levels, since 31 July 2024

Feel free to edit the comment to cross out any pages after they have been marked. Thanks. Tvpuppy (talk) 00:00, 8 June 2025 (UTC)Reply

Do you really think working with such a list is needed? Most cases only require one click as there are only minor changes often even outside of the translatable part. I would suggest to make a list only for cases where corrections in the translate syntax are needed. GPSLeo (talk) 05:32, 8 June 2025 (UTC)Reply
+1. Pages with minor changes get marked nonetheless. I find it personally tedious to each time visit Special:PageTranslation particularly to check pages with pending changes: so a list like this seems helpful, but those with minor changes shouldn't usually be listed. signed, Aafi (talk) 08:45, 8 June 2025 (UTC)Reply
It would make the long list of pages on Special:PageTranslation smaller. Also, I don't see any downsides of marking a page for translation. Thanks for compiling this list! Prototyperspective (talk) 16:12, 8 June 2025 (UTC)Reply
@Prototyperspective: could you please help revamp this list (as of current) and as GPSLeo suggested in June? signed, Aafi (talk) 06:09, 7 November 2025 (UTC)Reply
I didn't make this list and don't know how it was made (maybe a script or some Commons search with some sorting?). Tvpuppy made it. Tvpuppy, could you recompile it? And could you maybe also describe how you made the list so that others can compile it too and maybe a bot could then run that periodically for a new report page?
  • However, I wonder whether things as they currently are fine – wouldn't it be better if all pages get marked for translation automatically somehow, isn't that possible? There's so many pages with changes waiting to show up. Also the problem I described in the wish mark as solved at m:Community Wishlist/W308 still isn't solved as many such pages in categories haven't yet been marked for translation. I'm thinking of maybe creating another wish about things being automatically marked for translation (e.g. if not reverted for x days) – would there be any issues with this, what do you think? Often if not usually, changes should show up quickly or even need to such as in the case of temporary events like photo competitions. I don't know if there would be an issue with pages getting marked for translation that shouldn't be marked e.g. because only a few spaces were added (if so please explain), but such may be worth getting things to show up on pages much quicker than currently the case. Also it would be nice if you could mark pages with /Header at the end for translation soon.
Prototyperspective (talk) 12:36, 8 November 2025 (UTC)Reply
@Prototyperspective, perfect touch. We could ask @DreamRimmer to run his bot here for that purpose. It could automatically mark pages for translation where a human review isn't needed. signed, Aafi (talk) 16:20, 8 November 2025 (UTC)Reply
Hi :) How can I help you? My bot is currently set to mark pages for translation when there are no differences between the last marked and pending versions. At the moment, there are 37 pages on Commons that meet this condition. DreamRimmer (talk) 17:34, 9 November 2025 (UTC)Reply
@DreamRimmer, thanks for responding. Could you please have your bot do this here i.e, whenever such a page needs to be marked for translation, the bot takes its care. It'd just save our time. We can ask @Krd go grant TA rights for the purpose? ─ Aafī on Mobile (talk) 19:44, 9 November 2025 (UTC)Reply
Isn't the kind of automatic marking that would be useful the inverse of that: when pages have been edited and there are differences to the last marked version. One could have a delay of x days so that problematic changes can be reverted before the bot marks it for translation. I don't know if that's possible with the bot or in general and if (if so which) issues there would be with that. Prototyperspective (talk) 23:05, 13 November 2025 (UTC)Reply
The point of this bot task is to reduce the backlog on Special:PageTranslation by handling the obvious cases. It would be technically possible to mark any pages for translation, including those that do contain changes, but as I explained below, it would be practically impossible to get them right. —Tacsipacsi (talk) 14:19, 20 November 2025 (UTC)Reply
@Prototyperspective, thanks for the ping. Previously, I complied the list manually (sorting them by date using Excel), but I have just created a SQL query here that will compile the list automatically and available to see by everyone else.
However, the list basically includes almost everything from the "Pages with pending changes" section in Special:PageTranslation, since I'm not familiar with translating work, so I can't determine which pages only have "minor changes", as others have mentioned above.
Also, I agree that it will be very useful if someone (or a bot) can periodically transfer the query result list to Commons with a more useful format (e.g. adding links). Thanks. Tvpuppy (talk) 20:14, 8 November 2025 (UTC)Reply
Thanks for compiling it and now the quarry query (that's quite a lot of SQL!). A report could be created for it that gets updated by a bot similar to Commons:Report UncategorizedCategories with only infobox categories and other reports, some of which linked on that page. One could ask Mdaniels5757 and/or Wikiwerner and/or here.
If somebody is interested in manually importing it to a new report with clickable links, one could export the query results e.g. as wikitable and then using search and replace add the wikitext for the links or alternatively change the SQL to make things linked via the two square brackets on each side.
  • However, I doubt a report like that and translators' working on it is a good route. It may nevertheless be a good temporary thing. I think a method to get things automatically marked for translation would be much better and is the missing piece. Lots of changes are not showing up and by the time they are the page may already be irrelevant for example. Lots of changes to pages are rather small in terms of wikitext changed but have the effect that categories aren't cluttered with countless translated versions. Etc. I don't know how the translation tagging works but can't this be automated at least for most cases? Maybe some other wiki has it set up like that or there are tools for semi-automatically marking things for translation. (This could be a naive idea as of right now as I don't know much about how translation tagging works but I imagine theoretically it's possible for most cases even if difficult to implement and with exceptions and maybe it wouldn't be difficult at all or is already possible, no idea.) Is this issue about this?: phab:T252096 Automatically mark pages for translation on saving / update; maybe also relevant: phab:T131516.
Prototyperspective (talk) 23:39, 13 November 2025 (UTC)Reply
Thanks for the query, but actually there is a much easier and slightly more reliable solution: whether a page is marked for translation, and whether it has pending edits, is decided based on the revtag table, which is also available on Quarry. Here is my solution: https://quarry.wmcloud.org/query/99201. It might be unreliable on pages with imported revisions, as it assumes that revisions with higher revision IDs have more recent timestamps, but imports (other than file imports) are fortunately uncommon on Commons; and actually Translate itself also uses MAX(rt_revision), so my query is no worse than the one in Translate. ☺
Whether changes are “minor” is hard to tell via a query, especially without access to the actual page texts (those are not available on Quarry), but I added diff links that make it easier to see the changes. If the results are copied to a wiki page and you have Navigation Popups enabled, you can just hover over the diff links to see the differences (or a part of them if there are many differences – but if you don’t see everything, the changes are likely major). —Tacsipacsi (talk) 14:19, 20 November 2025 (UTC)Reply
If the page is identical to the latest marked version (e.g. it was vandalized and then reverted), that could be automatically marked. This is what User:DreamRimmer bot does (on Meta for now). However, if there are any changes, however small they are, they need human review: if the changes affect translatable parts, the translations may or may not need to be invalidated (a simple typo fix doesn’t need invalidation, but a single-character change that changes the meaning does); if they affect non-translatable parts, they may need to be made translatable; people editing the page may have got the syntax wrong, and translation admins have to correct it before marking the page for translation. —Tacsipacsi (talk) 11:03, 9 November 2025 (UTC)Reply
Thanks for these explanations! if the changes affect translatable parts, the translations may or may not need to be invalidated there would still be many that, basically just add text instead of altering any existing text. This may be detectable and markers be added or things invalidated to account for the newly added text. And maybe one could go on from there. But maybe it's not worth discussing this if it isn't already possible – I think I know too little about translation tagging to create a new issue or wish about more automated faster tagging and it doesn't seem to be possible any time soon if people here don't know of an existing way for this.
So what do you think could effectively speed up the translation tagging if there is anything? Prototyperspective (talk) 00:18, 14 November 2025 (UTC)Reply
there would still be many that, basically just add text instead of altering any existing text. Sure, but those aren’t entirely straightforward either.
  • Do they need to be translated at all? Templates often don’t need to be translated, or not in whole (only some of their parameters). However, there can be cases where it does make sense to translate them, e.g. {{Namespace}} should be left in the translatable part (translators may need to replace it with translated templates). File inclusions usually don’t need to be translated (only the captions), but if the file contains text (and it’s not an SVG that contains the translations itself), it does need to be made translatable (or translated in some other way, e.g. using {{LM}}).
  • Do all parts need to be translated? Templates, link targets, numbers etc. may or may not need to be translatable – most templates and link targets should be in <tvar>, as should regularly updated numbers, but static numbers are easier to translate without <tvar>, and templates like {{Namespace}} and Wikipedia links should definitely not be hardcoded to the English version/English Wikipedia.
  • If the text, although completely new, is added to an existing paragraph or list, should the existing translation unit invalidated or a completely new unit added? Both solutions have advantages and disadvantages, and even as a human it’s hard to decide sometimes; a bot would be even less likely to make the right decision. —Tacsipacsi (talk) 14:19, 20 November 2025 (UTC)Reply
So what do you think could effectively speed up the translation tagging if there is anything? My only idea is more/more active translation admins. —Tacsipacsi (talk) 23:05, 21 November 2025 (UTC)Reply

please confirm

[edit]
Latest comment: 15 days ago22 comments7 people in discussion

I have done some migration work on Template:Denkmalgeschütztes Objekt Österreich/i18n (feedback & help is welcome), and I feel that a translationAdmin has to confirm my changes, before I can adopt the language variants. best --Herzi Pinki (talk) 18:57, 20 August 2025 (UTC)Reply

I am not someone who has an extensive knowledge of templates, so probably @Tacsipacsi might be able to deal with this signed, Aafi (talk) 07:54, 21 August 2025 (UTC)Reply
I feel confident with templates. It's only about the embedding of templates in the translation system and maybe how to extract the two new error texts to separate parameters. --Herzi Pinki (talk) 10:53, 21 August 2025 (UTC)Reply
thx OifigeachWMIE, something is missing. Template:Denkmalgeschütztes Objekt Österreich/i18n: Translate this page; This page contains changes which are not marked for translation. How can I mark them for translation / transfer the changes in Template:Denkmalgeschütztes Objekt Österreich/i18n to Template:Denkmalgeschütztes Objekt Österreich/i18n/en etc.? best --Herzi Pinki (talk) 11:07, 27 August 2025 (UTC)Reply
@Herzi Pinki, they unfortunately responded in a wrong thread ;) I have marked the changes for translation. Let me know in case this breaks anything. Marking this as ✓ Done from here. signed, Aafi (talk) 15:03, 27 August 2025 (UTC)Reply
Better. And now I need help, not just support. The translated stuff should call {{Denkmalgeschütztes Objekt Österreich/Id|$1|2=|3=}} unconditionally, but it doesn't. What is wrong here? best --Herzi Pinki (talk) 18:25, 27 August 2025 (UTC) @Aafi: as requested --Herzi Pinki (talk) 18:26, 27 August 2025 (UTC)Reply
@Jarekt, would you be able to look at this? ─ Aafī on Mobile (talk) 18:56, 27 August 2025 (UTC)Reply
I’m not sure how the template works but if you wanted to call {{Denkmalgeschütztes Objekt Österreich/Id|$1|2=|3=}} unconditionally, then you don’t need the if-statement. The current setup means that it is doing “If the result of the Denkmalgeschütztes Objekt Österreich/Id is X, then do Y”, since both X and Y is not specified, it is not doing anything. Tvpuppy (talk) 01:14, 28 August 2025 (UTC)Reply

Please double check the templates above in Category:Pages using duplicate arguments in template calls -- ato (talk) 18:50, 28 August 2025 (UTC)Reply

was away for the we, will take care. I'm looking for missing }}? --Herzi Pinki (talk) 12:06, 31 August 2025 (UTC)Reply

after a lot of unsuccessful trials, I again need help: @Aafi: to

  • check my changes
  • commit my changes

I'm going with {{<tvar name="2x">Denkmalgeschütztes Objekt Österreich/Id|{{{1|}}}</tvar>|2=Id missing|3=needs migration to HERIS-ID}} in Template:Denkmalgeschütztes Objekt Österreich/i18n. The purpose is to have symmetric curly braces (I spent hours to find the cause of the asymmetry). The code in the language specific stuff than is: ... {{$2|2=Id missing!|3=migration to HERIS-ID needed}} ..., which should expand to {{Denkmalgeschütztes Objekt Österreich/Id|{{{1|}}}|2=Id missing!|3=migration to HERIS-ID needed}} - please check! If ok, please commit my changes. Sorry that I broke the code for the whole weekend. best --Herzi Pinki (talk) 18:29, 31 August 2025 (UTC)Reply

@Herzi Pinki, I can't seriously help in checking if the changes are right (I hardly have novice knowledege of templates) but if someone with good knowledge of templates says that it's okay to go, I will be glad to mark the page for translation. signed, Aafi (talk) 09:55, 1 September 2025 (UTC)Reply
@Mdaniels5757, would you probably help here? :) signed, Aafi (talk) 09:58, 1 September 2025 (UTC)Reply
@Aafi @Herzi Pinki Looks good to me, ✓ Done —‍Mdaniels5757 (talk • contribs) 15:18, 1 September 2025 (UTC)Reply
@Mdaniels5757: thanks a lot. Looks ok. best --Herzi Pinki (talk) 20:14, 1 September 2025 (UTC)Reply
translation to ar is missing, I get confused when I have open and closed stuff with rtl direction. --Herzi Pinki (talk) 20:16, 1 September 2025 (UTC)Reply

Sorry for not responding earlier (I didn’t have time when I got pinged, and then forgot about the ping). Unfortunately the chosen solution doesn’t work in all languages, for example it doesn’t work in my native language Hungarian.

The problem is that you split up the phrase with HERIS-ID 123456, ObjektID 12345 arbitrarily. The word with is the preposition of HERIS-ID and ObjektID – in English and German. However, other languages use other ways to express the grammatical connection, e.g. Hungarian uses agglutination (HERIS-ID-ja 123456, ObjektID-ja 12345) and Slavic languages like Slovak use inflection. Both of these would require changing the words HERIS-ID and ObjektID, which is impossible with the current setup. (Probably there are non-European languages that work yet differently, although I don’t have examples off the top of my head.)

A better solution would be:

Tacsipacsi (talk) 10:35, 8 November 2025 (UTC)Reply

@Herzi Pinki: FYI, if you haven't seen this yet. signed, Aafi (talk) 16:37, 8 November 2025 (UTC)Reply
thanks Aafi --Herzi Pinki (talk) 18:50, 8 November 2025 (UTC)Reply
  • the overall problem for me was that once the translation stuff has been applied to this template, it was really hard to modify the content of the template (except for minor text changes), especially without breaking anything and with so many transclusions. I just wanted to expand the functionality of my template and now I have to deal with the translation stuff.
  • the complexity arises from
  • the template does a legacy migration accepting old ObjektIDs and new WD-IDs as arguments as well, and has to differ correctly. No clear cut possible at the moment.
  • the values of the Ids shown in the template depend on existence of WD-properties.
  • generated links for supporting our workflows are created differently depending on parameter constellation.
  • Is there a way to develop your ideas Tacsipacsi in a copy of Template:Denkmalgeschütztes Objekt Österreich/i18n without the need to duplicate the whole template tree?
  • sorry, did not get your 3rd point, what are separate translation units; but the rest?
    • how do I switch between the three cases without duplicating the logic (now in Template:Denkmalgeschütztes Objekt Österreich/Id)?
    • is there really a need for HERIS-ID + ObjektID (and how?), or wouldn't it be possible to concat both (assuming that the comma as concatenation is ok in all languages, or have a separate translation unit for the concatenation string. How does concatenation work in rtl languages?). Otherwise I have to insert the ID values into that compound translation unit, don't know how (using {{Str rep}}?).
    • @separate translation units (like this in {{Denkmalgeschütztes Objekt Österreich/i18n}}?):
| lang = {{TRANSLATIONLANGUAGE}}
| 1    = {{{1|}}}
| 2    = <translate><!--T:2--> Upload more media to this category</translate>
| 3    = <translate><!--T:3--> Id missing</translate>
| 4    = <translate><!--T:4--> needs migration to HERIS-ID</translate>
| 5    = <translate><!--T:5--> HERIS-ID<!--this is the immutable literal name of an id, do not translate. You can add language specific inflection, prefix and/or suffix--></translate>
| 6    = <translate><!--T:6--> ObjektID<!--this is the immutable literal name of an id, do not translate. You can add language specific inflection, prefix and/or suffix--></translate>
| 7    = <translate><!--T:7--> HERIS-ID + ObjektID</translate> ?? or
| 7    = <translate><!--T:7--> HERIS-ID val1, ObjektID val2<!--do not change val1 and val2 strings!--></translate> ??
maybe it's better to make a clean rewrite from scratch, and apply the translation stuff again afterwards (by an expert). The current template seems to be bogus anyhow.
--Herzi Pinki (talk) 18:50, 8 November 2025 (UTC)Reply
@Herzi Pinki: I can only say what a separate translation unit means. In the case above, T2, T3, T4 and the rest are each a separate unit. Each string that you translate separately in the translation system is a different and separate unit. signed, Aafi (talk) 19:17, 8 November 2025 (UTC)Reply

Is there a way to develop your ideas Tacsipacsi in a copy of Template:Denkmalgeschütztes Objekt Österreich/i18n without the need to duplicate the whole template tree? I’m not sure what “duplicating the whole template tree” means, but I don’t think any page other than Template:Denkmalgeschütztes Objekt Österreich/i18n needs to be changed, so you could copy just that to a sandbox page.

how do I switch between the three cases without duplicating the logic (now in Template:Denkmalgeschütztes Objekt Österreich/Id)? A bit of duplication (one way or the other) is unavoidable, but most of the duplication can be avoided by simply not using Template:Denkmalgeschütztes Objekt Österreich/Id – with that, you don’t duplicate the logic, but simply move it.

is there really a need for HERIS-ID + ObjektID (and how?), or wouldn't it be possible to concat both (assuming that the comma as concatenation is ok in all languages, or have a separate translation unit for the concatenation string. How does concatenation work in rtl languages?). Exactly that’s the problem: concatenation works differently in different languages. Not only RTL languages, but also other languages, most notably Chinese and Japanese, which use a full-width comma (、) and no space after it. And even in languages that do use the same punctuation as English and German, “and” (or some variant) may read more naturally than a comma. Using three separate messages allows for more natural translation, at a relatively small cost (there are already two and a half branches, that’d increase to three).

Otherwise I have to insert the ID values into that compound translation unit, don't know how (using {{Str rep}}?). That’s what translation variables (<tvar>) are for.

I could change the interface of Template:Denkmalgeschütztes Objekt Österreich/Id to return a slash separated list of id-values I can strip using {{ParmPart}} / #titleparts. As I wrote, I think it’s best to just leave out that subtemplate.

can you provide a skeleton where I can then put my logic? Well, it turned out to be more of a complete solution than a skeleton. 🙂 

<languages />
<onlyinclude>{{Denkmalgeschütztes Objekt Österreich/layout
| text = {{tmpl
  |0=<translate><!--T:1--> This {{#if:{{#ifeq:{{NAMESPACE}}|{{ns:14}}|1}}|category|media}} shows the protected monument with $2 in Austria.</translate>
  |2={{#ifeq:{{Str left|{{{1|}}}|1}}|Q
    |{{#if:{{Data |item={{{1|}}} |property=P2951 |displayformat=raw}}
      |<translate>{{#if:{{Data |item={{{1|}}} |property=P9154 |displayformat=raw}}|HERIS-ID {{Data |item={{{1|}}} |property=P9154 |displayformat=raw}}|missing HERIS-ID}}, <small>ObjektID <span class="plainlinks">[https://denkmalliste.toolforge.org/index.php?action=EinzelID&ID={{Data |item={{{1|}}} |property=P2951 |displayformat=raw}} {{Data |item={{{1|}}} |property=P2951 |displayformat=raw}}]</span></small></translate>
      |<translate>{{#if:{{Data |item={{{1|}}} |property=P9154 |displayformat=raw}}|HERIS-ID {{Data |item={{{1|}}} |property=P9154 |displayformat=raw}}|missing HERIS-ID}}</translate>
      }}<!--

    legacy ObjektID: -->
    |{{#if:{{{1|}}}
      |<translate>ObjektID <span class="plainlinks">[https://denkmalliste.toolforge.org/index.php?action=EinzelID&ID={{{1}}} {{{1}}}]</span> <small>(needs migration to HERIS-ID)</small></translate>
      |<translate>missing ID</translate>
      }}
    }}
  }}
| lang = {{TRANSLATIONLANGUAGE}}
| 1    = {{{1|}}}
| 2    = <translate><!--T:2--> Upload more media to this category</translate>
}}</onlyinclude>
{{translated tag|marker}}

(I don’t see the <tvar>s in the rendered code for some reason, please copy the source code). I did some changes in addition to the translation markup:

  • Used missing ID / missing HERIS-ID instead of <Id missing!> – it reads more naturally, and avoids problems, should the translation happen to be a valid HTML/XML tag.
  • Used <small> instead of <span style="font-size:smaller"> to avoid overwhelming translators with syntax. I also think that <small> is semantically correct here. Moved the plainlinks class in the translation variable, so that translators don’t even see it (although I’m not sure if it’s needed at all; the old version didn’t use to have it).
  • Moved the “needs migration” message from a tooltip to a parenthesized note. This makes translation easier (no headaches with markup appearing in an HTML attribute), and avoids accessibility issues (tooltips are invisible on touchscreen devices such are smartphones).

The $2 in the main translation unit will appear on the translation interface as if it was a regular <tvar>, but {{Tmpl}} allows including more complex syntax.

Note that the translation interface shows message documentation (in the right column), what you wrote in HTML comments above should be added there (except for the comment about val1 and val2, which doesn’t need to be added anywhere ­– since they are translation variables, translators are expected to know how to handle them). —Tacsipacsi (talk) 12:59, 9 November 2025 (UTC)Reply

Marking nearly all Category and /Header pages for translation

[edit]
Latest comment: 4 days ago2 comments2 people in discussion

Could somebody please do this? Most of the category pages changes are small. With /Header pages I mean all the pages that end with /Header...those would be important to mark for translation. Prototyperspective (talk) 21:28, 19 November 2025 (UTC)Reply

There are almost 17.5 million category pages on Commons. No, nobody can mark 17.5M pages for translation, nor should one. Translatable categories basically make sense only if the pages they contain are also translatable, otherwise the translations end up being empty categories. The vast majority of Commons categories contain files (and subcategories containing files), which aren’t translatable. {{Mld}} and {{Wikidata Infobox}} do a much better job in them. There are probably a few categories that indeed need translation (I’d guess a few dozens of the 17.5M categories), but please list them (or tell better criteria) if you want them to be marked for translation.
/Header pages are much less in number (~250), but about half of them are in the User or User_talk namespace, where pages shouldn’t be marked for translation without the consent of the affected users. The majority of the other half could indeed be marked for translation, although there are some exceptions: for example, Commons:Deletion requests/Commons:Upload help/Header should definitely not be translatable, but the value of translating Commons:Universal Code of Conduct consultation/Header is also questionable (the consultation is closed, so people are unlikely to read that page at this point). Fortunately ~100 pages are few enough to be handled manually, so someone may go through them (I don’t have time right now). The SQL query I used to find them (it took almost two minutes to complete): 
SELECT page_namespace, page_title FROM page WHERE page_namespace NOT IN (2, 3, 6) AND page_title LIKE '%/Header' AND page_id NOT IN (SELECT rt_page FROM revtag WHERE rt_type = 'tp:mark') AND page_is_redirect = 0;
—Tacsipacsi (talk) 14:51, 20 November 2025 (UTC)Reply

Marking COM:China for translation

[edit]
Latest comment: 1 day ago2 comments2 people in discussion

Hello, can an admin modify this page for translation, as it has a few un-synced updates. 0x0a (talk) 07:09, 24 November 2025 (UTC)Reply

Translation unit name 108 is used more than once. - removed double use of 108. ✓ Done via Special:Diff/1120675726. — regards, Revi 07:44, 24 November 2025 (UTC)Reply
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Translators%27_noticeboard&oldid=1120676050"