typefu gives the error "Chosen file does not contain a valid Type Fu layout definition."

Does anyone have halmak working on a chromebook? Or is someone familiar with creating an extension that could add it for chromebook?

https://www.keybr.com/layouts

Hi, this keyboard don't have latam support, so i made it.
Hola, este teclado no tiene soporte latam, asi que lo hice.

I have tested it all, and it works in any Xorg session
Lo he testeado todo, y funciona en cualquier sesion de Xorg

to install it, copy this in the end of your latam file, in
/usr/share/X11/xkb/symbols/latam

para instalarlo, copia esto al final de tu archivo latam, en
/usr/share/X11/xkb/symbols/latam

copy this ↓ copia esto ↓

// Latin American Spanish Halmak mapping (by Germe-fur)
// original halmak layout in https://github.com/MadRabbit/halmak/
// star his repo ;)
partial alphanumeric_keys
xkb_symbols "halmak" {

    name[Group1]="Spanish (Latin American, Halmak)";

    key <TLDE> {[          bar, degree,             notsign,      notsign ]};
    key <AE01> {[            1, apostrophe,             bar,   exclamdown ]};
    key <AE02> {[            2, quotedbl,                at,    oneeighth ]};
    key <AE03> {[            3, numbersign,  periodcentered,     sterling ]};
    key <AE04> {[            4, dollar,          asciitilde,       dollar ]};
    key <AE05> {[            5, percent,            onehalf, threeeighths ]};
    key <AE06> {[            6, ampersand,          notsign,  fiveeighths ]};
    key <AE07> {[            7, slash,            braceleft, seveneighths ]};
    key <AE08> {[            8, parenleft,      bracketleft,    trademark ]};
    key <AE09> {[            9, parenright,    bracketright,    plusminus ]};
    key <AE10> {[            0, equal,           braceright,       degree ]};
    key <AE11> {[       exclam, exclamdown,       backslash, questiondown ]};
    key <AE12> {[     question, questiondown,  dead_cedilla,  dead_ogonek ]};

    key <AD01> {[          w, W,             U2018,          U201C ]};
    key <AD02> {[          l, L,              cent,      copyright ]};
    key <AD03> {[          r, R,        registered,      trademark ]};
    key <AD04> {[          b, B,             U2022,          U03B2 ]};
    key <AD05> {[          z, Z,             U0292,          U01B7 ]};
    key <AD06> {[     ntilde, Ntilde,   asciitilde,          U02EE ]};
    key <AD07> {[          q, Q,             U2039,  guillemotleft ]};
    key <AD08> {[          u, U,            ubreve,      Ubreve ]};
    key <AD09> {[          d, D,             U203A, guillemotright ]};
    key <AD10> {[          j, J,          jcircumflex, Jcircumflex ]};
    key <AD11> {[ dead_acute, dead_diaeresis, dead_diaeresis, dead_abovering ]};
    key <AD12> {[       plus, asterisk, asciitilde,    dead_macron ]};

    key <AC01> {[          s, S,     scircumflex,      Scircumflex ]};
    key <AC02> {[          h, H,     hcircumflex,      Hcircumflex ]};
    key <AC03> {[          n, N,          hyphen,            U2190 ]};
    key <AC04> {[          t, T,           thorn,            THORN ]};
    key <AC05> {[      comma, semicolon,  hyphen,         multiply ]};
    key <AC06> {[     period, colon,       U0323,         division ]};
    key <AC07> {[          a, A,              ae,               AE ]};
    key <AC08> {[          e, E,        EuroSign,            U2191 ]};
    key <AC09> {[          o, O,           U00BA,            U00AA ]};
    key <AC10> {[          i, I,           U2015,            U2192 ]};
    key <AC11> {[  braceleft, bracketleft, dead_circumflex,  braceleft ]};
    key <BKSL> {[ braceright, bracketright,     dead_grave, braceright ]};

    key <LSGT> {[     less, greater,        bar,       U00A6 ]};
    key <AB01> {[        f, F,            U2019,       U201D ]};
    key <AB02> {[        m, M,         multiply,       U2193 ]};
    key <AB03> {[        v, V,         division,       U03B3 ]};
    key <AB04> {[        c, C,      ccircumflex, Ccircumflex ]};
    key <AB05> {[    minus, underscore                       ]};
    key <AB06> {[        g, G,      gcircumflex, Gcircumflex ]};
    key <AB07> {[        p, P,            U2293,   paragraph ]};
    key <AB08> {[        x, X,            U2020,       U2021 ]};
    key <AB09> {[        k, K,            U00E7,       U00C7 ]};
    key <AB10> {[        y, Y             ]};

    include "level3(ralt_switch)"
};

