Bug 90960

Summary:	Model and geometry for Truly Ergonomic Computer Keyboard (TECK)
Product:	xkeyboard-config	Reporter:	mch
Component:	General	Assignee:	xkb
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	Geometry and definition of Truly Ergonomic Computer Keyboard

Description mch 2015-06-12 19:41:21 UTC

Created attachment 116464 [details]
Geometry and definition of Truly Ergonomic Computer Keyboard

Hi

In the attachment you find a patch that adds the geometry and keyboard definitions for Megawin's Truly Ergonomic Computer Keyboards model 227 and 229. The geometry files result in these graphics: https://imgur.com/di9EAGf,zxfe3nu#0
See https://www.trulyergonomic.com/ for a comparison.

Comment 1 Sergey V. Udaltsov 2015-09-29 20:15:26 UTC

Thank you, committed! Even though these days updating symbols/inet is excessive.

Comment 2 Vladimir Panteleev 2016-03-13 02:56:30 UTC

Hi, sorry I'm not familiar with XKB details but I think there is nothing to bind the keyboard model to its geometry. As a result, e.g. KDE layout preview shows the standard PC-101 geometry.

E.g. for the HHK there is this line in base.m_g.part:

hhk           =       hhk(basic)

I think a similar line should be added somewhere for TECK, something like:

teck227 = teck(teck227)
teck229 = teck(teck229)

Comment 3 Sergey V. Udaltsov 2016-05-18 15:32:22 UTC

> E.g. for the HHK there is this line in base.m_g.part:
That is right. Give it a try, and if works for you - please submit a patch.

Comment 4 GitLab Migration User 2018-12-28 00:38:27 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/67.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.