Page MenuHomePhabricator

[MEX] M3.1.2 - Left-to-right languages are supported
Closed, ResolvedPublic

Description

As a wikidata editor
I want my interface to be in the language I select while editing on mobile
So that I can feel confident while editing

A/C

  • left-to-right displayed languages match the figma file
  • the mobile version matches the desktop version in terms of which languages are supported
  • users can switch languages by using the "language" button on the home page of wikidata
  • unit tests are created/updated

Notes:

  • To change interface language on mobile, you must go to the home page, scroll to the bottom and tap "Language", then select a new language. This matches the functionality on wikipedia
    • (!) When language is changed on wikidata.beta.wmcloud.org, you are redirected to wikipedia's homepage
  • right-to-left designs are not yet completed (2025-aug-27) but will be handled in T403013: [MEX] M3 - Right-to-left languages are supported

Event Timeline

karapayneWMDE renamed this task from [MEX] M3.1.2 - Multiple languages are supported to [MEX] M3.1.2 - Left-to-right languages are supported.Aug 27 2025, 9:26 AM
karapayneWMDE updated the task description. (Show Details)

Change #1183631 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Use wikibase-edit message for edit link

https://gerrit.wikimedia.org/r/1183631

Change #1183651 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Use messages for edit statement dialog

https://gerrit.wikimedia.org/r/1183651

Question (probably for @Alice.moutinho or @Arian_Bozorg): Does the input field for the statement value (T402447) have a placeholder, and if yes, what is it? The current dialog has “add property value here”, but I feel like that’s probably just something Arthur made up for the prototype, because I don’t see it in Figma anywhere – and I don’t see an empty input field in any of the dev-ready components (they all have a value already filled in AFAICT).

And can you confirm that the “edit statement” (or “add statement”) heading is part of the intended UI and we should define a translatable message for it?

Should be ready for review apart from the two messages mentioned above.

@LucasWerkmeister Hi Lucas, just user the same copy we have on desktop - here and anywhere else where there is copy and there are doubts. Edit statement and add statement are part of the UI. (ps. i was never here )

Change #1183631 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Use wikibase-edit message for edit link

https://gerrit.wikimedia.org/r/1183631

Actually, about that “edit statement” heading… are we sure about that? Because I just realized it’s really perpetuating the same misunderstanding as in T403184. You’re editing more than one statement (in internal terminology, a statement group) – in this screenshot, “singer” and “songwriter” are separate “occupation” statements:

image.png (780×290 px, 35 KB)

I would probably phrase this example as something like “edit occupation(s)” – but there’s no way we can make anything like that work for thousands of properties across hundreds of languages… but I think “edit statements” would at least be more correct than “edit statement”?

The desktop UI uses very similar terminology, but I think it’s at least a bit closer to being technically correct. The button (link) at the bottom says “add statement”, but that’s correct because it really only lets you add one statement for the selected property – you can’t add a second statement until you’ve saved the first one. I would say that the “add value” button/link really adds another statement, but calling it “value” isn’t really wrong here I guess. And there’s no heading or button for editing the whole statement group at once. (I don’t think the desktop UI uses the term “statement group” anywhere, except in a handful of message keys that ordinary users never see. In Lua we speak of the “statements” of an entity + property.).

Change #1184047 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Remove placeholder from statement value input

https://gerrit.wikimedia.org/r/1184047

Change #1184048 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Respect $wgEditSubmitButtonLabelPublish

https://gerrit.wikimedia.org/r/1184048

Change #1184083 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Refactor editStatementGroup Jest tests

https://gerrit.wikimedia.org/r/1184083

Change #1183651 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Use messages for edit statement dialog

https://gerrit.wikimedia.org/r/1183651

Change #1184047 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Remove placeholder from statement value input

https://gerrit.wikimedia.org/r/1184047

Change #1184083 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Refactor editStatementGroup Jest tests

https://gerrit.wikimedia.org/r/1184083

Change #1184048 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Respect $wgEditSubmitButtonLabelPublish

https://gerrit.wikimedia.org/r/1184048

I think this is done except for the “edit statement” heading (T402630#11138088), which is waiting for feedback from Product / UX. Not sure which column would be best for this task in the meantime…

Yeah - it's basically done. Let's leave it here for today. Latest tomorrow at standup I will try and get clarification from @Arian_Bozorg and we can decide what to do with it.

Sorry, let's leave it as is for now and I will look at it with Alice as we move into the refinement stages of the project

Hi @LucasWerkmeister,

I see your point. Thank you for clearing that up. I thought the statement was "occupation" and singer and songwriter where ... sub-statements? because of the way the prototype i have been reworking was set up:

Screenshot 2025-09-08 at 09.02.43.png (678×732 px, 61 KB)

But if sometimes one block is more than one statement, then the title is indeed misleading.

Is it possible to differentiate between blocks with only one statement (that does occur, or?) and blocks with multiple statements? so that we could have singular "edit statement" when it is one, and plural "edit statements" if its several? like this we would be always correct!

If this is not possible, then we should go with plural as you suggested.

Is it possible to differentiate between blocks with only one statement (that does occur, or?) and blocks with multiple statements? so that we could have singular "edit statement" when it is one, and plural "edit statements" if its several? like this we would be always correct!

It’s always technically possible to have more than one statement with the same property (though it can be discouraged via constraints, or encouraged for that matter).

We could make the heading depend on the number of statements (“edit {{PLURAL:$1|statement|statements}}”) – show “edit statement” when adding a new statement or editing a statement group with just one statement, and change it to “edit statements” if the statement group has multiple statements or the user starts to add another statement.

That sounds like a simple and elegant solution to this

Change #1187446 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):

[mediawiki/extensions/Wikibase@master] Add message for edit statement dialog header

https://gerrit.wikimedia.org/r/1187446

Change #1187446 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Add message for edit statement dialog header

https://gerrit.wikimedia.org/r/1187446