Fix Formatting Issues - Training it / reject always or Use different langage

In our company, we use the “native” spellings for cities—such as Zürich instead of Zurich, and Genève instead of Geneva etc. Whenever I use the (very useful!) “Fix Formatting Issues” feature, I’m prompted to change these names to their English spellings.

This requires me to manually scroll through numerous entries I don’t want to modify, just to find the ones I do—like time zone discrepancies, extra spaces, or incorrect state/region details.

Additionally, using the “Reject” option only dismisses the unwanted corrections temporarily; the same suggestions reappear the next time I run the feature. A more permanent rejection option would streamline the process significantly.

My suggestion to the developers would be to enhance the “fix formatting issues” feature to include the option to do one (or more) of the following:

  1. Permanently reject certain corrections so they don’t reappear each time the feature is used.
  2. Train the system to recognize and prioritize our preferred spelling conventions.
  3. Incorporate a default language setting that preserves city names in their original language.
    For example.

I feel your pain. We need the changes you recommended, too!!

The majority of our suggested location “fixes” (we have 12,000+!) want us to change the name of one city to be another city. But the city we’re using is correct.

For example, here is a fix HS recommends:

I think this is probably because the USPS zip code lookup feature shows a preference for the city name based on zip code:

Yet interestingly, if you use the full address USPS will override its own recommendation and use the alternative when it’s more accurate:

So we definitely need a way to override certain fixes permanently. I could foresee a button or section that lets you add alternative valid values, which you could lock in or confirm by providing your HS ID.