Wikidata:Property proposal/Microsoft KLID

Microsoft KLID

Originally proposed at Wikidata:Property proposal/Natural science

   Not done

Description	Microsoft Keyboard Layout ID
Represents	KLID (Q112883424)
Data type	External identifier
Domain	item
Allowed values	regex for ID string [a-z0-9]{8}
Example 1	Arabic (101) (Q112882452) → 00000401
Example 2	Punjabi (Q112885440) → 0000040f
Example 3	Tamil keyboard (Q7681414) → 00000449
Example 4	Punjabi (Q112885440) → 00000446
Source	https://kbdlayout.info/ (ID can be appended to domain to list information related to keyboard layout)
External links	Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	Add to items for keyboard layouts and build out a more thorough coverage for these on wikidata
Number of IDs in source	208 available from external source as of the dataset included in Windows 10.0.25120.1000 (may grow in the future)
Expected completeness	eventually complete (Q21873974) eventually complete
Formatter URL	https://kbdlayout.info/$1
Wikidata project	WikiProject Computer Science (Q6526225)

Motivation

I am interested in working on language localizations for cross-platform applications and in investigating differences in language treatment across various platforms, I came across these Keyboard Layout IDs which would be helpful for identifying layouts used in Microsoft Windows. Middle river exports (talk) 08:35, 13 July 2022 (UTC)

Discussion

•  Comment @Middle river exports: How is the KLID different from Windows Language Identifier (Q113065422) as described in specification Windows Language Code Identifier (LCID) Reference (Q113065126)? I think Windows Language Identifier (Q113065422) would be justified as a new property for languages, but it appears KLIDs are largely the same identifier? Is there an official specification from Microsoft for what makes up a KLID? --Dhx1 (talk) 10:00, 14 July 2022 (UTC)

  Some languages have several keyboard layouts, and keyboard layouts can be disjointed from languages. There is a listing here from Microsoft where you can see a mapping of languages to their multiple keyboard layouts: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/default-input-locales-for-windows-language-packs?view=windows-11

  Keyboard layouts are also distinct entities from languages and this would be a property just for those rather than languages. --Middle river exports (talk) 10:06, 14 July 2022 (UTC)

  @Middle river exports your example identifiers are just "Language Code IDs" as specified in section 2.2 of Windows Language Code Identifier (LCID) Reference (Q113065126) and prepended with 12 reserved bits and then 4 sort order bits. I support a proposal if it's just the last 16 bits (2 bytes) being proposed to become a new property named "Language ID" (LCID). Otherwise I have to oppose what is currently proposed. Dhx1 (talk) 14:50, 26 September 2022 (UTC)

•  Oppose as proposed. There isn't a single keyboard layout per language but the proposed examples map one-to-one. What exactly is being proposed here? BrokenSegue (talk) 04:01, 14 September 2022 (UTC)

  The items are for single keyboard layouts, not single languages. The proposal is for an external ID for these keyboard layouts. This is explained in the proposal above. Middle river exports (talk) 07:18, 14 September 2022 (UTC)

  oh so they are. I misread. Sorry. Complaint withdrawn. BrokenSegue (talk) 02:17, 15 September 2022 (UTC)

  @BrokenSegue if you don't oppose this anymore can you use strikethrough on your oppose vote? ChristianKl ❪✉❫ 17:49, 7 December 2022 (UTC)

  Done. BrokenSegue (talk) 17:49, 7 December 2022 (UTC)

•  Not done no support for creation --DannyS712 (talk) 17:35, 14 December 2022 (UTC)