oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

2013-10-22 Thread wgw
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

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

2013-10-23 Thread Edward K. Ream
On Wed, Oct 23, 2013 at 12:03 AM, wgw 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 ha

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

2013-10-23 Thread wgw
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

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

2013-10-23 Thread Edward K. Ream
On Wednesday, October 23, 2013 12:43:08 PM UTC-5, wgw wrote: > > 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. > Thanks. If possible, please submit the smal

Re: oops! unicode error after update to Leo 4.11a3, build 6172, 2013-10-22 19:33:55

2013-10-23 Thread wgw
I put the bug report in, but I'm not sure what "smallest files (public and private)" means (sorry!). File? Does that mean a full leo file or just the node? To recreate the problem, all I need is an @shadow node with é or à etc... Pretty simple! Public and private? I'm assuming that "public an