Re: gVim Windows binaries updated to 6.1.464

[<dig...@mi...>]

From: Christian G=C3=B6bel, Wed, 16 Apr 2003 10:04:45 +0200
> A 23:21 15/04/2003 -0400, vous avez =C3=A9crit :
> > Christian Goebel wrote:
> > >=20
> > > [encoding problems]
> >=20
> > Somewhere around line 90 in cream.vim, you'll find a line that
> > forces &encoding =3D utf-8, conditioned upon the developer var being
> > set. Uncomment that single line and restart to force this and let
> > me know if that solves the problem. You might also force the file
> > encoding for any specific file giving you problems, too,
> > especially if it was created in some other app.
>=20
> The line was uncommented - instead I commented it. Everything seems
> to work fine again.   Thanks a lot. I have never set the developer
> var - this seems to be the default setting? (I installed cream
> manually)

UGH! I apparently forgot to comment out the developer var, so
*everybody* who is using the manual install will have that enabled.
Meaning that the Cream Developer menu is exposed and script encoding
is forced to utf-8. A new fixed version is posted which simply
comments out what you found.=20


> By the way: The old text files work fine with the new utf-8
> encoding. That means when I open a file with accents everything
> looks normal.  The described problems appear when typing new text or
> when I try to copy/paste text from other programs.

I think that what has happened for you is that your digraphs changed.
Vim makes different ones available based on encoding. I'd appreciate
if you can test the &encoding=3Dutf-8 for me:

o Does the digraph listing under the Insert menu help at all?=20
o Does changing font help? (Is your font utf-8 compliant?)
o What is the result of :echo &encoding with the dev var commented?


> > UTF-8 encoding may become official next release. I wanted to wait
> > to test this for a while myself before making it official. The
> > next alpha already indicates &fileencoding in the status line and
> > has the beginnings of a menu for over-ride, too. UTF-8 will
> > someday solve a lot of problems, but many apps, fonts and docs use
> > other standards now so this may shock some people. ;) (Similar to
> > what I believe you are now experiencing! For example, the
> > "prettier" invisible characters will regress to "$" and ">". :(  )
>=20
> This is what I got, too with the utf-8 encoding - this is quite a
> pitty - because there are no indicators for blank spaces anymore
> (something I found quite useful for 'cleaning' the structure of a
> file)

Hmm... this works for me, it's now simply a period (".") character.


> Perhaps it would be useful for some people (like me) to offer the
> 'old' enconding in the  settings - menue ?  The problem decribed in
> my 'bug' report is quite anoying at least when you are working with
> French text on a Belgium keyboard.

Next release will have a menu to set fileencoding to any number of
selections (but not script encoding). It may be that your "other"
programs don't properly handle utf-8 and that we can't solve this in
Vim. Then letting you pick encoding via Cream would help, right? (But
I'd still be in favor of keeping script encoding to utf-8.) BTW, what
version/patch level of Vim are you using? There were some
encoding-paste fixes just a short while ago.


--
Steve Hall  [ dig...@mi... ]