In T240196#5910192, @schoenbaechler wrote:

@Amire80, how about the comment below? Thx.

06)
@Amire80, Would it be possible for you to download the latest Android Alpha and check if the two issues that you found last time (see below) are fixed now? 👇

• Invert swipe gestures/animation and functionality of “Next" and “Previous” buttons in RTL. They currently feel odd/wrong in RTL.
• Center text in tags if word is short. They’re oddly aligned to the right if word’s too short (RTL).

I started a discussion in the Langcom about this.

In T240196#5905840, @Dbrant wrote:

05) Strangely, Amir gets a mix of languages in the suggested tags, e.g. 7 of the tags are in Hebrew one is in Russian, has happened multiple times in different combinations. Mentions that the Russian tags use very weird language.
07) Not all languages are probably supported by Google Cloud Vision AI, suggests to test it with a language that is not supported by Google Cloud Vision AI and see what happens.

The Google Vision API actually gives us Wikidata items (Q1234), and then we get the "label" for each item from Wikidata. Therefore the quality and/or correctness of the labels simply depends on what's currently in Wikidata for that item. It's possible that someone entered a Russian label in the field for the Hebrew language.

Thanks. I added a few trivial improvements to the messages themselves.

Just change the English. Translators will notice the change and update the translations.

In T240194#5876854, @schoenbaechler wrote:

Adding cryptic notes from my conversation with @Amire80 this morning. Will process them soon. Also, feel free to just drop screenshots here @Amire80. Thanks so much for your time, looking forward to our next session!
Amir uses a Samsung Galaxy S7 and Android version 8.0.0
Onboarding
W icon looks correctly in the status bar!

This is implemented in the latest monthly reports. Somewhat manual, but good as a start. Feedback is welcome.

Notice: https://bs.wikipedia.org/w/index.php?title=Wikipedia%3A%C4%8Car%C5%A1ija%2FTehnika&type=revision&diff=3149514&oldid=3086064

Notice: https://mk.wikipedia.org/w/index.php?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0:%D0%A1%D0%B5%D0%BB%D1%81%D0%BA%D0%B0_%D1%87%D0%B5%D1%88%D0%BC%D0%B0&diff=prev&oldid=3926166

In T243931#5840429, @Anomie wrote:

According to @daniel, this can be done without making a full implementation of general change propagation and dependency engine mechanisms

Lacking that would mean edits to the "global" module wouldn't propagate to the local wikis. That seems like something that would quickly be reported as a bug.

In T239823#5840312, @SBisson wrote:

1. Fully, or mostly, translated on TWN. [1]

Makes sense, but it's a really easy thing to achieve. The project doesn't have a lot of strings now, and most of the strings are very easy technically, so it's not supposed to take a long time to translate everything. For someone who can write in the language, a couple of hours is enough, including coffee breaks :)
It's also possible in translatewiki to encourage translations only to some languages. For example, if you know that you are never going to market the app to Italian speakers, you can discourage translation into it.

Is there a way to reach out to users or groups on TWN and solicit translations for some languages?

In T239823#5838859, @SBisson wrote:

One of the next steps here is to decide which languages we allow to search and to read articles.
Until we can support all languages, if ever, I propose we start a whitelist of languages that respect the following

1. Input method works on the device. It is possible to type search terms in this language using the device keyboard.
2. Display of article works well enough. Acceptable fonts available.

I had a quick conversation with @daniel about this. This is the closest thing I could find to a Phab task for implementing the Dependency engine :)

First of all, I really appreciate the effort to harmonize the names across different wikis. Thanks for starting this.

It's indeed quite possible that it't intended, but it shouldn't be :)

And what are the languages for which it's possible to use real codes? Languages in Names.php? Something else?

I confirm. I saw it myself, and heard complaints from multiple people.

... Maybe, as a workaround until this is properly fixed in Blink, these wikis can define a font other than Georgia for their heading in Common.css?

In T243119#5818547, @matmarex wrote:

I found the relevant upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=673095 (filed by our own @Amire80 :) …in December 2016).

In T243119#5816472, @kruusamagi wrote:

Just for it to be clear: Udmurt and Komi (and probably some other languages as well) use this letter. But if I copy it to Estonian Wikipedia [use it there], then it gives me the same messed up result. I.e. it doesn't depend on what Wikipedia version it is. In some computers it doesn't show the letter right.

Here, as in T103066, I'd say that the really right solution is having better semantics in the text, and this is outside the scope of CX.

I've tried to reproduce, and here's what happens:

I agree with declining, but I'd add a slightly different rationale: It should be done, but not by Content Translation. Content Translation should be responsible for adapting only the most obvious and least ambiguous things, like links and images. Template adaptation is very non-obvious, and it is done by Content Translation, but that, too, should be refactored (see T243150 for an initial proposal).

Thanks. I don't see this problem on MacOS. This may be a problem with Windows. Does this happen in all browsers on Windows—Firefox, Internet Explorer, Edge? Does this work better on other websites?

In T238411#5814642, @eranroz wrote:

Partially related patch (5 years old):
https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Scribunto/+/158323/
proposed to move Module:Arguments from enwiki to MediaWiki and adding translation capabilities to getArgs

On which browser does it happen?

This is an extreme setting. No other wiki has such huge numbers.

Thanks for the clarification! I updated the documentation.

Maybe I'm missing something, but I cannot actually select the current year in the form. It's 2020 now, and it's grayed out:

In T222867#5797824, @AnneT wrote:

I'd like to wrap this one up and after reading the comments it seems we can move forward with the following UI in RTL language mode:

@Amire80, can you please confirm that this is correct? If so, and if no one else has feedback, I'll move forward on this. Thanks!

I've just reproduced this by translating the article GAZelle from English to Hebrew: https://he.wikipedia.org/w/index.php?title=%D7%9E%D7%A9%D7%AA%D7%9E%D7%A9:Amire80/%D7%92%D7%90%22%D7%96%D7%90%D7%9C&oldid=27056000

This happened today in the Hebrew Wikipedia.

Is this just the branch cutting, which usually happens on Tuesdays? Or does it also affect the time of the actual deployment?

Yeah, possibly related, but I'm not sure it's the same.

I'm working on integrating it with the Language team monthly reports.

Thanks for the explanation. As I noted in the description, I wasn't sure whether the truncating of the link before <ref> happens in VE or in Parsoid. I'm pretty sure that it happens somewhere.