The reason this is not trivial is two-fold: 1) caching and b) the semantics of URLs. Serving different content from the same URL is generally a bad thing.
A soltuion for this is dicussed in <https://phabricator.wikimedia.org/T114662>, but work on this is currently not resourced. Am 25.01.19 um 11:44 schrieb Darren Cook:> I wanted to send someone a URL to show them how a data item looks in > Japanese (so we could see which items have a translation). But am I > right in thinking there is nothing I can put in the URL to do this? > > I also tried changing my accept-language header to put "ja" first, but > it is ignored. Was this a feature that was discussed and rejected; or > just an itch that no-one has got around to scratching yet? > > Darren > > P.S. I realize I can login, change my UI to another language, and see > the data that way. But that is quite a long-winded process, especially > if the person has not created an account yet. > > It also changes the whole UI, not just the data, which is painful if I > just want to see what has been translated but cannot read the language. > I think for a project about data, you should be able to set the UI > language and the content language separately. > > E.g. I just put a page into Greek (I think), and now I can see the few > items that have been translated, but cannot read the property names! Let > alone navigate the site.) (The switch back to previous language link at > the top was a great idea, though - thank-you to whoever thought of that > shortcut.) > > > _______________________________________________ > Wikidata mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata > -- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation _______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
