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

CLDR Ticket #10921(accepted)

Opened 9 months ago

Last modified 3 days ago

/tags/release-32-0-1/keyboards/und/ should be sorted by platform

Reported by: Marcel Schneider <charupdate@…> Owned by: anybody
Component: keyboards Data Locale: any
Phase: dvet Review:
Weeks: Data Xpath: /tags/release-32-0-1/keyboards/


The /und/ directory currently contains keyboards for three platforms. The platform a given keyboard can be used on is declared as part of the locale ID.

Hence these keyboards are not “undefined.”

It would be more appropriate to add an /additional/ subdirectory in each platform directory, and to dispatch the additional keyboards accordingly.


Change History

comment:1 Changed 9 months ago by mark

  • Owner changed from anybody to kristi
  • Phase changed from dsub to dvet
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 34

comment:2 Changed 4 months ago by kristi

  • Owner changed from kristi to Future

comment:3 Changed 4 months ago by Marcel Schneider <charupdate@…>

Sorry, the original suggestion was based on a misconception of what “undefined” is supposed to express.

Actually what is undefined with respect to the layouts grouped in the /und/ directory, is the contributor of the layouts, not the platform they are designed for. The folder named /android/ contains the layouts currently distributed by the vendor of that operating system, and so on for /chromeos/, /osx/, and /windows/ respectively, By contrast, /und/ contains layouts designed and/or distributed by various organizations or individuals. Therefore it is not convenient to move them to subdirectories included in the folders dedicated to main vendors.

Additionally, the number of layouts contained in /und/ is actually less than a dozen. Grouping them together in a single folder is very convenient as they are naturally (by default sorting) ordered by locales, and thus probably by designers.

Therefore I’d suggest to dismiss this request and to close the ticket. Thanks.

comment:4 Changed 4 weeks ago by pedberg

  • Milestone changed from 34 to upcoming

CLDR 34 BRS closing item, move all open 34 → upcoming

comment:5 Changed 3 weeks ago by mark

  • Milestone changed from upcoming to 35-optional

comment:6 Changed 8 days ago by mark

  • Milestone changed from 35-optional to to-assess

comment:7 Changed 3 days ago by mark

  • Owner changed from Future to anybody

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.