On Mon, 2006-07-31 at 20:39 -0500, Jorge Gajon wrote:
> 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'.
Also the variable 'fileencodings' is import
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.
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
--~
On Jul 30, 2006, at 08:08, Mikko Nylén wrote:
Also, I'd like to ask how different timezones should be handled? I'm
building an application where it would be necessary for the users
to be able
to choose their own timezone to display date and time information
correctly.
One option would be,
On 7/30/06, Antonio Cavedoni <[EMAIL PROTECTED]> wrote:
> I don't know much about Vim, but it appears your ö and ä are entered
> with an encoding different than UTF-8. Python then tries to decode
> your characters thinking they might be valid UTF-8, but they are not,
> so it raises the UnicodeDeco
On 30 Jul 2006, at 14:08, Mikko Nylén wrote:
> I tried to change all 'ä's with \xe4 and 'ö's with \xf6 and with
> those I was
> able to make the messages compile. However, when trying to launch the
> built-in server, I get error saying "UnicodeDecodeError: 'utf8'
> codec can't
> decode bytes i
6 matches
Mail list logo
