You have support for Korean and Japanese and Hebrew. How about the rest of unicode? My guess is you have a static or fixed size texture atlas. To put all 140k g

You have support for Korean and Japanese and Hebrew. How about the rest of unicode? My guess is you have a static or fixed size texture atlas. To put all 140k glyphs of unicode in a single texture atlas would require a 12k by 12k texture assuming 32x32 pixel glyphs. Plenty of devices don't support textures of that size and you'd be limited to just that size of font. Handling this in an actually "all of unicode" way so a user can read documents and type names in all the languages etc ("use facing apps") is not something Dear ImGUI as currently designed can handle AFAIK. It's not just a PR waiting to be written, it would be a large change. There are other issues with ImGUI paradigm as well. How does it handle accessibility for example. With OS level widgets the OS itself can read the content and deal with accessibility. Same with HTML. But with entirely internal data and just a list of GPU commands that's a huge open issue. I'm a HUGE fan of Dear ImGUI and have donated $$$$ to it. I think it's awesome. I think there is lots of room and inspiration to be had from Dear ImGUI for making it easier to make UIs. I've written articles on it (https://games.greggman.com/game/imgui-future/ https://games.greggman.com/game/imgui-future/) But I'm not blind to its current limits