to activate it, run
para activarlo, corre

setxkbmap -model pc105 -layout latam\(halmak\)

a personal improvement is activate caps:backspace, that converts your (unused) caps lock key to a backspace.
and allow it to repeat (the xset at the end)
una mejora personal es activar caps:backspace, que convierte tu (sin uso) tecla bloq mayus en un retroceso.
y permitirle la repetición (el xset al final)

setxkbmap -model pc105 -layout latam\(halmak\) -option caps:backspace && xset r 66

uninstall - desinstalar

to uninstall it, just delete the code you have pasted in your latam file
para desinstalarlo, solo borra el codigo que pegaste en tu archivo latam

Note: you must run the command to apply every session, but you can automate it, writing the command in ~/.xprofile
Nota: deberas correr el comando para aplicar cada sesion, pero puedes automatizarlo escribiendo el comando en ~/.xprofile

Could you please add Linux support?

I had to deviate from the instructions a little bit.

1. Copy the contents of /symbols/halmak and paste them into the /usr/share/X11/xkb/symbols/us file which contains all keyboard layout variants of standard US English, including Dvorak, Colemak, and Workman. Preferably locate it near where those other options are.
2. Add a line above name[Group1]= "English (Halmak)"; that says include "us" in the symbols file.
3. Put the halmak variant near the Colemak or Dvorak list & description section in /rules/evdev.xml similar in formatting to the other variants. An example description is English (Halmak) or AI superiority.

Notes:

• The < and > symbols, which are normally on the , and . keys, have been switched for the ( and ) symbols, making it far easier to program and type, but your keyboard keycaps may still show the wrong symbols.

Issues:

• The layout will switch all the key positions back to QWERTY when you hold down the CTRL key so that undo, cut, copy, paste, find, close window, select all, and other common muscle memory shortcuts work without remapping everything to new keys or reaching for awkward combinations. However, this does not always work as expected in every program, and I think it would just be better off without the hit-or-miss backwards compatibilities. Disabling them in the qwerty-controls file seems to at least work with CTRL no longer switching keymaps, but there may still be a little bit of odd behavior depending on whether the program detects direct hardware input, or the translated inputs from xkb.

I find this far easier to use and learn versus ColemakDH or Qwerty. Thank you for sharing it with us, and telling us how to get it working on each of our operating systems. I tried for days to get it working on Clear Linux, Arch, FreeBSD, and Fedora before finding your repository.

global search and find does not work with key combination of command plus F within macos Catalina 10.5.7

I'm from Poland and use ąćłŃŹŻ etc.
Many people using Celsius degree char, phi, paragraph (on apple keyboard) etc. French have many chars, Korean too.

I'm found only one https://klawiatura.wordpress.com/ but this is only concept

I build these installation files and .klc file by Microsoft Keyboard Layout Creator.
You can choose one for your Windows and install it.
At least the developers can release halmak.klc file.
halmak.zip

First off, very cool project. Thanks for putting it out there.

Was any consideration given to the potential of using digraphs or trigraphs to make typing more efficient? Digraphs like 'th', 'he', 'in', and 're' may all be more useful than a 'z' or a 'q' key. I'm curious if your AI considered this and/or if it could be implemented as a mixed-layer solution.

It's definitely broken on macOS, even the latest Ventura. It can install fine after reboots, however it is impossible to have it select halmak - it just hangs and reverts back to the system language.

Will go with a hardware based solution and pick it up again then.

Hello, Halmak seems very promising, but is there any guide on stages of learning similar to the Minimak or Tarmak layouts? I feel like it could certainly help me get a feel for this layout better.

Thanks so much!

https://github.com/pguerin3/halmak4windows

Hello,

This seems great and I would like to use try it out.
I've followed the installation instructions for Mac, but under macOS Mojave they don't seem to work.

You can select the keyboard layout, but does not activate.

Any suggestions or hints?

Cheers,
Tom

From the README:

This is an AI designed keyboard layout that was built within the keyboard-gentics project.

Too bad AI didn't write that README, it probably wouldn't make typos like that (highlighted, also repeated in another part of README, which leads to concerns that fingers motions with the new keyboard are such that in a key sequence of "n", "e", "t" - the "e" gets often lost ;-) ).

Not sure if kbd can allow for different mappings when pressing ctrl or other modifiers, but kbd uses a different format which seems pretty easy to map. I found it while looking at the keyboard configuration page on the arch wiki.

https://jlk.fjfi.cvut.cz/arch/manpages/man/keymaps.5

If I get around to it at some point I'll probably try to make the configuration, but for now I figured you might find it useful and if you want to make it that'd be sweet

