I do write Lisbon, Portugal, whenever I talk about where I live. Doesn't take much extra effort to provide more precision and avoids possible confusions.
In a moment of whimsy I briefly considered a date format where digits were sorted alphabetically.
2026-07-02-16-31-52 -> -----00011222235667
Hopefully it will remain a nonsense and never be seen in the wild, unlike the phone number field which I found on a real website which responded to scroll events to increase and decrease the value it contained.
Well that's just totally ambiguous. What you should do instead is treat the date as one long number and present its factors, for instance 2⁴⋅11⋅7649⋅15050023, much more practical.
Most every personal phone number I've obtained has had a spelling, and a good logical spelling, which isn't really the norm for personal phone numbers.
In fact, the first time I signed up for my own line, it happened unintentionally, and it was only after Pacific Bell had installed the line that I figured out it spelled something, and I informed my father and it was hilarious (the spelling was "BUG-BLOW").
The European Commission published its own language guide. In terms of English it's only a small deviation from en-GB, but my first thought was indeed: when can I set en-EU?
> This style guide is intended primarily for English-language authors and translators, both in-house and freelance, working for the European Commission.
as an American this is my favorite format. Sortable, and the mm-dd order reflects the standard American way of writing month+day, and yyyy is unambiguously the year since it's 4 letters. Best of both worlds.
I believe it's the ISO standard because it is obviously distinguishable from both the MM-DD-YY (US) date order and the DD-MM-YY (UK/EU/Others) date order and so is unambiguous.
Although my (AU) locale is dd-mm-yyyy, I'll use yyyy-mm-dd anywhere I have to write a date in all numbers to avoid any ambiguity. It also has the advantage of sorting correctly in things like file names.
For something more likely to be read by a human and not parsed by a computer (and is not locale or i18n/l10n flexible) I'll use d mmm yyyy, e.g., 3 Jul 2026. To my thinking, for English speaking this is the friendliest unambiguous format (although I'm sure opinions will differ).
"Friday 3 July 2026" (yes, I elected to spell out the month) also has the advantage of not requiring commas for legibility ("Friday, July 3, 2026" being common in the US).
Vad himla pratar du om? ALLT använder dd/mm-yy. Jag har aldrig sett något på svenska som använder yyyy-mm-dd, det finns bara inte. Det finns i Sverige, men då är det också på engelska.
Back in 1997 I was assigned to convert a legacy SAS 5 application to SAS 6.
Let's just say that the original programmer had adopted MANY of the techniques in the linked post. The first thing I did was to go through all the code and convert it to only have one statement per line. eye roll
I think you would need a lot more context to say if 0.019% is too high. If this platform is driving real operational improvements and is the core software backbone, then it doesn't seem particularly unreasonable.
Could track length include sidings and double-tracks and extensions and other maintenance track needs that aren't useful for the passengers themselves?
reply