VSS Language code - sufficient or improvement needed?

[erikbosch]

In Infotainment.vspec we have:

HMI.CurrentLanguage:
  datatype: string
  type: sensor
  description: ISO 639-1 standard language code for the current HMI

But ISO 639-1 does not consider regional differences, there is only 1 "English" - en.
Do we see a need to extend this to also cover country specific variations, like allowing en_GB and en_US where the [_XX] part potentially could be optional and would come from https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

Or is it unusual for a vehicle to support multiple variants of english or any other language? I.e. no need to specify?

And if we support <language>_<country>, do we want arbitrary combinations to be allowed, or is there some good standard? As an example Android list just a subset, you cannot for instance specify that you use sv_FI (Swedish as spoken in Finland, which has some minor differences compared to sv_SE, and those differences are likely not relevant for a vehicle).

Two side discussions:

• Would we like the signal to be an actuator instead, so we can set language?
• Do we see a value in an HMI.AvailableLanguages signal (attribute, string array)

[erikbosch]

Meeting notes: Please comment

[erikbosch]

There seems be no interest/need for change, so closing this issue