Hi, Take notice that there is also a 'fileencoding' setting in vim. When you create a new file in vim, 'fileencoding' will not be set and so it will take the current value from 'encoding'.
When you open an existing file, vim will try to determine its encoding and set 'fileencoding' accordingly. But be aware that if you change the 'encoding' the 'fileencoding' variable will not be affected. If you want to actually change the encoding of an existing file you must change the variable 'fileencoding' and save (:w) the file. Look at :help fileencoding and :help encoding for more details. You could also take a look at this script: http://www.vim.org/scripts/script.php?script_id=789 Cheers, Jorge On 7/30/06, Mikko Nylén <[EMAIL PROTECTED]> wrote: > > Thanks for all answers. I was able to fix the problem by starting over with > the django.po. May be the problem was that when I did start working with the > file, I didn't have set encoding=utf-8 and when I turned it on in the middle, > Vim didn't convert the characters to UTF-8. > > - Mikko Nylén > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
