Hi all, I am experimenting some problems with the Carbon version of vim. I want to be able to write latin1 text files. In this respect I :set encoding=latin1Message 1 of 2 , May 14, 2002View SourceHi all,
I am experimenting some problems with the Carbon version of vim. I want
to be able to write latin1 text files. In this respect I :set
encoding=latin1 in my ~/.vimrc.
When editing files it turns out that they are encoded as MacRoman, and
not as Latin1. This is strange as Vim did not warn me that the specified
encoding was not used.
In this respect I tried to compile Vim, thanks to Benji Fisher patches,
with the iconv option. To do this I edited Make_osx.mak to add
-I/sw/include and -L/sw/lib in respectively include and library path
(/sw is where the Fink distribution is installed, it contains unix
libaries, programs and headers).
The problem is that I cannot go further in compilation, it breaks like
(spierre@localhost)-~/<1>vim61/src >> make -f Make_osx.mak
gcc -Wall -fpascal-strings -O3 -DMACOS_X_UNIX -DFEAT_PERL
-DFEAT_MBYTE_IME -DHAVE_PATHDEF -I/sw/include -I. -Iproto
-I/Developer/Headers/FlatCarbon -I/System/Library/Perl/darwin/CORE -c
auto/pathdef.c -o ObjX_UNIX/pathdef.o
./vim.h:533: warning: redefinition of macro OK
/sw/include/curses.h:205: warning: this is the location of the previous
In file included from ./os_mac.h:71,
/sw/include/curses.h:96: conflicting types for `bool'
/usr/include/gcc/darwin/2.95.2/stdbool.h:10: previous declaration of
make: *** [ObjX_UNIX/pathdef.o] Erreur 1
Has anyone had any success using Fink installed libraries with Carbon
«Life begins at the centerfold and expands outward.»
<http://www.type-z.org> -- Miss November, 1966
... Hmmm... When I write a file with encoding=latin1 the file is encoded as MacRoman. For instance in the command-line version of Vim which I have from FinkMessage 1 of 2 , May 14, 2002View SourceLe mardi 14 mai 2002, à 07:18 PM, the shrubber a écrit :
> In fact, in the underlying stuff, vim still THINKS it's using Latin-1 orHmmm... When I write a file with encoding=latin1 the file is encoded as
> Unicode, but it's using MacRoman for the display/input.
MacRoman. For instance in the command-line version of Vim which I have
from Fink the word "sécurité" is encoded as "s<E9>curit<E9>", while in
Carbon Vim I have "s<8E>curit<8E>". So as you say Vim thinks the <é>
keystroke is in fact the <8E> character in Latin1?
> I'm not sure if i'm making much sense, but the key idea is that on aI'm not familiar with Carbon, so I couldn't really help :(
> Unix level, the encoding stuff is right, it's just that we need to
> upgrade Vim from Quickdraw to something more Carbony.
> I can't help you otherwise, but i will hold you in high regard if you
> fix this (it's something specific to the Mac interface for vim), so that
> i can write en français, without running any transformations on my text.
I was thinking of autocommands using the iconv command-line tool and a
variable different from fileencoding as a turnaround, but your functions
seems fine :)
Q: What drug makes the experience of listening to you guys so much
better? herb just isnt enough for me anymore.
A: Sex. Most of our friends tell us it improves their listening
<http://www.type-z.org> -- Anonymous fan question to Lords of Acid