Support

From translatewiki.net
Jump to: navigation, search

Note Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries, see also documentation.


Contents

Thread titleRepliesLast modified
Rename request004:14, 14 December 2017
Template loop110:16, 10 December 2017
Change my username to Athena in Wonderland015:35, 8 December 2017
Filter out API messages?218:02, 7 December 2017
Special:Translate: Group ext-0-all cannot be retrieved214:28, 4 December 2017
Not translated words000:55, 5 December 2017
Export generates empty <resources/>013:03, 28 November 2017
Add support for Western Armenian (hyw)610:39, 27 November 2017
Change username106:52, 16 November 2017
Please support "Traditional Mongolian Script"521:46, 15 November 2017
LibreRouter: new project with software and HowTo booklets1315:56, 15 November 2017
MediaWiki talk:Sp-translate-data-MagicWords/ce313:43, 15 November 2017
About MediaWiki:Purge/en105:28, 10 November 2017
Support for Guianan Creole language ! 013:29, 13 November 2017
User:Fitoschido behavior315:27, 7 November 2017
{{support}} Adding TheWikipediaLibrary Card Platform TranslateWiki311:29, 3 November 2017
Support for Kumyk609:44, 3 November 2017
How to replace wrongly translated spelling of a word appearing in language list for language code anp420:50, 1 November 2017
Wikimedia:Xtools-edits/sr112:04, 1 November 2017
See to what languages my project has been translated207:44, 1 November 2017
First page
First page
Previous page
Previous page
Last page
Last page

Rename request

Please rename my account to MacFan4000 Thanks.

01:24, 12 December 2017

Template loop

Today I am too supid to detect why there is a template loop on e.g. MediaWiki:Smw-category/qqq

16:14, 9 December 2017

Templates like {{msg-mw|Smw browse hide incoming}} loop too all of a sudden ...

09:05, 10 December 2017
 

Change my username to Athena in Wonderland

Hello, please change my username to Athena in Wonderland, like my username in the Wikipedia, thanks. I changed my username in Wikipedia in 2015, but I forgot to request a change of the username here too. Thanks and greetings from the Portuguese and Mirandese communities.

18:25, 7 December 2017

Filter out API messages?

There are soooo many API-specific messages, and they will only be read by a tiiiiiny fraction of the people who use MediaWiki. I'd like to focus on translating anything else, but as far as I know there's no way to do that. Would it be possible to implement something to filter them out from Special:Translate (and the stats at Special:LanguageStats)?

12:14, 15 September 2017

I second that.

23:01, 17 September 2017

The same with the localized Wikimedia project names, Dissemin, iHRIS, iNaturalist, Mifos and future big projects. I would prefer a message prefix filtering.

07:54, 28 September 2017
 
 

Special:Translate: Group ext-0-all cannot be retrieved

16:31, 2 December 2017

There was a slowdown. Technical details: HHVM bytecode cache was full and it started interpreting new code. I restarted HHVM and things should be fast again.

13:46, 4 December 2017

Thanks!

14:28, 4 December 2017
 
 

Not translated words

12:19, 4 December 2017

Export generates empty <resources/>

I wanted to try to download a localization manually.

So, I went to https://translatewiki.net/w/i.php?title=Special:ExportTranslations&group=commons-android-strings and selected "Italian" (a language known to have near-complete localization) and "Export in native format", then clicked "Fetch".

Problem: All I get is a nearly empty file containing only "<resources/>".

Not a problem since I can get them from our Git, but I just thought I would let you know about this problem. Cheers!

06:14, 28 November 2017

Add support for Western Armenian (hyw)

Edited by author.
Last edit: 22:55, 14 April 2017

As per langcom discussion on WMCON, the code hyw will be requested for w:Western_Armenian and we are sure it will be approved, but only at the earliest in December. But the users would already like to translate into it. Pinging user:Raymond.

13:39, 2 April 2017

The usual information is needed: Translatewiki.net languages.

13:47, 2 April 2017

Note that on Wikidata: d:User:Nikki/Permanent duplicates#Armenian, where "hy-arevela" used for Eastern and "hy-arevmda" for Western, because of https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry :

...
%%
Type: variant
Subtag: arevela
Description: Eastern Armenian
Added: 2006-09-18
Prefix: hy
%%
Type: variant
Subtag: arevmda
Description: Western Armenian
Added: 2006-09-18
Prefix: hy
%%
...
14:06, 2 April 2017

