| 1 |
maillog: 04/08/2005-19:35:01(-0700): Robin H. Johnson types |
| 2 |
> On Fri, Aug 05, 2005 at 11:28:46AM +0900, Georgi Georgiev wrote: |
| 3 |
> > > As a vim workaround, maybe force encoding=utf-8 in the gentoo filetype |
| 4 |
> > > stuff? |
| 5 |
> > But utf-8 is supposed to be autodetected, since the default |
| 6 |
> > fileencodings always contains utf-8, doesn't it? It is not |
| 7 |
> > autodetected only if the file is not *strictly* utf-8. |
| 8 |
> It sets 'fileencoding' correctly, but 'encoding' is not set at all. |
| 9 |
> |
| 10 |
> Here's the vim settings that I see after opening the file and running :set. |
| 11 |
> |
| 12 |
> autoindent hlsearch tabstop=4 ttymouse=xterm |
| 13 |
> backspace=2 ruler textwidth=80 viminfo='20,"500 |
| 14 |
> history=50 shiftwidth=4 ttyfast |
| 15 |
> commentstring=<!--%s--> |
| 16 |
> fileencoding=utf-8 |
| 17 |
> fileencodings=ucs-bom,utf-8,default |
| 18 |
> filetype=gentoo-metadata |
| 19 |
> suffixes=.bak,~,.o,.h,.info,.swp,.obj,.info,.aux,.log,.dvi,.bbl,.out |
| 20 |
> syntax=gentoo-metadata |
| 21 |
|
| 22 |
What does "set enc?" say? |
| 23 |
|
| 24 |
Anyway, setting enc=utf-8 when your terminal is using something else |
| 25 |
makes the output look like shit. Furthermore, you wouldn't be able to |
| 26 |
input any non-ascii characters anyway (or maybe you will, depending on |
| 27 |
your locale, but they would appear as garbage on the screen). If you're |
| 28 |
not going to go anywhere near non-ascii text it might be OK. |
| 29 |
|
| 30 |
I guess you're better off using gvim if "locale -k charmap" doesn't say |
| 31 |
UTF-8 in your term. |
| 32 |
|
| 33 |
-- |
| 34 |
-* Georgi Georgiev -* Each honest calling, each walk of life, -* |
| 35 |
*- chutz@×××.net *- has its own elite, its own aristocracy *- |
| 36 |
-* +81(90)2877-8845 -* based on excellence of performance. -- -* |
| 37 |
*- ------------------- *- James Bryant Conant *- |
Archives