no, it's on musl, i just tested it with my patches, with vim, stripping will lead to unknown characters.
I mean, .mo files under zh_CN/ of vim is GBK set, while zh_CN/ of other apps is UTF-8 set, that meas there may be other apps like vim, we should be more cautious, add a check before map the .mo files, and fail non-UTF8 set in setlocale.
Btw, _nl_msg_cat_cntr & _nl_domain_bindings will block apps compiling with the native intl of musl, and after i added a dump for these two symbols, gnu tar showed me segfaults, because he passed a zero msgid1 causing __mo_lookup segfault, we should add a check in dcngettext to avoid it(if (!msgid1) goto notrans;):
#2 0x00007ffff7d82a6f in dcngettext (domainname=0x6737a0 "tar", msgid1=0x0, msgid2=0x0, n=1,
category=5) at src/locale/dcngettext.c:211