Updating Gallo names to use a standard key

About 300 elements are currently tagged with the name in Gallo, mostly in the Brittany region of France. When these names first appeared around 2017, there was no standard language code for Gallo, so it was common to use a private extension, name:fr-x-gallo=*, consistent with the BCP 47 standard. In 2021, fr-gallo was registered as an official subtag, making it possible to avoid a private extension.

Does anything currently depend on the name:fr-x-gallo=* key? Would anyone be willing to help migrate these elements to name:fr-gallo=*? This would improve interoperability with software that expects valid IETF language tags. Thank you.

2 Likes

The inventor of the tag is fine with the change, due to the low usage, it’s not used in an application (yet).

1 Like