Currently, strings are used as specified in the configuration file and printed as-is into the JSON responses. This works fine with ASCII, but breaks when using anything other than that.
The easiest/cheapest (in terms of memory copies) method of solving this would be to JSON-encode these strings at configuration time and just use them like that. The command and layout names additionally will have to be URL-encoded for use in requests.
Currently, strings are used as specified in the configuration file and printed as-is into the JSON responses. This works fine with ASCII, but breaks when using anything other than that.
The easiest/cheapest (in terms of memory copies) method of solving this would be to JSON-encode these strings at configuration time and just use them like that. The command and layout names additionally will have to be URL-encoded for use in requests.