Koichi Murase

So there is still an issue with `LC_CTYPE=C` in Termux. The content of the error message *"The locale 'en_US.UTF-8' (LC_CTYPE) seems broken"* is actually wrong in Termux. [The code to...

Specifically, Termux produces "1" instead of the expected "3" with the following command, which is wrong. ```console $ (LC_CTYPE=C; a=$'\xE3\x81\x82'; echo "${#a}") 3 ```

The current status of the locale support by Termux is really unclear, so I raised a discussion at https://github.com/termux/termux-packages/discussions/23010.

> And after generating locales like in any GLIBC Linux distribution I'm not familiar with Termux. Could you explain it step by step? I seem to have been able to...

OK, Thanks. I could generate `en_US.UTF-8` by setting `PREFIX=$PREFIX/glibc`, editing `$PREFIX/etc/locale.gen`, and running `locale-gen`. Then what would be the next step? I tried to run bash with `LANG=en_US.UTF-8 $0`, `LANG=en_US.UTF-8...

Sorry, I actually generated `es_US.UTF-8`. It's quite confusing. I commented in `es_US.UTF-8` and commented out `en_US.UTF-8` and generated the locale again. It now works with `bash` inside `grun -s` (i.e.,...

> Normally `$PREFIX/glibc/bin` executables take over `$PREFIX/bin` ones. I only have `source /path/to/ble.sh` in my `~/.bashrc`, but `$PREFIX/glibc/bin` doesn't seem to take over `$PREFIX/bin` outside `grun -s`. I rebooted the...

Thank you for the hint. That will suppress the warning message, but I'm currently unsure if the original problem is indeed fixed by just setting the locale to `POSIX` or...

Regardless of the intent of the OP, the issue does exist.

I think you know it, but let me clarify that removing the function doesn't fix the original problem. It just hides the messages, but the problem still exists and may...