Feature Proposal - Restrict int_name for exonyms in place names

Overview

A proposal regarding int_name as a place name.
The same key has two meanings that are diametrically opposed: romanization of local name and foreign-language name.
An exonym must specify the language or script (character set).
Non-standard alternate name keys are undesirable.
Please discuss this proposal on its wiki talk page.

RFC announced at tagging mailing list.

1 Like

Can you link its wiki page?

3 Likes

The voting procedure of this RFC, due to the various interim pauses and miscommunication, is causing a weird mix of votes and comments, which makes it unclear if the proposal is clear enough since some voters voted based on something that the OP mentioned that is not the case.
(if what I’m saying isn’t clear, just read the whole voting section of the proposal. I don’t know about you, but it’s clear that even after several discussions in both forum and wiki, there’s still a confusion about what exact changes the proposal seeks to implement, and who/what exactly is affected by those.)

2 Likes

The post is missing context from a previous edit war and debate Key "int_name" must be deprecated

I apologize.