-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
review: various timezone/language/format results #94
Comments
I am referring to this |
I'll take a closer look at this. I plan on focusing more on |
fyi: FF85+ 1635561 this changed Moz.Intl to use The only way to protect this is for en-US only, which is a bit of a hole IMO, that RFP could tighten. TB I think is OK when they hit ESR91 |
update:
So I now have
I can flip the base list to the full So I think that's about it for covering the field, no need to dig further. I mean there's almost 9.5k listed by CLDR, and I don't think that's all of them that are possible |
new summary: so this is out of
|
https://arkenfox.github.io/TZP/tests/timezonenames.html - terrible perf, wish I could do a combined result
So anyway
If you're
nothiding your language, it seems as if two languages can still affect my TZ RFP notation .. and now I just realize I was using resolvedOptions 🤦@abrahamjuliot I'm tired, do you want to whip up a test to return the resolvedOptions timezone for all locales - thanks
The text was updated successfully, but these errors were encountered: