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

CLDR Ticket #6227(accepted tools)

Opened 5 years ago

Last modified 2 years ago

move functions for "which locales can the vetter modify" and "which locales are readonly" into core

Reported by: srl Owned by: srl
Component: survey Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description (last modified by srl) (diff)

locale match

  • function is currently misnamed UserRegistry.localeMatchesLocale
  • For example, "en" matches "en_GB", etc.
  • This would also process matches such as "*"
  • This would allow VettingViewer to do matching of which users match which locale

which locales are readonly

  • SurveyTool's function STFactory.isReadOnlyLocale should be retitled and moved into core
  • this will let tools know which locales are editable vs non editable in ST

Attachments

Change History

comment:1 Changed 5 years ago by srl

also STFactory.isReadOnlyLocale should include aliased and defaultcontent locales.

Perhaps these functions should move into Core also? Could be useful for tools to know whether they should tell users to file bugs or redir to ST.

comment:2 Changed 5 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to tools
  • Priority changed from assess to medium
  • Milestone changed from UNSCH to 24dvet
  • Owner changed from anybody to srl
  • Type changed from unknown to task

comment:3 Changed 5 years ago by mark

Make sure the method name reflects the purpose and operation.

comment:4 Changed 5 years ago by srl

  • Description modified (diff)
  • Summary changed from UserRegistry.localeMatchesLocale() should use CLDRLocale parentage functions to move functions for "which locales can the vetter modify" and "which locales are readonly" into core

comment:5 Changed 5 years ago by srl

  • Milestone changed from 24dvet to 25dsub

triage

comment:6 Changed 4 years ago by emmons

  • Milestone changed from 25dsub to 25M1

Moving all 25dsub to 25M1. Please adjust the milestone if you are not planning to complete the item in the 25M1 time frame.

comment:7 Changed 4 years ago by srl

  • Milestone changed from 25M1 to 25rc

comment:8 Changed 4 years ago by srl

  • Milestone changed from 25rc to 26dsub

rolling

comment:9 Changed 4 years ago by srl

  • Milestone changed from 26dsub to 26dvet

comment:10 Changed 3 years ago by srl

  • Milestone changed from 26dvet to 27dsub

roll

comment:11 Changed 3 years ago by markus

  • Phase set to dsub
  • Milestone changed from 27dsub to 27

comment:12 Changed 3 years ago by srl

  • Milestone changed from 27 to 28

roll

comment:13 Changed 3 years ago by markus

  • Type changed from task to tools
  • Component changed from tools to unknown

comment:14 Changed 3 years ago by srl

  • Status changed from assigned to accepted

comment:15 Changed 2 years ago by emmons

  • Component changed from unknown to survey

comment:16 Changed 2 years ago by emmons

  • Milestone changed from 28 to 29

Moving all survey related to 29dsub

comment:17 Changed 2 years ago by emmons

  • Milestone changed from 29 to upcoming

Auto move of all 29 -> upcoming

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.