So, do you think I should leave yyyy/mm/dd in addition to yyyy-mm-dd? I didn't think it was that much of a problem to replace slashes with hyphens; as I said, it felt to me more like a "minor stylistic change" on the YMD template, rather than the removal of a template. Note that I also did change mm.dd.yyyy with mm/dd/yyyy (which I think is more common in places that use MDY format), and left dd.mm.yyyy as is (despite of dd/mm/yyyy being more common in Spain, for example). The important thing is that I kept all dd?mm?yyyy, mm?dd?yyyy, yyyy?mm?dd formats, which pretty much covers all formats used around the world (and more specific formats can always be added as custom formats anyway).
But if you think it's better to have both yyyy/mm/dd and yyyy-mm-dd formats in the menu (despite of that causing the menu to be larger for a sort of redundant option), I can leave it as well. Whatever you decide.
And to clarify, I did this not out of rudeness or disregard with other cultures or parts of the world, but on the contrary, as an attempt to find the best compromise solution that would satisfy everyone while keeping Geany simple and easy to use, and to fix an open issue that had been reported. My apologies if this effort was seen otherwise.
As I said, a quick glance at https://en.wikipedia.org/wiki/List_of_date_formats_by_country suggested that the use of yyyy-mm-dd was far more common than yyyy/mm/dd (and that the most frequent format overall seemed to be dd/mm/yyyy, which Geany has never supported).
Looking more into the matter, and since you sparked my curiosity, a search of mentions to date formats within that article yields the following table:
Order | . | - | / |
---|---|---|---|
dd?mm?yyyy | 27 | 7 | 37 |
mm?dd?yyyy | 0 | 0 | 2 |
yyyy?mm?dd | 0 | 24 | 6 |
So maybe we should add dd/mm/yyyy as well (and perhaps dd-mm-yyyy), if we're really aiming to cover most of the world.
(Personally I feel OK with writing DMY dates as 31.01.2024 despite of being more used to 31/1/2024, so I assumed it wouldn't be as much of a big deal for others as well.)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.