this! but also, I have grown so tired of UI toolkits launching with no plan for internationalization. and the bolt-on solutions that come after launch are inefficient because they're fighting against the framework's paradigms. toolkit authors have a responsibility to do better
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
one thing I haven't figured out how to resolve is that moving from Unifont to Noto as the built-in font in SolveSpace would increase the binary size by a factor of 20. it would be less of a problem if that wasn't one of the selling points of SolveSpace.
-
I think the underlying problem here though is "Noto sucks" because we already have a vector font with substantial CJK coverage and it's not 120 MB in size, but it's still a problem I don't know how to easily solve.
- 3 more replies
New conversation -
-
-
Or developers who only know European languages refusing to accept internationalization patches because it adds more dependencies or increases the binary size.
-
Most European languages don't fit ASCII though.
- 1 more reply
New conversation -
-
-
Is there good stats on this? Would be interested in learning more
-
The internationalization support for KDE is so large that Slackware has a separate packaging category for it.
End of conversation
New conversation -
-
-
IME when people say "bloat" they usually mean "features I don't use"
-
“Don’t use” or “don’t want”? Does all telemetry code take up a lot of space (either directly via increased executable size or indirectly via data files)?
- 4 more replies
New conversation -
-
-
If there's good reason to care about binary size (which... not sure?), couldn't one just split language packs from binaries and get both?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.