Thank you, we are well aware of this subtag which was introduced as an expedient with the knowledge that a formal language code would be required.

23:38, 2 April 2017
 

All right,

  • A language code from ISO 639-3 or the Ethnologue website (for example 'de') - hyw [proposed]
  • The language name in English and in its own language (for example 'German – Deutsch (de)') - Western Armenian - արեւմտահայերէն
  • Is the language RTL or LTR (written from right to left or left to right) - LTR
  • If the language is commonly written in more than one script, please say in which script the language should be enabled. Other variants can be enabled as and when translators for those variants volunteer. - Armn only
  • (For MediaWiki) Should the language fall back to another language other than English? If so which? - Fallback should be to hy.
23:36, 2 April 2017

Once the code has been approved, it can be added. For now, this request will be denied.

11:55, 20 May 2017
 
 
 

Change username

Could you please change my username to Épine? Thanks.

01:12, 16 November 2017

Done. Thanks for your continued translations to ckb!

06:52, 16 November 2017
 

Please support "Traditional Mongolian Script"

"Traditional Mongolian Script" ([w:https://en.wikipedia.org/wiki/Mongolian_script] ) are used in mongolia and Inner Mongolia of China to this day to write Mongolian , which based on this classical vertical script. In Mongolia, the Cyrillic script writing system is used. Until 1990, only elders used to read and write the Mongolian script. But in the 1990s, secondary schools began to intensify the teaching of the Mongolian script.In China, the ethnic Mongol population was nearly 6 million according to a 2010 census. Many of them still receive nine-year compulsory education in Mongolian using the traditional Mongolian script.Mongolians living in Inner Mongolia are not familiar with the Cyrillic script and use the Mongolian script writing system only. They are unable to read Mongolian Wikipedia in Cyrillic. Data: A valid ISO 639-1 or 639-3 language code:mon [1] Unicode range: [2] The language name in English and in its own language: mongolian -ᠮᠤᠨᠭᠭᠤᠯ ᠬᠡᠯᠡ writing-mode: vertical-lr. Now, Internet Explorer, Safari, and Chrome support CSS writing-mode: vertical-lr. Default should still be "mon" in Latin alphabet. Please support "Traditional Mongolian Script".

00:50, 5 January 2014

I would exclusively oppose mn-Mong, as currently the Traditional Mongolian language is having a test-Wikipedia against at incubator:Wp/mvf.

13:15, 27 May 2017
  • One of the reason why the wiki is at mvf because creation of test wiki with codes like mn-Mong are not allowed?
  • Code on TWN do not need to correspond to wiki site code. For example, we have lzh and yue in TWN, while their wikis are now using zh-classical and zh-yue code.
22:20, 12 November 2017

I would leave first question for @Nikerabbit:, as the code selection should be judged by him. For the second question, URLs of both wikis are to be renamed, but not soon, technical blocks are listed on phab:T172035.

03:50, 13 November 2017
 

@C933103: The another reason that I oppose mn-Mong is the touchability, as a matching example, the Azerbaijani can be written (commonly) in Latin and Persian (aka Perso-Arabic) scripts, however, due to the tonal incompatible, we enabled both ISO 639-1 az for Latin (the national official language of the Republic of Azerbaijan, which should points ISO 639-3 azj "Northern Azerbaijani") and ISO 639-3 azb for Persian (the regional official language of South Azerbaijan province (?) of Iran, called "Southern Azerbaijani" in SIL website).

12:51, 13 November 2017

I believe there are no "incompatibility" between khk Mongolian and mvf Mongolian when writing with the Mongolian script. (Although Russian-originated words and Chinese-originated words will be different).

21:46, 15 November 2017
 
 
 
 

LibreRouter: new project with software and HowTo booklets

Hi, we're curious about whether TranslateWiki might be a good home for the translation of a project we're working on, the LibreRouter. We want to translate software interfaces, documentation, and also an illustrated booklet about how to use the LibreRouter. There's more info about the project at https://librerouter.org/.

The code is in the repositories at https://github.com/libremesh, and is in English. All the software is in active development or pre-development. One of the apps in active development that's already giving attention to translation is https://github.com/libremesh/lime-app.

The source language for the HowTo booklets is Spanish. The text for those booklets isn't ready to translate yet, though we hope to have first drafts ready no later than mid-October.

Some people from our community would join the translation effort, especially for English, Spanish, Portuguese, and maybe German and Afrikaans.

We've tried the interface for translating software strings on TranslateWiki, and we like it. We're not sure if the format of the HowTo booklets is compatible with TranslateWiki, since those are long paragraphs of text. We tested on Zanata, and it worked with .ODT files.

If we need to use a different file format for the code i18n/l10n or for the booklets, we're open to that.

We're interested in TranslateWiki because of the community of translators already active here, and the long-term continuity of the TranslateWiki platform and community.

Does this look like a good match, LibreRouter with TranslateWiki? What would be necessary or desirable actions from the LibreRouter community in order to move forward? We're available to chat on IRC or via e-mail or here on this thread.

15:05, 21 September 2017

Hi TranslateWiki team,

I wonder how to get in touch with you so that we can figure out whether LibreRouter can join TranslateWiki. I don't see any email address to write to, and the IRC webchat isn't working at the moment (and I don't usually spend any time on IRC). I will respond here to the items listed on the New Project criteria page, and hopefully this will make it clearer whether LibreRouter can join TranslateWiki.

- Openness: yes, LibreMesh software and documentation use free and open source licenses, such as GPLv3.

- Development: yes, LibreMesh is in active development, using a Git repository for version control. The project has periodic releases of LibreMesh, and will have periodic releases of other software and documentation (which has't yet reached first release). Time to get translations into use is currently unknown, and depends on how often network maintainers update the firmware on their router (perhaps we could automate part of this process to make TIU faster, or have a translation-only auto-update so as not to deal with potential software bugs and version incomatibilities between routers on a network), and how often users update Lime-App on their phones. More discussion could be helpful.

- Integration: It seems very reasonable that TranslateWiki staff could have direct push commit access.

- i18n Support: two key parts of the LibreRouter system support i18n already (LibreMesh GUI and Lime-App), though I do not know if they support the details of i18n mentioned on the TranslateWiki New Project page. I have passed the Localization for Developers link to developers and they're looking at it.

- Communication: I am the current liason, and I am not active in development. I have communication with the developers, and it's feasible that one of the developers may takeover the liason role and/or at least one developer might be active in translatewiki.net. I am a user and tester of the software and documentation.

- File formats: yes, we use translation files, I don't know if they're in one of TranslateWiki's preferred formats. Here's a translation file for Lime-App https://github.com/libremesh/lime-app/blob/master/i18n/translations/es.json , and I'll find one for LibreMesh.

We need to start translating this month, October 2017.

What else do you need to know in order to decide whether LibreRouter can join TranslateWiki?

cheers, Pato

20:35, 6 October 2017

The JSON format looks okay except we don't include the language code as a key in the file (it's already there in the filename). Would you consider changing that format?

Is the repository in GitHub your main repository?

I would request to add some message documentation to guide the translators (see https://www.mediawiki.org/wiki/Localisation#Message_documentation).

20:45, 6 October 2017

Does taking the language code as a key out of the file just mean removing the line   "es": { As well as the closing bracket } ?

Yes, the repository in GitHub is our main repository.

We will add some message documentation to guide the translators based on the advice at https://www.mediawiki.org/wiki/Localisation#Message_documentation. It might take us a week or so to start adding that documentation.

21:03, 14 October 2017

Yeah if the file looks like following, then we support the format.

{
  "key": "value",
  ...
}
14:10, 15 October 2017
 

I'm talking with coders... we're moving forward on changes to be more compatible with TranslateWiki, and we're coming up with questions about TranslateWiki:

1) We're looking at 4-7 different pieces of software to translate. Each piece has it's own practices of what branch development happens in, so we're getting all that info in one place. Arranging direct push commit access for TranslateWiki to the development branch of each software is part of our conversations.

2) If one or two pieces of software are ready to connect with TW.net before the others, can we go ahead and connect those? If yes, how?

3) Can the TW.net platform translate the Readme.md file for each software? Or maybe we'll have to setup a separate help folder with a file in each language, like at https://github.com/LonamiWebs/Stringlate/tree/master/help -- would that work? Is there a TW.net parser-generator for MarkDown .md files?

4) Is there a smartphone interface for TW.net, either via a web browser or a special app? (It seems that using a computer with a keyboard and at least a 10-inch screen is easier for translating, but sometimes a smartphone is the only device available to a translator.)

