Better localised address handling.
Overview
Currently, address forms in CiviCRM are built from a US-centric default set of form fields, currently we're using the translation system to alter the titles of these for different regions (e.g a string translation exists for State/Province to County for EN_GB).
This ends up giving us a bad DX and bad UX we end up in a situation where even US address fields end up with a "County" field if we're using the EN_GB translation, not to mention that we're violating a rather fundamental aim of translation in that we're not actually translating - we're substituting a different string for a localised requirement that's unconnected to the language in use.
Proposed Solution
We should investigate using a library e.g: CommerceGuys/Addressing (or another mechanism) to provide country-aware address forms/fields which work for CiviCRM's global community.