At the moment, at least on Fedora, when logging in via login on console or with su, tlog is supplied with ASCII as the character encoding to use and aborts (because it only supports UTF-8). At the same time ASCII is not the actual character encoding to use, and the configured encoding is in fact UTF-8. This is due to Fedora (at least) setting it in /etc/locale.conf, to be sourced by shells when they read startup files.
This ad-hoc solution is leaving other programs, which are not prepared to interpret shell language (or even just the limited language of /etc/locale.conf) in the cold. Instead something like the Debian approach should be used. Debian sets locale using pam_env, which works for any program.
Find a way to read Fedora (and RHEL) locale settings in tlog, and/or change the way the distributions do it.
At the moment, at least on Fedora, when logging in via login on console or with su, tlog is supplied with ASCII as the character encoding to use and aborts (because it only supports UTF-8). At the same time ASCII is not the actual character encoding to use, and the configured encoding is in fact UTF-8. This is due to Fedora (at least) setting it in /etc/locale.conf, to be sourced by shells when they read startup files.
This ad-hoc solution is leaving other programs, which are not prepared to interpret shell language (or even just the limited language of /etc/locale.conf) in the cold. Instead something like the Debian approach should be used. Debian sets locale using pam_env, which works for any program.
Find a way to read Fedora (and RHEL) locale settings in tlog, and/or change the way the distributions do it.