Drop-down menus not translated

[Mashin6]

Items in several drop-down menus are not translated to localized version. Tested on Chrome 28, iD 1.1.4 (but affected were also older versions) with Slovak localization.

Untranslated appear:

• yes/no in oneway
• yes/no/... in access
• asphalt/pawed/... in surface
• parking isle/....

Also pre-filed help strings in those fields are in english only.

[tmcw]

Hm - can you point to the menus specifically by where they are located in the UI? The Slovak translation is 100% complete, so there should be no untranslated strings in the interface.

That said, the tag editor, and the values of tags in OpenStreetMap, are not translated on purpose. They are literal values are not translated in the data, and we cannot translate all combinations. These values come from taginfo rather from iD itself.

[Mashin6]

The one I mentioned were when tagging line as: Road > Service >
Affected are fields: Type, Surface, Oneway

Also Area > Parking > Type

Area > Building > Building: shows yes

[Mashin6]

Road > Service > Access > all subfields are affected e.g General, Foot, Bicycle,...

All those I mentioned here affect other Road features as well...

[Mashin6]

point > hospital > Emergency: shows english yes

Point > place of worship > religion and denomiantion

Point > Cafe > Cuisine and internet access

There seems to be a lot of those fields with untranslated strings. Since nobody so far reported this problem I assume that it is language specific or maybe system specific?

I have OS X 10.8.4 and affected is both chrome and opera.

[tmcw]

Yes, this is what I'm referring to in

That said, the tag editor, and the values of tags in OpenStreetMap, are not translated on purpose.

The values of actual tags in OpenStreetMap are not translated in iD because they are not translated in OSM.

[Mashin6]

OK. But couldn't be those tags translated on UI-level, but kept as original for OSM upload?
Object names (e.g. service road) are tags as well, yet they are translated.
Having half of the UI translated and half not kind of defies the whole purpose of translation.

My suggestion would be to translate all tags in drop-down menus and the actual values could be then viewed under "all tags".

[Debeet]

That said, the tag editor, and the values of tags in OpenStreetMap, are not translated on purpose.

But hints for these tags are translated (see: access), no? So you can't translate tags but you can translate hints for these tags.

[bhousel]

If a field provides strings to choose from (and the access radio field is an example of this), they can be translated. But the "combo" dropdown fields and the raw tag editor populate themselves based on actual data from taginfo, so you will just see the most frequently used values here, not translations.

[bhousel]

To anyone following this issue, see #2296 for discussion, some combo fields are translatable now.