school510587

Hi @jserv, I just follow the style of naming of chewing_new2. Actually I don't know how to select a meaningful name for chewing_set_logger2, because it may be too long. Do...

> A quick test showed that you might be able to do it with begmode/endmode: Yes, this is a quick solution, but it is not realistic to list all latin...

> 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. Latin characters includes...

> 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...

Hi @bertfrees, According to your suggestion, I create a file: ``` # zh-chardef.uti attribute latin A attribute latin B attribute latin C begmode latin 0 endmode latin 0 ``` I...

> `bin\lou_translate unicode.dis,zhcn-g1.ctb,zh-chardef.uti` I tried this command to translate the same input, and the result was: `⠌⠲⠁⠒⠂⠓⠢⠂⠀⠠⠠⠁⠃⠉⠀⠀⠓⠒⠆⠵⠪⠀⠊⠁⠅⠊⠄⠐⠆` There are double spaces after "⠠⠠⠁⠃⠉`, which should not be accepted by the...

Hi @bertfrees, > It's because you can't insert something at the very end of the string. If you translate "5⅔ " (with a space at the end) you'll see that...

Hi @bertfrees, I can't figure out more appropriate way to satisfy the requirement. There is a hard-coded solution as follows. ``` noback context _1$d["\x2150"] @456-1456-2-34-2356-456-3456 noback context _1$d["\x2151"] @456-1456-2-34-35-456-3456 #...

Hi @bertfrees, OK, thanks! The expected output `5_?2/3_#` is generated. What is the function of the underscore before $d? I have difficulty to search it in the documentation.

Hi @bertfrees, Then, why is there no brackets around %FRACTION?