For those who may not know, the IPA (international phonetics alphabet) is widely used for writing out how words are spoken. It's very useful for linguists writing research papers, and for people looking to learn new languages!
As I wasn't satisfied with most IPA keyboards available, and wanted something that integrated well with fcitx, which I already have to use for japanese input, I re-implemented parts of the SIL IPA keyboard . It's not a one-to-one recreation (yet), because I needed somthing now rather than later, and took some shortcuts to put in all the features I personally needed, but it should be good enough for doing broad transcription of RP English. It should also be fairly trivial to hack in support for most character combinations.
Feel free to check out the git repo!
well, the point of flatpak is to have bundled dependencies so they run predictably no matter the distro
if one of your software's dependency gets updated, and your software isn't, you may run into issues - like a function from the library you're using getting removed, or its behaviour changing slightly. and some distros may also apply patches to some of their library that breaks stuff too!
often, with complex libraries, even when you check the version number, you may have behavioural differences between distros depending on the compile flags used (i.e. some features being disabled, etc.)
so, while in theory portable builds work, for them to be practical, they most often are statically linked (all the dependencies get built into the executable - no relying on system libraries). and that comes with a huge size penalty, even when compared to flatpaks, as those do have some shared dependencies between flatpaks! you can for example request to depend on a specific version of the
freedesktop SDK
, which will provide you with a bunch of standard linux tools, and that'll only get installed once for every package you have that uses it