Which language should we advertise in maps ZIMs?

[benoit74]

Maps will have a mix of English and local language/alphabet:

Which language should we:

• put in ZIM name (for filename and ZIM Name metadata)?
• put in ZIM Language metadata

Is this a rare edge-case where using mul in both places would make more sense?

@rgaudin @kelson42 I really need you help on this one ... not an easy choice.

[kelson42]

Can we not have all languages in the ZIM... and display, on demand, one of them?

Otherwise, please take the English first approach, and we should have an issue here to improve this later.

[benoit74]

Can we not have all languages in the ZIM... and display, on demand, one of them?

Maybe, I don't know, I don't see how it answers the issue of which language we should advertise in ZIM Name and ZIM Language

Otherwise, please take the English first approach, and we should have an issue here to improve this later.

What does it means? Use eng in ZIM Name and advertise only eng in ZIM Language metadata?

[rgaudin]

in OSM, every name is a local language one and then there are available translations. The original name, we can consider it language-less.

In your dataset, are you specifying each translation you want? From your text “a mix of English and local language” I understand that either you only selected EN or only EN was provided along.

If this is only applying to the tiles, then I think we can also consider it language-less and use the EN versions as latin-readable alternative.

If it is used in queries and I can search for Москва and Moscow but not Moscou then it's an eng IMO.
But as this suggests, I think the ZIM(s) should be coded based on the UI and the data it interacts with.

[benoit74]

In your dataset, are you specifying each translation you want?

Nope. I used the dataset "as-is".

I've dived a bit in the issue and in fact all this comes from the styles which uses configuration like below for all labels:

        "text-field": [
          "case",
          ["has", "name:nonlatin"],
          ["concat", ["get", "name:latin"], "\n", ["get", "name:nonlatin"]],
          ["coalesce", ["get", "name_en"], ["get", "name"]]
        ],

Looking at a specific specific feature of a specific tile of Corsica, I have this data:

            "properties": {
                "name": "Parc naturel r\u00e9gional de Corse",
                "name_int": "Regional Natural Park of Corsica",
                "class": "parc_naturel_r\u00e9gional",
                "name:latin": "Parc naturel r\u00e9gional de Corse",
                "name_de": "Regionaler Naturpark Korsika",
                "name_en": "Regional Natural Park of Corsica"
            }

This seems to indicate that we could switch language directly from the UI, even if conditions are so diverse that I'm not sure it is going to be easy to define a rule better than current one "for the whole world".

I propose that for v0.1 we stay with current labels.

Which brings back to original question. Since name:latin has priority over name_en when name:nonlatin exists (meaning default alphabet for the location is not in a latin alphabet), we do not really have something like a ZIM language to advertise.

[rgaudin]

Which brings back to original question

Is there no UI at all ?

[benoit74]

Mostly no UI besides the map.
Currently we only have a dropdown with styles name (in English, especially tooltips).
And two buttons (with tooltips in English again, indeed)
Maybe a +/- button might be introduced at some point.
And I indeed plan to have an about page, which will be in English again.

Is that sufficient to say that the ZIM is in English? I'm fine with this idea.

[rgaudin]

With the principle that there is less confusion and frustration in not being presented a new ZIM rather than being presented something for a language that it is not (or doesn't appear to be), then I'd say this first version is ENG.