This issue tracks the full display name algorithm implementation on top of the optimized data (#3260), which is designed for granular data slicing and supports more efficient loading where only a single name lookup is required (e.g., "Current Location: France").
While the multi submodule provides broader coverage, the single submodule is currently in active development and has a more limited feature set. We are seeking early adopters to test the current implementation and provide feedback on real-world utility.
See also #7824 for evaluating the single vs multi API style.
Implementation Status
The single submodule currently supports a subset of the display name types available in multi.
| Feature |
Supported in single? |
Type Name (Example) |
| Regions |
✅ |
RegionDisplayName |
| Scripts |
✅ |
ScriptDisplayName |
| Languages |
❌ |
Not yet implemented |
| Variants |
❌ |
Not yet implemented |
| Locales |
❌ |
Not yet implemented |
This issue tracks the full display name algorithm implementation on top of the optimized data (#3260), which is designed for granular data slicing and supports more efficient loading where only a single name lookup is required (e.g., "Current Location: France").
While the
multisubmodule provides broader coverage, thesinglesubmodule is currently in active development and has a more limited feature set. We are seeking early adopters to test the current implementation and provide feedback on real-world utility.See also #7824 for evaluating the
singlevsmultiAPI style.Implementation Status
The
singlesubmodule currently supports a subset of the display name types available inmulti.single?RegionDisplayNameScriptDisplayName