Opened 8 years ago

Last modified 7 years ago

#12179 new enhancement

maps (trans_maps.java) needs a context field to guide translation — at Initial Version

Reported by: holgermappt Owned by: team
Priority: normal Milestone:
Component: Core imagery Version:
Keywords: i18n Cc:

Description

The list of TMS/WMS/WMTS sources, https://josm.openstreetmap.de/wiki/Maps and https://josm.openstreetmap.de/maps, contains a lot of names with acronyms and names in languages other than English. Examples:

  • OSMIE EDs
  • LPI NSW Base Map
  • Powiat łańcucki: Budynki (buildings)
  • Vercors - Réserve naturelle des Hauts-Plateaux du Vercors - Orthophotos 1999 - 1 m

Those strings make their way into Launchpad for translation. But a translation requires more context if acronyms are used and an English translation for strings in other languages. What is missing is a context field for the entry <name> in the imagery definition XML. The context can write out acronyms or have an English translation. That context field is then added to trans_maps.java by convmaps.pl. The name could be <name-context>.

Or should acronyms be discouraged and be written out in the XML? In my opinion most acronyms make sense only to the one who adds a layer entry. Or in the region that is covered with the layer. But the usage and translation is world wide.

An other question is what should happen with entries that have something like this:

<entry>
  <name>Buildings</name>
  <name lang="de">Gebäude</name>
  ...
</entry>

The German translation will be lost in the current setup. Should it be added to the context too?

Change History (0)

Note: See TracTickets for help on using tickets.