I don't think you need that coding line any more. That was a Python2 thing. Python3 uses unicode/utf-8 automatically. FWIW, I generally (before the abbreviations) copied and pasted non-ascii characters from various web pages, and it's always worked well.
On Tuesday, January 10, 2023 at 11:53:41 AM UTC-5 jkn wrote: > Hi Edward > > On Tuesday, January 10, 2023 at 4:36:23 PM UTC Edward K. Ream wrote: > On Tuesday, January 10, 2023 at 10:31:02 AM UTC-6 jkn wrote: > > I *do* use Unicode, of course ... just not extensively within my Leo > notes, for instance. > > :-) > > I am not planning to use non-ASCII glyphs within my Python *code*, either. > > It's easy to allow Unicode within .py files. Just start `@file` nodes > with: > > @first # -*- coding: utf-8 -*- > > or just: > > # -*- coding: utf-8 -*- > > For other kinds of @<file> nodes. > > Edward > > Yeah, I appreciate that. I just choose not to have such characters in my > Python. > (I actually don't write much of my Python with Leo, but that's a different > matter... ;-/) > > Regards, J^n > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/334e20f3-8d50-4182-84f3-1c8b22958566n%40googlegroups.com.