i18n: Remove our awkward &-escape support, except in [DesktopUI] #19218
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows supports adding "&" before a text character in a string, and using that as an accelerator key. To actually produce a "&", you need to use "&&". This is mainly used in window menus and in classic win32 dialog boxes. Elsewhere in the app, it's not used. The Win32 "DrawText" API supports discarding & for drawing, and we've stuck to that standard for all the text backends, leading to awkward workarounds.
So, to simplify the code (before improving our text rendering code in other ways) let's get rid of it almost everywhere (except in win32 menus).