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

CLDR Ticket #10705(accepted)

Opened 13 months ago

Last modified 6 days ago

Stricter script and consistency checks

Reported by: mark Owned by: mark
Component: survey-backend Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

Problems like those in ticket:10689 lead me to think that we should have

  1. A much stricter script test.
  2. Better cross checks between the widths of forms. For example, we could flag an error if all the characters in each of the widths (wide, short, narrow, ...) are disjoint. That would help to catch cases where the script was Latin, but the narrow=abc & wide=cdefgh — they have no characters in common.

I've been thinking about this, and we could have a data file of allowed errors. That is, one problem we have is that we can't make a case into a error unless it is wrong 100% of the time, if because there are some exceptional cases where it is justified.

But suppose we had a set of files like:

errorsSuppress/bg.txt
ldml/units/unitLength[@type="short"]/unit[@type="duration-hour"]/unitPattern[@count="*"] ; asciiCharactersNotInMainOrAuxiliaryExemplars
...

we could edit that to allow the errors in special circumstances. It would be a bit of a pain to edit; copying the bath from the bottom of the ST into the file, and picking up the error from the left-hand info box but in might be workable. (In the future we might have some UI to do it, with TC access.)

Attachments

Change History

comment:1 Changed 11 months ago by mark

  • Status changed from new to accepted
  • Component changed from unknown to survey
  • Priority changed from assess to major
  • Milestone changed from UNSCH to 34
  • Owner changed from anybody to mark
  • type changed from unknown to tools

comment:2 Changed 3 months ago by mark

  • Milestone changed from 34 to 35

do before ST

comment:3 Changed 6 days ago by mark

  • Milestone changed from 35 to 35-optional
View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.