5) How do we include screenshots in the translator notes (the qqq messages)?

03:29, 11 November 2017

1) Are those pieces in different git repositories?

2) Yes we can. I need the basic info about the repository, push access, file format.

3) We do not have MarkDown parser at the moment. It could work as translatable page.

4) Amir is working on a Telegram app. There is also unmaintained android app. The web interface should accommodate tablets pretty well, but mobile phones are not well supported.

5) Uploading them here in translatewiki.net and using the wikitext syntax to include them. Can also put direct links to images, if they are too large, but then translators have to click.

15:24, 12 November 2017

1) Yes, each piece in a different repo.

2) The first two pieces that I think are ready:

3) "It could work as translatable page." Do you mean it could work without a parser?

4) Cool! I hope Amir and crew get that Telegram app to a usable release.

5) Where in TranslateWiki would we upload the screenshots? When you say "too large", what are the maximum dimensions of the image (like 80px by 200px)? What is the maximum file size?

23:22, 13 November 2017
 
 

6) Where is the code for the parser-generators that are currently in use on TW.net? We'd like to look at them to get a sense of what it would take to write another.

7) Any suggestions on how to internationalize this relatively simple web page interface, https://github.com/libremesh/chef ?

14:36, 12 November 2017
15:26, 12 November 2017

