Yurik added a comment.
Another possible use case: multiple sitelinks to the same site. For example, Wikidata may have a project page for postal codes in English, and someone wants a similar page in German. But the community does not want direct translation, because English page may want to cover
Marsupium added a comment.
Perhaps the set problem could be solved with qualifiers, too.TASK DETAILhttps://phabricator.wikimedia.org/T86517EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: MarsupiumCc: Marsupium, Bugreporter, Esc3300, Susannaanas, Laddo,
Esc3300 added a comment.
I agree about P1922 and P1843.
P2559 (Wikidata usage instructions) seems to be mainly a GUI problem with descriptions. I suppose that could be solved with a new datatype.
Not sure about P2275.TASK DETAILhttps://phabricator.wikimedia.org/T86517EMAIL
Bugreporter added a comment.
Clearly yes, if we have two sets of monolingual strings in different languages, we should want to know which set a individual string belongs to.
Multilingual text should be used if:
Texts in different languages are translation each other, and only one and any one is
Esc3300 added a comment.
Is there still a point in having this? We could merely improve display of various languages for properties with multiple monolingual strings.TASK DETAILhttps://phabricator.wikimedia.org/T86517EMAIL
