4 ms·

Don't complain. Contribute. I've worked on text rendering in the past, and the amount of subtleties in how each language is rendered and the exceptions/code pa

Don't complain. Contribute. I've worked on text rendering in the past, and the amount of subtleties in how each language is rendered and the exceptions/code paths that must be implemented to properly support said languages is not insignificant. Mind you, I say this as a native speaker of these languages. I don't want to imagine the amount of effort and work that would be required to support a language I don't speak. Doubly so if I'm not being payed for it. If you need support for a language you speak, help the developer by implementing and contributing the support yourself. PS: This isn't aimed at you specifically, but to those who criticize projects for lack of language support without understanding the effort required.

jake_the_third 8y ago
Folks, downvoting me isn't going bring your language any closer to being supported. If you have a sound argument against what I stated, please voice it instead.
- raphlinus 8y ago
  It's not useful advice. One does not simply add complex script support to some simplistic text drawing codebase. You have to take on dependencies to codebases at least an order of magnitude larger than GuiLite itself (wc harfbuzz/src/*.{h,hh,cc} is 86kloc and doesn't include the Unicode functions). Thus, it's a major architectural decision to support complex scripts at all, and to figure out how to do it.
  - jake_the_third 8y ago
    > One does not simply add complex script support to some simplistic text drawing codebase. We don't disagree here. This is the reason why rendering support for non-Latin scripts is usually abysmal on most software like op. It's why authors need help and usually won't do it themself. > Thus, it's a major architectural decision to support complex scripts at all, and to figure out how to do it. That's all the more reason to contribute to the project. > It's not useful advice. Perhaps it isn't very practical, but someone has to do it. It's also better than the alternative of just complaining without contributing towards a useful result.

jake_the_third 8y ago

Folks, downvoting me isn't going bring your language any closer to being supported. If you have a sound argument against what I stated, please voice it instead.

raphlinus 8y ago
It's not useful advice. One does not simply add complex script support to some simplistic text drawing codebase. You have to take on dependencies to codebases at least an order of magnitude larger than GuiLite itself (wc harfbuzz/src/*.{h,hh,cc} is 86kloc and doesn't include the Unicode functions). Thus, it's a major architectural decision to support complex scripts at all, and to figure out how to do it.
- jake_the_third 8y ago
  > One does not simply add complex script support to some simplistic text drawing codebase. We don't disagree here. This is the reason why rendering support for non-Latin scripts is usually abysmal on most software like op. It's why authors need help and usually won't do it themself. > Thus, it's a major architectural decision to support complex scripts at all, and to figure out how to do it. That's all the more reason to contribute to the project. > It's not useful advice. Perhaps it isn't very practical, but someone has to do it. It's also better than the alternative of just complaining without contributing towards a useful result.