I am working on a project, and it would make our schema much much simpler if the Locales feature allowed for custom locales. For example, if we could create locales with the name Mars, Venus, and Uranus, and then use all of the per-field locale options just like we can currently do with real-world locales.
Hmm, technically you CAN use custom locales as long they “look like” locales:
- Only letters and dashes, no numbers or symbols
- 2-4 letters long per segment (separated by dashes)
- Two segments max
e.g.
Note that the system will try to fight you if your code happens to match a language or locale, like:
But yeah, this isn’t great UX. It’d be nice to just have a proper custom locale system.
Ah! Thank you for the quick response! That would work ok for my project, but if you do implement a fully custom locale system that would be fantastic.
1 Like