6) Thanks, we'll look at those.

7) The maintainer of the software to internationalize (Chef) says: "I'm currently not using jQuery in Chef but plain JavaScript. I'd rather keep it that way - if possible. Some quick searches resulted in https://github.com/eligrey/l10n.js/ - maybe thats already enough?"

23:23, 13 November 2017
 
 
 

Also, what are the howto booklets you mention in the subject? Our primary focus is on software user interfaces. [edit] We don't currently support ODT files. Some kind string extraction to another format would be needed. Are the booklets created so that they can be automatically generated from the translated texts (i.e. no hardcoded positionings with length restrictions)?

20:46, 6 October 2017

The HowTo booklets are a series of guides about the social, technical, and economic aspects of how to create and maintain a community network, with the LibreRouter as the example hardware and software. The idea is that each booklet will be laid out by hand after translating. This means that an automated workflow (as is used in software) is not our plan for the first three languages, and we would join TranslateWiki.net only for the software interfaces.

However, if anyone can suggest a workflow to create the booklets that aligns with the way TranslateWiki.net functions, we're interested to try it out since that could facilitate the translation of the booklets into many more languages. Perhaps the ODT parser from the Zanata translation management platform could be included in TranslateWiki.net, or perhaps we could use a different format. Or perhaps a bit of the BookType software used to create the books at Flossmanuals.net could be reused.

21:22, 14 October 2017

I haven't done that before. I am sure there are string extraction plugins for ODT. The problem is that usually booklets have quite tight positioning and size constraints. Doing the layout manually for many dozens of languages (and dealing with possibly frequent updates) doesn't scale. But a flexible or simple ODT file we could probably support if there is a suitable parser-generator we can integrate.

14:29, 15 October 2017
 
 
 
 

Please pay your attention to my question on the page.

11:22, 15 November 2017

I'm afraid, the only possible way to handle your first sentense "User:Nemo_bis, Can I remove Russian words from here?" is, as like Ukrainian, drop the Russian fallback, which as Chechen is also a language of Russian Federation, I ask now: is it really fair to you?

Here are some important notes if you have ever accepted that:

  1. You have to translate messages from, and only from, the English, no longer Russian, also ALL the untranslated messages will be English rather than Russian;
  2. You have to make sure every Wikidata stuffs (where you have to visit wikidata.org and find templates, modules, items and properties, and some of templates, modules and ALL Wikidata MediaWiki: namespace pages will also require sysop edit requests) are having proper Chechen translations;
  3. You have to make sure the donation CentralNotice BANNERS are proper translated (you have to ask Meta-Wiki administrators to get the translateable message)
13:03, 15 November 2017
 
Edited by 2 users.
Last edit: 05:27, 10 November 2017

Could you please set up translation for the Purge extension. Repo @ https://github.com/Hutchy68/Purge. @translatewiki has been added as a collaborator to the project.

Thanks!

04:36, 10 November 2017

I closed this as it appears the project was already added. Thanks!

04:49, 10 November 2017
 

Support for Guianan Creole language !

Hi everyone ! Would like to request support for Guianan creole language. Portal link: https://translatewiki.net/wiki/Gcr Looking forward to your reply Thanks !

22:20, 8 November 2017

I'm sorry to bring this up here, but it's not the first time this happened and I need help to deal with this user.

User:Fitoschido is a very active Spanish translator. Not only he does a lot of work but also it's good work. That works as long as no one else challenges his contributions. In simple terms, he is not a "team player". When you try to contact him and discuss his changes, he doesn't reply or if he does, he doesn't want to reach consensus. It seems that his opinions are the only ones that matters. And this is going on since I came here (3 years ago). Most of the time I try to avoid conflict. I don't want to enter edit wars whith him (or anyone else). I avoid "touching" messages that he translates, etc. I'm not the only one having trouble with him.

But that's not the most serious thing. In the past, he called another users "imbecil" and "stupid". I tried to talk to him, asking to apologise to them so we can have a more pleasant enviroment for all of us (volunteer translator in our spare time) but nothing happened.

All our previous exchange in Translatewiki was in Spanish so I don´t know if the rest would be able to follow what happened, but it's there in his Talk page, in his comments, etc.

Hope someone else here at Translatewiki would help. I want to make clear that this is no personal at all (he makes many and good contributions most of the time) and that what I said is very verifiable in this very site (if you know Spanish).

Regards.

23:03, 2 November 2017

I suggest talking with other Spanish language translators, and if they make conclusion that that user's certain translation(s) he/she does not "allow to touch" are really incorrect – try to talk them, "finalize" why they are incorrect and try again to correct them – and if that user still does not accept those correct and explained translations, use block on that user for certain periods of time, or indefinitely if still refuses to change (I hope blocking users here is possible same or similar as on Wikipedia).

PS After I posted this answer here, I got notification about New message; this should be fixed so that after user A posts something, user A does not get notification about new comment on some thread. Also, publishing changes when making new post still triggers "Do you want to leave this site, Changes you made may not be saved"...

14:39, 5 November 2017

We use Liquid Threads here for discussion. It is no longer maintained. I am exploring the possibility to move to Flow, which is still maintained. But it won't be easy and migration is likely to be disruptive to some extend so it is not going to happen very soon.

11:33, 7 November 2017

Note: I vote strongly support to migration, because since October, nearly all of my actions are stucked by a huge, huge and huge number of CSRF token errors. Do not say some "wrong from HHVM", HHVM doesn't result any wrong, the only wrong is from LQT which is too hard to uninstall.

15:27, 7 November 2017
 
 
 

{{support}} Adding TheWikipediaLibrary Card Platform TranslateWiki

I've been working on TheWikipediaLibrary Card Platform https://wikipedialibrary.wmflabs.org/ for some time now, and I think we have the codebase in a place where it's ready for localization.

Message documentation:

Since this project is a Django app, which has some nice tooling around gnu gettext, we decided to bake our message documentation into our code comments and let gettext add it to the qqq po file. https://github.com/WikipediaLibrary/TWLight/blob/master/locale/qqq/LC_MESSAGES/django.po

Adding new message translations:

In addition to adding new translation files, the universe of available languages in the user preferences should be expanded by updating the LANGUAGES variable in our base settings. https://github.com/WikipediaLibrary/TWLight/blob/master/TWLight/settings/base.py A nightly build script pulls the latest changes from master and applies them so long as the changes don't fail the unit tests.

Limitations:

This app has content that lives in the database. That content is comprised of fairly large blobs of text that are not visible to Translatewiki via the code repo. We're on the hook for translation of that content, but I don't really see a good way around that. We do have some folks internal to our project willing and able to expand translation for that content. That's how we got the Finnish and French that we currently have in place.

11:32, 1 November 2017

You need more space for the login button. Finnish text is truncated.

> In addition to adding new translation files, the universe of available languages in the user preferences should be expanded by updating the LANGUAGES

Can you do that? We have no support for such automation (nor even manual process) right now.

Please consider using https://github.com/wikimedia/jquery.uls for language selection, or at least take the language names from https://github.com/wikimedia/language-data or CLDR. We don't want language names translated here again and again for different projects.

11:59, 1 November 2017
 

