Bert Frees
Bert Frees
Update: I read your update :-) What makes most sence I think is to delete the .tbl file and move the second include rule to the .ctb file.
Superceded by https://github.com/liblouis/liblouis/pull/1584.
I need to figure out the name and possible values of the new metadata field, and maybe I can look at "fix the table resolver".
Let's add two new metadata fields to the tables: `#-encoding` and `#-unicode-range`. Encoding needs to be one of: - `utf-8` - `iso-8859-1`, `iso-8859-2`, etc. - `ucs-2le` - `ucs-2be` - `ucs-4le`...
`#-encoding` is for specifying the encoding of the file. Just like you have an encoding field in HTML files, HTTP headers, etc. > I'd rather keep it simple and assume...
A downside I can think of is that the expectation will be that for forward translation, `include` rules with `noback` are completely ignored. However that is not what the simple...
Having two tables which forward translate the same but backward translating using one of the scripts makes sense indeed!
@readmemyrights I have made some comments on the PR.
Nice. I had thought of m4 (and other general-purpose macro languages) too, but didn't really explore it I think. If this solution really appeals to you, I guess we can...