I think it should be done now. Can you check please?

Any improvement that automates the procedure at https://wikitech.wikimedia.org/wiki/Add_a_wiki is a good step in the direction of implementing this. As the beginning of this task's description says, this task is a version of T158730 that addresses the user-facing aspects of creating new empty wikis, mostly in underresourced "small" languages (they are small only in their presence on the web, but some of them have millions of speakers).

I'm really not much of a Java or Android coder, but as far as I can see, the relevant code is this:

This is definitely not a Content Translation issue, and probably not a translatewiki issue either.

In problem #1 both screenshots look broken in different ways :)

OK, now I've looked at the code properly and I see formatDuration. It's kind of like a simplified Moment.js, for PHP. Like Moment.js, it's good for standalone expressions, but not necessarily for embedding in sentences.

The initial task description applies also to Russian and probably most other Slavic languages.

It will be a very nice bonus if you can write a little user manual for it at this URL:

It's good. Thanks a lot for your work, @zypA13510.

This happens because the Unicode bidi algorithm tries to re-arrange numbers and letters from different alphabets and cannot guess the user's intention correctly. This is especially common on MediaWiki sites with page titles, usernames, and IP addresses.

Not immediately, but some time very soon I'll merge this with the ULS extension, and then it can be resolved.

Great, thank you!

What I'm trying to say is that in the pageviews tool there is now a topviews tool that shows data per language, and there should also be a topviews tool that shows data per countries, and if it's not perfect for data per languages, it will be just as imperfect for data per countries. So not having a very good spam filter doesn't sound like a blocker. It's better to have something imperfect that not to having anything at all.

In T207171#5056374, @Nuria wrote:

Is this also an issue for the topviews that are shown per language?

Yes, it is an issue with any top list. Now, topviews has a "spam" list so titles that are known to be spammy traffic are removed. Those are reported by users and while list is great to have it just removes the major offenders.

In T207171#5056278, @Nuria wrote:

This work needs the bot filtering be active first, otherwise you would just get "fake" top10 lists per country as much of the data will be distorted by bot traffic.

This is supposed to be fixed in https://gerrit.wikimedia.org/r/#/c/analytics/limn-language-data/+/498981/ , which is waiting for a rerun at the moment.

We checked the query, and it's already done in the current dashboard. I updated the title to clarify this

My bad, sorry about that. I somehow thought that it's outdated.

Thanks for the update!

Somewhat related: T207171: Have a way to show the most popular pages per country.

In T217510#5020304, @Pginer-WMF wrote:

I think that the text input cursor conveys a strong expectation for allowing input, which is potentially confusing here.

I reported a few CLDR issues, and some of them were resolved, but I can't say I'm exceptionally good at getting them to resolve my issues or at adding new languages. I think that @Nemo_bis may be more experienced in this particular area, however.

Well... it's definitely weird when it's seen as a blinking thing.

In T197075#4995003, @Etonkovidova wrote:

Presently it's not possible to add just a link from a source article to a target article. It's added only when the whole paragraph with link(s) is translated.

I split it into a numbered list:
(1) When selecting a link from the source document, a link card will be shown
(2) The card will include as the main piece of information the corresponding article on the target wiki

Detailed report: https://www.mediawiki.org/wiki/Content_translation/Created_pages_comparison

Briefly, here are the results for these languages:

A font for Santali is supposed to be installed on the server where the SVG is rendered. @ASHWANI gave several examples of fonts that would work for Santali.

In T217122#4984048, @Schnark wrote:

That would prevent local communities from changing this to a page in a different namespace, e.g. "Help". Especially, in de.wikipedia, this indeed is the case: https://de.wikipedia.org/wiki/MediaWiki:Visualeditor-descriptionpagelink

Somewhat related: T72159: Forward according to user's preferred language on Special:GoToLinkedPage.

In T72159#2440343, @Legoktm wrote:

My usecase is that I'd like to give people a language-neutral link instead of just linking to en.wp.

I propose making the URL routing for the special page like:

• Special:GoToLinkedPage/enwiki/Q42: current, when you know the site
• Special:GoToLinkedPage/Q42 : auto-detect language, if there are multiple sites with that language code (e.g. en.wp, en.voy), go to the item
• Special:GoToLinkedPage/Q42?project=wikipedia: auto-detect language, but only look at sites in that project group.
  
  In all cases we'd apply the normal MW language fallback chain. If we still can't find a matching sitelink, go to the item.

Results: https://www.mediawiki.org/wiki/Content_translation/Deletion_statistics_comparison

I can reproduce it in mediawiki.org:

Update: A basic Superset dashboard is set up, but to make it more useful, there should probably be a meeting between myself, @Pginer-WMF and @mforns to discuss the details of how does it look like.

Where does it happen that it shows as "undefined"? I do see it as one of the valid languages in translatewiki. (Although, as others have said, it should probably be renamed.)

Nice effort.

In T210273#4938271, @Tchanders wrote:

In T210273#4938269, @Amire80 wrote:

In T210273#4938231, @Tchanders wrote:

I wasn't sure about lengthening the "OK" message on the blue button, given the narrow width of the screen and possible longer translations in other languages. Perhaps @Amire80 has a opinion?

Thanks a lot for asking!

No, I don't see a problem here at the moment. OK is a common button on all platforms and it has standard translations in many languages, e.g. here.

If there will be a problem, the translators will complain ;)

Thanks @Amire80 - sorry I wasn't clear with my question! The button currently says "OK" but there is a suggestion to change it to "Got it" - I'm worried that the translation of "Got it" might be too long in other languages?

In T210273#4938231, @Tchanders wrote:

I wasn't sure about lengthening the "OK" message on the blue button, given the narrow width of the screen and possible longer translations in other languages. Perhaps @Amire80 has a opinion?

In T214781#4937717, @schoenbaechler wrote:

@Amire80: Are you referring to the “Translate title descriptions“ screen? 👇

In T214786#4937786, @schoenbaechler wrote:

Is this more related to an id/class the app’s architecture which isn’t visually outputted? Thanks for clarifying @Sharvaniharan or @Amire80.

Nothing much more except comments about references and templates.

In T131013#4929585, @alexhollender wrote:

@Amire80

So in other words, what Wikipedia wants (in Latin languages) is inconsistent with what Wikidata recommends.

Sorry if it was already mentioned and I missed it, but where is it written that Wikipedias in the Latin alphabet want this?

My apologies for not explaining this statement. The design recommendation is for consistency, specifically capitalization (as stated in the comments).

So in other words, what Wikipedia wants (in Latin languages) is inconsistent with what Wikidata recommends.

In T131013#4928746, @Jdlrobson wrote:

The question remains: Do we want to keep capitalisation on languages where it is useful e.g. Deutsch, English, francais.
I'd argue no as it creates tech debt and confusion, but let's make a decision promptly.

In T214534#4920839, @Pols12 wrote:

Is it possible it is related to T154329? I often switch tab, then, coming back to wiki tab, VE fails to load.

@Amire80 do you switch between browser tabs too, when VisualEditor is loading?