Also, is there a reason you are using the non-standard code iw for Hebrew instead of the standard one he?

10:33, 2 November 2017

No idea why iw code was chosen, but I can see that there are no actual message strings for that translation file, so I just removed that one. I fixed the login button as well.

On the way we're doing language selection: We start out by using the language requested by the browser. We record a detected language for authenticated users on first login. Users may manually set their language on their preferences page as well. We use the recorded value for interaction not tied to a browser session (emails). We're relying heavily on Django's i18n features for all of this to just work behind the scenes. Integrating the jquery library might be a difficult fit for this project, as our community expects to be able to use the site without javascript. Having said that, this looks much, much more usable than having a selection list with a ton of items in it. The current ui works for 3 languages, but I could see it getting user-hostile with 100. I'll see how feasible it is to use this when we have javascript, and use the plain form when we don't.

11:29, 3 November 2017
 
 

Support for Kumyk

Hi everyone!

Would like to request support for Kumyk language.

Portal link: https://translatewiki.net/wiki/Portal:Kum

Looking forward to your reply

Thanks

00:11, 15 September 2017
Edited by another user.
Last edit: 19:31, 18 September 2017

I am supporting this request. This user is one from active participants of test Kumyk Wikipedia in the incubator:.

11:41, 15 September 2017
 
Edited by another user.
Last edit: 19:30, 18 September 2017

I am supporting this request.

18:13, 16 September 2017
 

Fallback to Russian? English? Or others?

04:31, 17 September 2017

Could you please specify what fallback means within Wikipedia? Or link me to the info? Thanks a lot

Got it.

Fallback to Russian, next to English. Thanks

19:30, 18 September 2017

hey guys! any updates on this request? thanks

21:30, 3 October 2017

User:Liuxinyu970226, hi! any updates on this request?

09:44, 3 November 2017
 
 
 
 

How to replace wrongly translated spelling of a word appearing in language list for language code anp

It is observed that Angika translation of Angika (Code - anp) is being shown in the language list as अङ्गिका . The same should be written as अंगिका .

I am not getting the right link as to where the spelling can be corrected.

Show me the method to replace wrongly translated spelling of a word appearing in language list. Else change the same from अङ्गिका to अंगिका .

03:12, 1 November 2017

Have you already searched the word in Special:SearchTranslations?

07:43, 1 November 2017

Yes, I have searched the word, अङ्गिका and the same was not found in search results.

You may be interested in viewing the previous activities for the same issue;

https://translatewiki.net/wiki/Thread:User_talk:Siebrand/Unable_to_edit_anp_messages#Unable_to_edit_anp_messages_6811

https://translatewiki.net/wiki/Thread:Project:Translator/_anp_Angika_–_anp#x.7B.7BLanguageHeader.7Canp.7D.7D_6810

10:24, 1 November 2017

Can you specify which language list are you talking about?

12:03, 1 November 2017

Everywhere in Default Language Lists of Suggested Languages on Translatewiki.net, MediaWiki, Wikipedia Incubator and all other sister projects of Angika (anp) in Incubator.

File-1
File-2
File-3
File-4
File-5
File-6
File-7
20:50, 1 November 2017
 
 
 
 

Wikimedia:Xtools-edits/sr

Could someone delete/empty this page? It is probably primary for Xtools; Wikimedia:Xtools-edits/sr-ec should be used (capitalized), and here it is non-capitalized and editing /sr is not possible becuase we got transferred to sr-ec (and sr-el).

There is some problem with saving posts here, so it is saved twice. And it constantly keeps asking Do you want to leave this site, Changes you made may not be saved...

23:25, 15 October 2017

The session issue should be fixed now.

12:04, 1 November 2017
 

See to what languages my project has been translated

How to see a list of languages my project has been translated to, with percentages of completion?

Example:

  • English 100%
  • Hindi 99%
  • Punjabi 99%
  • German 98%
  • [...]
  • Swahili 1%

All other crowd translation platforms have this feature, so I guess there is something like this here too, but I haven't managed to find it. Thanks!

09:18, 29 October 2017

Special:MessageGroupStats, which is also accessible from Special:Translate tabs and linked from e.g. Translating:WikimediaMobile.

09:27, 29 October 2017

Cool, thanks!

10:25, 29 October 2017
 
 
First page
First page
Previous page
Previous page
Last page
Last page