Skip to content
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

Locale info #97

Open
Mariaperez00 opened this issue Dec 29, 2024 · 0 comments
Open

Locale info #97

Mariaperez00 opened this issue Dec 29, 2024 · 0 comments

Comments

@Mariaperez00
Copy link

Or maybe even just define explicit fallback values instead of defaulting to und-001, that way it's more clear what to do in a (theoretical) implementation which doesn't even have locale data for und-001.

| Operation | Default value |

|---|---|

|CalendarsOfLocale | "gregory" |

|CollationsOfLocale | ??? |

|HourCyclesOfLocale | "h23" |

|NumberingSystemsOfLocale | "latn" |

|CharacterDirectionOfLocale | "ltr" |

|WeekInfoOfLocale | { [[FirstDay]]: 1, [[Weekend]]: « 6, 7 », [[MinimalDays]]: 1 } |

collations seems to be a problem, because ICU4C returns the collations for the default locale when the input locale is unrecognised:


andre@andre-dev:~$ LANG=de opt/v8/d8 -e "print(new Intl.Locale('tlh').collations)"

emoji,eor,phonebk

andre@andre-dev:~$ LANG=fr opt/v8/d8 -e "print(new Intl.Locale('tlh').collations)"

emoji,eor

(When de is the default locale, there's an additional phonebk collation in the returned array.)

This seems a bit problematic to me.

Originally posted by @anba in #76

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant