Bert Frees

OK, I must admit I only discovered your stuff recently and I hadn't really taken a closer look at it. But I think I'm starting to understand now. I can...

I'm glad that it works good for you too! > it is the most interactive and expressive way to write C code (with the c\* special form) I have yet...

(oops almost forgot about this, sorry) Okay, looks like you've already been putting much more thought in this then I did. I'm don't think I'm smart enough to give you...

See https://github.com/xproc/3.0-specification/issues/18#issuecomment-610250754 > Back in 2017 I have implemented a stack trace in our Pipeline version or calabash1, similar to how Jostein described it, and I've also extended the error...

A quick test showed that you might be able to do it with begmode/endmode: ```yaml attribute latin abcABC begmode latin 0 endmode latin 0 ```

Why is it not realistic? All Latin characters that have a character definition can be given a `attribute latin` rule as well. That seems perfectly feasible. In the future it...

Why not? I don't see any reason why it would be unreasonable. It will require a lot of rules indeed, but it's not something that would be hard to create...

> attribute latin ABCD...Zabcd...z # and hundreds of Unicode latin characters > attribute han 一二三四... # up to a billion characters Yes, except that you can also use one line...

You have to specify a display table, otherwise the translation table (zhcn-g1.ctb) will automatically be interpreted as display table (which results in nonsense). So try e.g. this: bin\lou_translate unicode.dis,zhcn-g1.ctb,zh-chardef.uti

There seem to be other rules in that table that result in spaces. Below is the result of running your example through the lou_trace tool: ``` 1. sign 中 34-256-1...