Re: [vile] problem with 'wide characters' (utf-8) under macosx

[j. van den hoff]

forgot to Cc the list. sorry for the noise, brendan ....

On Sat, 06 Dec 2014 07:49:29 +0100, Brendan O'Dea <address@hidden> wrote:

> On 6 December 2014 at 09:39, j. van den hoff <address@hidden>  
> wrote:
> > [...] I want to use it in the native `Terminal.app' coming
> > with macos. here's the problem: despite `Terminal.app' being set up for
> > utf-8 character encoding, vile displays
> > non-ascii characters by their hexcode such as \u00E4. [...]
> Hi Joerg,
hi brendan,

> Could you paste the contents of the buffer produced by :show-variables
> when you are in a file which has such a problem?
sure. I've saved this list for _both_ cases, editing from within urxvt
(where everything is fine and
  from within `Terminal.app' (where it is displaying the utf-8 hexcodes). I
here only list the differences:

urxvt:                                          Terminal.app:
======                                          =============
$curcol = 1                                                  |  $curcol = 6
$encoding =                                                 |   $encoding = 
UTF-8
$lcols = 9                                                    | $lcols = 14
$locale = de_DE                                          |      $locale = UTF-8
$pagelen = 50                                              |    $pagelen = 56
$pagewid = 141                                            |     $pagewid = 181
$pid = 33249                                                |   $pid = 33243
$term-cols = 141                                           |    $term-cols = 181
$term-encoding = utf-8                            |     $term-encoding = locale
$term-lines = 50                                          |     $term-lines = 56
$wlines = 48                                                |   $wlines = 54

most of these differences are obviously irrelevant but the encoding
related values differ, too...
I think I will start to read up, what exactly they mean in `vile --help'
...

> The output of the locale command from the shell and the value of $TERM
> may also be useful.
the problem might lie in this area. in urxvt I get

LANG=
LC_COLLATE="C"
LC_CTYPE="de_DE.UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

where I explicitely set LC_CTYPE to that value in (the equivalent of)
.xinitrc so that it is defined when the x11 window manager starts up (but
is ignored, of course by Terminal.app...) in Terminal.app I get instead:

LANG=
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

which conforms to what I can select under "character encoding" in the
`preferences' settings of that program. so it's not exactly the same
locale but my (limited) understanding of these things is that "UTF-8"
alone should suffice and the country specfic qualifier (de_DE for me) has
not much of an influence? (and both terminals identify as xterm-color).
the strange thing is that several other editors
recognize these settings in a way that utf-8 is displayed correctly in
bother terminal emulators.

joerg

> --bod

--
Using Opera's revolutionary email client: http://www.opera.com/mail/