Hello, thank you for reaching out regarding this edit.

1. The Names -> Good Practice -> Multiple Names covers this to some extent.

"Sometimes name=* itself can contain multiple values separated by semicolons:

In multilingual regions or localities, multiple names in different languages may be relevant enough to include in name=*. A separator other than a semicolon, such as "/" or "-" (spaced or not), may be customary locally. This is not a substitute for language-specific keys, such as name:en=* for English."

https://wiki.openstreetmap.org/wiki/Names#Multiple_names

A decision therefore needs to be made whether each name is relevant enough to be added with a separator slash such as a "/". One should also take into account whether that language is used by a significant amount of people in that locale.

2. This would go back to coverage in #1. Does it appear on signage and print materials? Is it used locally in equivalent quantities to the English language name? Do a significant portion of the local population speak the language?

3. I mentioned this due to a few cases:

#1 An International editor edited Indian Reservation boundaries to include dual Indigenous / English language names. However, the Indigenous name is not an officially recognized or locally used name for the Indian Reservations boundaries. For example, in evacuation notices distributed by the Indigenous band the English name was the name used.

#2 The addition of the Indigenous / English language name to Whistler and Britannia Beach. Both of these areas are disputed by Indigenous bands. And, neither name is frequently used by a significant portion of locals and hence fails the test to be included in the default name tag.

#3 A recent edit of The Lions peaks to an English version of the name. The Indigenous name is not the official name, not on signage, and not frequently used by locals. 