On big sur 11.01 only few apps allow me to use halmak as input source, such as terminal and different ides. For example in Safari I am unable to select halmak as source even id it's appear in every select option.

I'm amazed by the idea of using AI to find the most efficient keyboard layout. And I really appreciate the effort you've put into creating the Halmak layout.

It's very obvious that the efficiency of a keyboard layout is language-specific. I want to apply the same method to find the most efficient layout for Chinese (using Cangjie input method) and Japanese (using Romaji). Neither of them requires more keys of those needed to type English. So no problem here.

Since the whole thing is AI based and the only difference is the input material if I understand it correctly, I reckon there's probably a simple way to reutilize the AI you've put a lot of effort into just with different input.

However, I barely have any knowledge in programming, let alone anything AI-related. I would really appreciate it a lot if you would like to guide me to reapply the same AI-based method for input material of other languages!

hi, small bug .... on mac OSX Catalina 10.15 shift comma and shift period have incorrect characters. ( Loving this over workman as I am relearning touch typing 👍 )

So I found your analysis interesting and, frankly, I'd hope right on board if the last line of your features was true, "Has letters ZXCV and S in their original positions". Unfortunately I'm seeing this in your layout image:

Was this not compared to QWERTY as the baseline for the originals as noted in the readme?

I'm trialing a Halmak layout that can work in Windows 10.
Can you approve a push request in the near future?

Hi, I was wondering if the algorithm only considered standard "rectangoloid" keyboards or also other layouts, i.e. those with staggered key columns, like those running around on r/ErgoMechKeyboards

Context: I'm currently getting a split keyboard ("ferris" keyboard) and I would like to know if I can trust Halmak to be the best layout for that configuration of keys

In Google Chrome, Command key combos are unmodified (using Halmak bundle).

In VS Code they are.

When I use halmak_no_qwerty keymap on Linux, the SHIFT key does nothing. Is there a way to troubleshoot that?

I wonder if it would be possible to add these 3 extra characters into a version (Å Ä Ö)? I've been using Colemak-SE for some years now, would be interesting to try something new!

QWERTY

Colemak-SE

https://github.com/motform/colemak-se

I love it. I'm still trying to learn the layout but I can feel the massive improvement over QWERTY. Great layout.

Now, for my idea, the G feels so much further than the Q on ortholinear keyboards so I'm considering swapping the positions of the two since the G is so much more common than the Q in the English language. Even on staggered keyboards I'm considering doing it for uniformity's sake. Any thoughts?

Background: Typed on a colemak ergodone (ergodox clone) for a few years, and the 'laptop-style' keys layout is really different , but it is worth pointing out nevertheless, especially to those who are interested in evolution.

So here it is; the accepted home row position is forced. Try it now, just lay your fingers where they want to rest according to their length , youll find that either the middle and ring fingers go on the top row (ring finger is kinda between the two rows for me), or the little finger slides down one row (this is what the ergodone encourages my hand to do, since on a 'regular' keyboard, moving the left little finger down puts it halfway between 'z' and shift, and the keyboard already moves the middle columns up a bit). If you are interested to research this, Id like to develop a layout with this approach.

I'm interested in your thoughts and opinion on revamping the numbers (and symbols) row, just like programmer dvorak, and if you would ever consider doing this? by either implementing it straight or in another alternate version.

Here's a picture of the programmer dvorak layout I took from wikipedia

Ah, and also, would swapping the placement of backspace and caps-lock (Kinda like colemak) be of any use?

just an observation how they are not close together in this layout

Help! I switched to Halmak on PC but can't find a way to get it to work on iPad Pro keyboard!

The theory behind Halmak got me to switch and now that I've developed some proficiency with it, I am enjoying it. That said, I am completely unable to swap layout muscle memory back and forth as some people report being able to do.
I've since worried about having to get a job where I have to share a machine with other people or are unable to switch layouts for security lockdowns... I tried to switch back and just couldn't. QWERTY sucks. I mean, I know that muscle memory is mostly gone, but it definitely feels like poor design... so I decided to stick with Halmak!

On PC I can hotkey back and forth between layouts with shift+ctrl if I need to.
On iPad I've found apps to swap the key placement of the custom On-Screen keyboards.
I need help making the stock iPad Pro keyboard work with Halmak.

Hi

Mind if I add it here?
http://www.keyboard-design.com/best-ansi-layouts-as-determined-by-keyboard-layout-analyzer.html

Will help if you can send me the KLA .json file then I won't have to redo it and possibly get it wrong.. :-)

Thanks, Ian

E.g. http://nikolay.rocks/categories/optimal+keyboard is showing a Heroku error message (maybe because they shut down their free tier?).