https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #303 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to crptdngl71 from comment #301) > Why can't we have a locale named "my_MY" which at first simply is a local (on > same computer) copy of an existing locale, such as de_DE here. "my_MY" > indicates "my locale", or name it "usr_USR" and introduce a naming convention > to identify standard locale from user adjusted locale. The correct language code would be mul-XXX-{$custom_name}, per ISO 639-3:2007(en) and ISO 3166-3:2013(en). See https://linguistics.stackexchange.com/revisions/38453/1#:~:text=It%20is%20a%20misconception%20that%20an%20unassigned%20code%20in%20a%20standard%20can%20be%20just%20used%20for%20anything%20you%20want.%20It%20may%20be%20officially%20assigned%20tomorrow!%20This%20is%20unlikely%20in%20the%20case%20of%20ISO%20639%2D1%2C%20but%20this%20is%20the%20way%20standards%20work. > Then use a GUI tool (KDE) to change whatever separation string into which > ever time separation string, re-arrange locale time tags to the order you > want, > change / to . where ever you want, use capital letters vs. small letter where > you want - but in the end we do not use anything totally new or introduce > anything completely new or re-invent the wheel again. Otherwise, the reason for such customisation not being the focus is because if someone wants to adhere to ISO 8601-2:2019/Amd 1:2025, as so many here do, they shouldn't need to locate a suitable string to add to their preferences: it should be a preset. However, in retrospect, your proposal might be a useful basis – better to have it be entirely customisable, then add presets later. -- You are receiving this mail because: You are watching all bug changes.
