Skip to content

feat: name a UTF-8 locale - #7

Merged
vitramir merged 1 commit into
mainfrom
set-a-utf8-locale
Aug 9, 2026
Merged

feat: name a UTF-8 locale#7
vitramir merged 1 commit into
mainfrom
set-a-utf8-locale

Conversation

@vitramir

@vitramir vitramir commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

ubuntu:24.04 names no locale, so glibc falls back to C, which cannot decode UTF-8. Every byte of a typed accent or Cyrillic letter reaches zsh's line editor undecodable and it renders each as <ffffffff> — typing привет ç in a sandboxes-app terminal produced fourteen of them.

C.UTF-8 is built into glibc 2.39, so no locales package and no locale-gen.

Reproduced on ubuntu:24.04 + zsh through a real pty:

without LANG:  <ffffffff><ffffffff><ffffffff>... (14)
LANG=C.UTF-8:  привет ç

agynio/terminal-proxy#9 defaults LANG for terminal sessions, which covers images we do not build. This covers the paths that are not terminal sessions — agent processes and EXEC sessions.

ubuntu:24.04 names no locale, so glibc falls back to C, which cannot decode
UTF-8. Every byte of a typed accent or Cyrillic letter reaches zsh's line
editor undecodable and it renders each as <ffffffff> -- typing "привет ç" in a
terminal session produced fourteen of them.

C.UTF-8 is built into glibc 2.39, so this needs no locales package and no
locale-gen. Reproduced and confirmed fixed on ubuntu:24.04 + zsh driven
through a pty.

terminal-proxy defaults LANG for terminal sessions too, which covers images we
do not build; this covers the paths that are not terminal sessions.
@vitramir
vitramir merged commit 80ca054 into main Aug 9, 2026
3 checks passed
@vitramir
vitramir deleted the set-a-utf8-locale branch August 9, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant