-
-
Notifications
You must be signed in to change notification settings - Fork 13
Insights: unicode-org/conformance
Overview
-
- 0 Merged pull requests
- 1 Open pull request
- 2 Closed issues
- 2 New issues
There hasn’t been any commit activity on unicode-org/conformance in the last week.
Want to help out?
1 Pull request opened by 1 person
-
Updating number format data generation and NodeJS number_fmt
#468 opened
Jun 18, 2025
2 Issues closed by 1 person
-
Dart Native and Dart Web executors need fixes
#440 closed
Jun 16, 2025 -
Add tests for new Segmenter component
#463 closed
Jun 16, 2025
2 Issues opened by 1 person
-
What to do with dateTimeFormatType atTime?
#469 opened
Jun 20, 2025 -
Re-enable the Dart Native executor
#467 opened
Jun 16, 2025
8 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Make collation data read from CLDR
#401 commented on
Jun 16, 2025 • 0 new comments -
Segmenter results are inconsistent across platforms
#466 commented on
Jun 16, 2025 • 0 new comments -
Specify order of library/platforms in dashboard
#452 commented on
Jun 16, 2025 • 0 new comments -
Add UI to compare test results other test runs: same platform/other ICU & same ICU/other platform
#449 commented on
Jun 16, 2025 • 0 new comments -
End-to-end should quit for Node JS when executor missing
#459 commented on
Jun 16, 2025 • 0 new comments -
Investigate correct behavior for Japanese skeleton resolution
#448 commented on
Jun 16, 2025 • 0 new comments -
Number format in C/J has problems with rounding and number of digits represented
#442 commented on
Jun 16, 2025 • 0 new comments -
DateTime test data from CLDR (>= CLDR 47) is not consistent with ICU4C/J
#441 commented on
Jun 16, 2025 • 0 new comments