Thanks! I was working in a2, I believe. not a3. So "previous" means way back when.
You know your code! The problem is only in the @shadow nodes. I will file a bug report. I also noticed a slightly odd file: stand_along_globals.leo. Should that be stand_alone_globals.leo ? Thanks for the quick response. B Le mercredi 23 octobre 2013 04:42:33 UTC-7, Edward K. Ream a écrit : > > On Wed, Oct 23, 2013 at 12:03 AM, wgw <[email protected] <javascript:>>wrote: > >> In the previous version, I had no problem writing unicode files (I'm in >> ubuntu 12.04, utf-8 everywhere). I did a bzr pull for the latest version >> of leo and now I'm getting : >> UnicodeEncodeError: 'ascii' codec can't encode character >> >> I must have overwritten something but not sure what: everything in my >> leosettings files is utf-8, and my ubuntu is utf-8. >> >> Any thoughts? >> > > According to the bzr logs, the last changes to leo/core/leoShadow.py > happened on 2013-09-12. These changes did indeed concern unicode. I > suspect, but do not know for sure, that what you call "the previous > version" dates from before Sept. 9. > > The change starts with the following:: > > # A massive kludge: read the file private file > # just to read the encoding. > > The read code than uses this encoding to reread the file. This fix may > indeed change the text. > > Presumably, Leo shouldn't crash no matter what characters you type. > Please file a bug report. > > Perhaps the new code, being more "correct" in some sense, may be more > sensitive to the absence of required @encoding directives. Adding same may > help. Or maybe there was just a botch in the fix ;-) > > HTH. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
