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

CLDR Ticket #11239(new survey)

Opened 3 months ago

CLDR Data stability guideline is inappropriate and should be discarded

Reported by: Marcel Schneider <charupdate@…> Owned by: anybody
Component: survey Data Locale: All
Phase: dsub Review:
Weeks: Data Xpath: http://cldr.unicode.org/translation#TOC-Data-stability
Xref:

Description

CLDR guidelines mention data stability as more desirable than optimal data:

“Data stability

Please be mindful of data stability by carefully reviewing previously Approved data. When it's clearly incorrect, it should be changed — but for data stability, don't change the field it is already acceptable (even if not optimal). When you have an evidence of a variant being much better and in customary use than the existing Approved data, use the Forum to bring up discussions and gain consensus to change Approved values.”

Found at: http://cldr.unicode.org/translation#TOC-Data-stability, as per v34 survey while inherited from prior surveys (old guideline).

The meaning of “acceptable” is subject to interpretation. As a thumb rule, in User Interfaces, whenever data is not optimal, it is unacceptable. From an end‐user point of view, data that is suboptimal while it could be easily corrected (like now in a survey round of CLDR), reflects badly on the software brand it is used in, worsening the corporate image of the vendors that appear unable or unwilling to issue an order to correct all obsolete or otherwise wrong data. That phenomenon may commonly be associated with an impression of mindlessness, carelessness, cavalier attitude, flippancy on one hand, and old‐fashioned, not up‐to‐date, belated, backward‐minded on the other hand.

To encourage maintenance of suboptimal data in CLDR is ultimately to deceive the software vendors that are paying for it through their Unicode membership and through appointing delegated staff members to the project.

From that it becomes clear that this displaced stability policy aims at nothing more than keeping inadvertant end‐users in an illusion of accuracy, while those end‐users who are aware of wrong or suboptimal data are disrespected as a small minority (an assumption that needs yet to be assessed).

In a short form, stable while suboptimal CLDR may be considered a front‐stage of hypocrisy.

Therefore, I kindly request that poorly designed stability policy to be discarded.

Attachments

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.