Add old_name= support

[matkoniecz]

Description, Motivation & Context

It makes sense to support this tag

Related issues

fixes #1288

Links and data

Relevant OSM Wiki links:

https://wiki.openstreetmap.org/wiki/Key:old_name

Relevant tag usage stats:

911k uses

Checklist and Test-Documentation Template

Read on to get your PR merged faster…

Follow these steps to test your PR yourself and make it a lot easier and faster for maintainers to check and approve it.

This is how it works:

1. After you submit your PR, the system will create a preview and comment on your PR:

   🍱 Your pull request preview is ready.
   If this is your first contribution to this project, the preview will not happen right away but requires a click from one of the project members. We will do this ASAP.

2. Once the preview is ready, use it to test your changes.

3. Now copy the snippet below into a new comment and fill out the blanks.

4. Now your PR is ready to be reviewed.

## Test-Documentation

### Preview links & Sidebar Screenshots

<!-- Use the preview to find examples, select the feature in question and **copy this link here**.
     Find examples of nodes/areas. Find examples with a lot of tags or very few tags. – Whatever helps to test this thoroughly.
     Add relevant **screenshots** of the sidebar of those examples. -->

<!-- FYI: What we will check:
     - Is the [icon](https://github.com/ideditor/schema-builder/blob/main/ICONS.md) well chosen.
     - Are the fields well-structured and have good labels.
     - Do the dropdowns (etc.) work well and show helpful data. -->

### Search

<!-- **Test the search** of your preset and share relevant **screenshots** here.
     - Test the preset name as search terms.
     - Also test the preset terms and aliases as search terms (if present). -->

### Info-`i`

<!-- **Test the info-i** for your fields and preset and share relevant **screenshots** here.
     The info needs to help mappers understand the preset and when to use it.
     [Learn more…](https://github.com/openstreetmap/id-tagging-schema/blob/main/CONTRIBUTING.md#info-i)
 -->

### Wording

- [ ] American English
- [ ] `name`, `aliases` (if present) use Title Case
- [ ] `terms` (if present) use lower case, sorted A-Z
<!-- Learn more in https://github.com/openstreetmap/id-tagging-schema/blob/main/GUIDELINES.md#2-design-the-preset -->

[github-actions]

🍱 Your pull request preview is ready

Please use this preview to check your changes. Ideally use the test documentation template and document your test results by commenting on the PR. This will speed up the review process for everyone.

FYI, once this PR is merged, you can use the iD Editor Preview to test your changes in interaction with all other changes.

[matkoniecz]

hmm, maybe something should be done to keep it with regular name?

https://pr-1996--ideditor-presets-preview.netlify.app/id/dist/#locale=en&map=19.79/50.05932/19.94286&disable_features=boundaries&background=fr.ign.bdortho&id=w1428450731

[matkoniecz]

though I see that alt_name gets jumped into random position between

[matkoniecz]

mentioned at https://community.openstreetmap.org/t/likely-upcoming-tags-in-id-review-welcome-food-old-name-piercing-indoor-seating-yes-no/142495

I propose to wait at least until 2026-04-04 to give community time to review this PR

[mcliquid]

For me it would be important to ensure consistent field ordering and grouping with other name-related tags (like name and alt_name) to avoid a confusing or fragmented user experience in the editor UI.

[1ec5]

#215 added several similar fields. They all sort at the bottom because they’re optional fields. Adding them immediately after Name makes logical sense but would push down other fields that are important enough to be visible by default. In any case, that sorting behavior is iD’s responsibility if I’m not mistaken.

[1ec5]

Also: historical name, dated name, formerly known as, fka.

[matkoniecz]

added!

[matkoniecz]

In any case, that sorting behavior is iD’s responsibility if I’m not mistaken.

well, we can also define this in tagging schema but it requires https://github.com/ideditor/schema-builder work to extend schema what we can define

[matkoniecz]

kind of related: openstreetmap/iD#12005 - Show and edit related subtags in the inspector (check_date, note/description, source, conditional, numeric, other)

[matkoniecz]

Created ideditor/schema-builder#282 to cover field positioning.

The question is now whether it is better to show old_name imperfectly (for now) or not at all.

[1ec5]

old_name=* is already more tenuous than the alt_name=* etc. fields we already have. If we can live with those fields having less prominence than operator=* or access=*, then I think we can live with old_name=* being just as obscure.