![[Unicode]](http://www.unicode.org/webscripts/logo60s2.gif){kind=small}
Modify ↓
CLDR Ticket #6428(accepted enhancement)
Show errors regardless of coverage level
| Reported by: | mark | Owned by: | srl |
|---|---|---|---|
| Component: | survey | Data Locale: | |
| Phase: | dsub | Review: | |
| Weeks: | Data Xpath: | ||
| Xref: |
Description
A significant proportion of errors are where the comprehensive item is wrong, but the vetter doesn't see that listed as a problem — because s/he can't see it at all (at the normal coverage level)!
What we might want to do is make the comprehensive item have an error, but the other item have a warning.
Other ideas?
Attachments
Change History
comment:1 Changed 4 years ago by mark
- Priority changed from assess to major
- Component changed from unknown to design
- Milestone changed from UNSCH to 25dsub
comment:2 Changed 4 years ago by emmons
- Milestone changed from 25dsub to 25rc
Moving all 25dsub and 25design tickets to 25rc. If you plan to complete items in the 25M1 time frame, please move those tickets to 25M1.
comment:3 Changed 4 years ago by emmons
- Owner changed from anybody to srl
- Status changed from new to assigned
- Type changed from unknown to enhancement
- Component changed from design to survey
- Summary changed from Display Collisions across coverage boundaries. to Show errors regardless of coverage level
TC agreed to modify the ST to always show any errors regardless of the selected coverage.
comment:4 Changed 4 years ago by srl
Steven to file separate bug against Vetting Viewer to also include such errors.
comment:11 Changed 22 months ago by emmons
- Milestone changed from 28 to 29
Moving all survey related to 29dsub
comment:12 Changed 20 months ago by emmons
- Milestone changed from 29 to upcoming
Automatic move of all 29 -> upcoming
Note: See
TracTickets for help on using
tickets.
