mafiltenborg

I've had that thought. I know very little about the whole 'active HTML content' scene and wanted to start out by investigating if someone had already made provisions for language-handling along those lines. Not. Modding the code is a logical next step. Albeit a nonideal way of doing it as I'll effectively be making a fork which I'll then have to maintain myself. Oh well.

Right then. Working happily with the nice encoder script. Works beautifully. But... I'm not a native american-speaker, and my PC is not setup with US keyboard. So, I got hold of the BashBunny language json file and entered that by cliucking the "Change keyboard layout" button, search up the relevant file and select it. In my case 'dk.json'. Now scripts work as intended. Nice However, re-selecting dk.json on every Duck Encoder start gets old really quickly. Is there a way to automate selection of a language different from US? Add <path-to-language.json> as parameter or similar?