Try to read in the attached file which contains only one line: 221 Ý The error message is quite long and I don't know how to copy it from the terminal window (it doesn't show up in the log pane). Rob......
On Monday, February 23, 2015 at 12:28:50 PM UTC-5, Largo84 wrote: > > That doesn't fix the problem. It appears to write correctly because when I > view the created file in a text editor (Notepad++), it shows up correctly > as ÷, but when read back into Leo it becomes ÷. I'm working from an > extended ASCII character set, maybe that's different from unicode (not sure > I really understand the difference). > Rob..... > > On Monday, February 23, 2015 at 11:52:28 AM UTC-5, Edward K. Ream wrote: >> >> >> >> On Mon, Feb 23, 2015 at 9:33 AM, Largo84 <lar...@gmail.com> wrote: >> >>> I have a number of @nosent ...xml files that are triggering node >>> recovery on read using the most recent Leo pull. It appears that it's >>> trying to change one of the characters (the divide-by character, summary >>> below): >>> >>> old: AS ÷ >>> new: AS ÷ >>> >>> Any idea why it's doing this or how to prevent it? >>> >> >> This is a standard unicode-related problem, having essentially nothing >> to do with @clean. The conversion happens when Leo *writes* the node, not >> when it reads it. >> >> Add the following line to the node:: >> >> # -*- coding: utf-8 -*- >> >> This tells Leo the correct encoding to use and all should be well. >> >> 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
221 Ý
