Ico Doornekamp

You'd have to make some changes to the code for this as well, at as this time the input scanning ignores key repeats; for example, the X11 input code `scan-x11.c`...

`allot`, `constant` and `variable` are pretty much standard Forthism, a good source to learn about these is the original Forth book by LEo Brodie: https://www.forth.com/wp-content/uploads/2018/01/Starting-FORTH.pdf Let me know if this...

You're right, not all of the example libraries have these comments - I'd be more than happy to take PRs for this though!

A viable alternative would be to have a whitelist of 'special' layers that will be exported if these exist, or export all layers that have a specific prefix or suffix...

> I will think about a way to realize this. Renaming layers seems a bit inconvenient. Maybe a new Setting that lets the user choos which layers should be exported...

I must admit I never got into the XML specs proper; the parsers I tried up to now were all happy to eat whatever UTF-8 I feed them, and I...

Right; that all makes perfect sense, I hadn't realized we were talking malformed file names here. The problem here is that duc is basically oblivious to encodings; it simply does...

Thank you for the PR, but this change does not really fix issues, it merely hides them by disabling a warning and no longer treating warnings as errors. I don't...

The file names are just the raw key scan codes, find yourself a scan code table somewhere on the internet and you should be good. Note that scan codes sometimes...

yeah, Tokyocabinet has been causing us a lot of headaches over the years; long ago this was chosen as the default db implementation for Duc to rely on because it...