All other uses seem to be translated, but maps.wikimedia.org is not.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T43307 Alow comparison with old revisions while editing an old version of a page | |||
| Resolved | TheDJ | T70008 PDF-related improvements needed at Wikivoyage, especially for dynamic maps | |||
| Declined | Feature | None | T64572 Media Viewer and location map overlays | ||
| Resolved | Etonkovidova | T52714 VisualEditor: Location map template does not display correctly | |||
| Declined | None | T32702 PDF export extension problem with <div style="position:> and any location templates | |||
| Declined | None | T92535 Exclude {{location map}} images from PageImages | |||
| Duplicate | None | T169507 Fix vector map visualisations once the user clicks them on an article (red dot and label missing) | |||
| Resolved | TheDJ | T120809 Generate location maps dynamically, producing actual images | |||
| Resolved | SBisson | T112948 All map location names should be in the user's language | |||
| Declined | None | T187288 maps.wikimedia.org copyright attribution should be translated |
Event Timeline
Comment Actions
maps.wm.o is here only for basic testing of tiles. It has never been intended for end users to see at all and can be replaced with a single HTML page somewhere in labs if it causes any problems. Recommend not wasting time on this.
Comment Actions
I wouldn't consider this a priority, as it's a debugging/demo page.
On the other hand, we're going to need a debugging/demo page where we can switch the language of map that is being requested, and we might as well translate the attribution text at the same time.
Comment Actions
This would mean adding jQuery.i18n to the /server repo along with the i18n files and then connecting them to translatewiki.org
It's not insane work, but it does make things more complex, so if maps.wikimedia.org is strictly testing, then we might not need it. We can still test i18n on maps inside the wikis, and the label languages will be affected/changed regardless of the attribution, and don't need jQuery.i18n.
Do we still want to do and prioritize this task?
Comment Actions
This task was not in the previous maps backlog and not coming from the community wish list. I don't know why it was even created. I vote for "declined".