Future of musl locale/strerror(). In LC_MESSAGES=C, strerror(ENOENT) = ?
-
-
If including most localizations only costs ~1-2k that seems like a fairly small price pay for better internationalization support out of the box. Save a lot of developer time, and concern. But I guess embedded folks maybe against it.
-
Obviously things are oversimplified in a tweet. The question is whether to keep English-phrase error msgs in C locale or use the E* codes (more 'language-agnostic').
-
In the former case, it costs more size to make the translation framework clean. In the latter, making the translation framework clean also makes it smaller (and you can have English-phrase error msgs still in "en" locale, just not "C").
End of conversation
New conversation -
-
-
1k can be a breaking point in what I work with. We use musl because it's 1 readable (therefore trustable) 2. Because glibc wouldn't even fit
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.