On Jul 30, 7:28 pm, loretta <[email protected]> wrote:
> On Jul 28, 5:48 pm, "Ville M. Vainio" <[email protected]> wrote:
>
> > On Tue, Jul 28, 2009 at 6:43 PM, loretta<[email protected]> wrote:
> > > So, my sitecustomize.py looks like this:
> > > sys.setdefaultencoding( "iso-8859-15")
>
> > Alright, remove this.
>
> > The problem with hacks like this is that they may make stuff that
> > shouldn't work appear to work, and it makes programs on your computer
> > work differently from the same program on other people's computers,
> > making bug tracking harder.
>
> > If everyone hasn't yet removed all custom hacks from their
> > sitecustomize.py, please do that now ;-).
>
> Did a sys.setdefaultencoding( "utf8") in my sitecustomize.py a few
> days ago (didn't dare yet to go back to ascii, because of troubles in
> the past) and held my breath for 4.6.1 (still 4.6.0-rc1 here).
>
> Deleted my Leo settings.
> Installed Leo 4.6.1 over the prev. version (BTW on Linux install isn't
> executable, had to chmod it).
> No changes in Leo settings.
> Opened workbook.leo.
> Inserted umlauts and copied the node and pasted it as clone.
> Umlauts still there.
> So, everything seems okay :-).
>
> However, I am not sure what to do with my production Leo file, which
> is a iso-8859-1-file.
> I'll try the following:
> Dont't change Leo settings wrt encoding.
> Use nano to change the first line of my production Leo file so that it
> is a utf-8-file.
> Load it into Leo.
Leo changed the 1st line into utf8 by himself.
Loretta
>
> > --
> > Ville M. Vainiohttp://tinyurl.com/vainio
>
> Loretta
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
