>> So, which terminal-coding-system should we set by default when LANG is >> de_DE.UTF-8(en_US.UTF-8), iso-latin-1 or utf-8?
The terminal coding system does not necessarily depend on LANG. It seems that OSX's Terminal.app uses utf-8 by default, independently from any locale. Maybe it can be set to something else, of course. The problem I have now is: how can we detect when Emacs is running in Terminal.app. The TERM envvar is set to xterm-color, just like it is in several X11 terminals (which don't use utf-8 by default). > UTF-8 should be the natural/native encoding in dired-mode, shell, > shell-command-on-region, find-grep. file-name-coding-system on OSX already defaults to utf-8. > And a different object is Carbon Emacs! When running in Terminal.app, it should be no different. > Although too a Mac OS X binary it comes directly from Mac OS 9 and seems > to have no good idea of Unicode and UTF-8. I do not know from where you get this misconception. It handles Unicode *exactly* like the rest since it's using the exact same code. > It's fontsets are Mac-Roman oriented and it's close to impossible for > Latin scripts to use the whole spectrum. Maybe the default font settings need to be changed. > 'defaults read com.apple.Terminal StringEncoding' would reveal the default > encoding of Terminal, % defaults read com.apple.Terminal StringEncoding 2005-03-23 07:43:09.466 defaults[9360] The domain/default pair of (com.apple.Terminal, StringEncoding) does not exist % -- Stefan _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
