[tex-live] fwd: \delta in overfull \hboxes screws up xterm

David Kastrup dak at gnu.org
Wed Jul 14 12:19:47 CEST 2004

Vladimir Volovich <vvv at vsu.ru> writes:

> "DK" == David Kastrup writes:
>  >> Or at least, TeX's output to *terminal* should honor the locale's
>  >> isprint() properties. All other output (to log files, \write,
>  >> \special, etc) MAY use 8-bit, if one wants to, but there's no
>  >> reason to insist on "pure 8-bit" for output to *terminal*.
>  DK> You mean, like AUCTeX which correlates the output of error
>  DK> messages on the terminal with input lines?
>  DK> Sorry, but when TeX is running inside of a TeX shell (writing
>  DK> into a pipe or pseudo terminal) there are valid reasons for
>  DK> wanting 8bit throughput.  So while we don't want a _default_
>  DK> print-through setting probably, we at least want an option to
>  DK> have the terminal output go through.
>  DK> It is not sufficient here to just have the log file work out: if
>  DK> I am using TeX in interactive mode, it is the terminal messages
>  DK> that I have to analyze since they are up to date and flushed.
> Shouldn't you then better have correct locale (LC_CTYPE) setting on
> your terminal, instead of unconditionally writing binary characters
> onto terminal?

LC_CTYPE is not a terminal setting, and you tell me what a correct
LC_CTYPE setting for Windows, MacOSX, HP/UX, Linux, Solaris in various
versions for a document including subchapters by different people
written in utf8, latin1 and applemac input encoding would be, even if
we stipulated that we wanted to goof around with the environment in
the first place.

> And what is the point to have "full 8-bit output" to terminal, even
> for all codes less than 32?

^^I is a valid input character.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

More information about the tex-live mailing list