Fri, Jan 18
Yes. This is currently a rather low-priority task, and will be handled at a later time.
Thu, Jan 17
Excellent! Some light commentary to kick things off:
Closing as non-reproduceable.
Tue, Jan 15
Can you please clarify the exact steps to reproduce the issue? Where are these article sections that you are clicking? Which article are you reading? What actually happens when you click?
Mon, Jan 14
Closing as unreproduceable.
Fri, Jan 11
The number of description edits made from the app is currently on the order of ~500 per day.
Here is what we would like to receive, ideally, in these API responses:
Thu, Jan 10
This is an interesting issue, but it will not be easy or practical to solve. Here is some information about what's happening here:
Wed, Jan 9
Tue, Jan 8
@Sharvaniharan This still seems to be missing the functionality seen in the first three "mock" images. Will you take care of them?
Mon, Jan 7
Thu, Jan 3
The Commons App is maintained on GitHub (and not by WMF):
Wed, Jan 2
Do we know what the offending string is so we can fix it at translatewiki?
This is done (both locally and on twn)
it would be good that, instead of having to recheck each time an l10n-update patch is uploaded, that jenkins could just run the checks but not merge. It can save a lot of time.
That would be great, and that's how it worked before, but for some reason it was disabled by someone, and I'm not sure how to re-enable it.
Thanks, OK then, it looks like we'll need to make a separate call to the meta=siteinfo API to get the language code, since we can't rely on the subdomain or the sitematrix code.
This is because a poorly-translated string is causing one of our unit tests to fail. This is a regular occurrence, and is fixed by tweaking the offending string and re-syncing with TWN.
This person appears to be using a custom operating system ("FlymeOS?"), and a "beta" version of the operating system, no less. We can't possibly test, much less support, such edge cases.
...But the Alemannic Wikipedia actually exists under the subdomain https://als.wikipedia.org, and the database name of the wiki is alswiki, therefore the app treats the language code as als. How should it know that it should convert it to gsw? Is there a list of other language codes that are treated differently on Wikidata versus Wikipedia?
We no longer support versions of Android older than Kitkat (4.4). This has been true for over a year, but unfortunately the FAQ was out of date (I've just updated it).
Description must be no more than 250 characters long
Where does this appear in the app?
Dec 17 2018
Dec 12 2018
Hard-coded punctuation is fixed, and the TWN strings will be updated upon the next sync.
Dec 11 2018
Dec 10 2018
@cmadeo A very general design question stemming from this task:
In your mock, the negative dialog button ("Maybe Later") is in a different color than the positive button. The standard behavior is for both buttons to be the same color.
We can potentially override this color, but then the question becomes: do we want this style to apply to *all* dialogs in the app, for the sake of consistency? (This would also be the simpler way to go, as long as we're already making customizations.) Or do we want to leave the buttons with the standard (uniform) color?