I can’t replicate this in 8.9.2 on macOS 14.14.6, noting we are on different OS major versions. For me, the AM/PM times coerce correctly to the 24-hour clock format. I say this as Tinderbox looks at the user’s OS locale for date/time formatting, so the issue might be something in the way you’ve got your OS date settings configured. If it was v8.9.2 generally, I’d expect to see the errors you report, but i don’t.
Incidentally, I’m not sure this is true:
I think you mean common in the USA. In reality, for both date and time formats, the US is actually an global outlier:
But there’s no single right/wrong here as there isn’t a single global format convention for time & dates in general (vs official) use. This worldwide variation is why Tinderbox uses your OS locale, as this is generally most likely to match your expectation. Most of us are used to using our local conventions and get confused by unfamiliar ones.
Time conversions depend on your locale settings, which you will find in System Preferences : Language and Region : Advanced.
Even further complicating things, Tinderbox does intervene to catch some usages that macOS thinks to be ill-formed but that aren’t uncommon — and, for better or worse — Tinderbox in these cases tends to assume American idioms. But I don’t think that’s what happens here.
To make things more complicated, details of the default settings change from one version of macOS to the next, and of course you might not be using the default settings.
Yes, I’m a Japanese user living in Japan. My OS’s locate is Japan and “Language & Region” and “Date-Time” preferences also are set to Japanese.
For confirmation, I made a new user account whose language is English.
In the environment, the time conversion is correct.
So, my problem is likely due to my own environment.
But, exploring the true condition leading this problem would take many time and effort, or, if my system setting related to locate be set to English, other problems could occur.
A practical and fast resolution may be, therefore, a special processing the string being misinterpreted with Applescript or other scripting. I will do so.
