[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #11105(new unknown)

Opened 2 months ago

Last modified 6 weeks ago

CheckWidths fix?

Reported by: mark Owned by: anybody
Component: unknown Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description (last modified by mark) (diff)

I saw the following. Seems like we should follow up on it.

        // This was put in specifically to deal with the fact that we added a bunch of new units in CLDR 26
        // and didn't put the narrow forms of them into modern coverage.  If/when the narrow forms of all units
        // are modern coverage, then we can safely remove the aliasedAndComprehensive check.  Right now if an
        // item is aliased and coverage is comprehensive, then it can't generate anything worse than a warning.
        Boolean aliasedAndComprenehsive = (coverageLevel.getLevel(path).compareTo(Level.COMPREHENSIVE) == 0)
            && (status.pathWhereFound.compareTo(path) != 0);

Attachments

Change History

comment:1 Changed 8 weeks ago by mark

  • Description modified (diff)

comment:2 Changed 6 weeks ago by mark

This is in

CheckWidths

public CheckCLDR handleCheck(String path, String fullPath, String value, Options options, List<CheckStatus> result) {

View

Add a comment

Modify Ticket

Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.