I've pretty much given up on creating any automation for converting the existing config files. Trying to pull codes out of the LIRC data is surprisingly painful, as I've probably explained earlier. With the amazing collection of settings, formats, and options available, no two LIRC config files are the same, even when they describe the same data. The JP1 data is somewhat better, but is split between two or three different competing formats (and has even less coordination than the LIRC does).

Moreover, I'm really not trying to do what either of these two groups do -- I don't want to bother trying to emulate individual remote controls. It is easy to see that many devices share the same IR "language", and I don't see why an intelligent remote control app couldn't take advantage of that fact. So I'm trying to create these "keysets", which are synthetic combinations of compatible remote control languages.

I guess, In short, you could say I'm playing around with the data as I enter it.

Once the backend code crystallizes a bit more, it should be easier to construct a method to enter in remote codes. But I don't think it will ever be as easy to do in Pierogi as it is with LIRC or JP1...