Conversation
|
Thanks for the PR! I'm wondering if we should just add a "default for locale" option that more flexibly handles this? Also, from my experience the slash |
I think a default for locale option would make sense. The only issue I see with that is that English US being the only English locale, while also being the only one that uses MM/DD/YYYY (I think? idk what Canada does but the UK, AUS, NZ and other English speaking places use ddmmyyyy). This could be solved with more English "translations" too. Also yes the slash is the most common here. I see "." sometimes (as in 2.3.2022) but not often. |
…er than being semi hard-coded. Translations need discussing as it does slightly change the functionality in every language but en_us.
|
Yeah thats locale based now and adds a numerical option. Using 2nd March 2022 as an example, numerical becomes:
For supporting other English varieties (such as en_gb, which is why I made this in the first place lmao) these would have to be added to weblate. If you added en_gb I can get that "translated" relatively quickly, which is one of them done, and I'm sure that other people can do the same for the other English varieties. |
Changes
Added in 2 date formats for dd/mm/yyyy and dd MMMM, yyyy (examples: 2/3/2022 and 2 March, 2022 respectively).
This is really simple and just is to accommodate people who use dd/mm/yyyy rather than mm/dd/yyyy (like me).
Todo before merging
Related Issues
Closes #1757 as I found it while writing this lmao.