[melbourne-pug] Superscript chars are a pain

2020-03-07 Thread Mike Dewhirst
I'm now exclusively Python 3.6+ thank heavens but ... UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb3 in position 6500: invalid start byte It just so happens that is the superscript 3 character.  It also happens that superscript 3 displays correctly and works properly on Windows 10

Re: [melbourne-pug] Superscript chars are a pain

2020-03-07 Thread Mike Dewhirst
Oh well ... maybe it isn't Python's fault. I just looked at the data input file and found the ³ character in all places had been turned into a box. When I edited the boxes back into ³ it all went well. I used Filezilla to get the input files across so I'll focus on that next. Sorry to interrup

Re: [melbourne-pug] Superscript chars are a pain

2020-03-13 Thread David Micallef
Hi Mike I could be missing something though is there an opportunity to set the encoding when your reading the file. The default is utf-8 though you can set enociding to be the actual encoding of the file that you are reading. These file could be ISO-8859-1 or another variant. Cheers Dave On Sun

Re: [melbourne-pug] Superscript chars are a pain

2020-03-13 Thread Mike Dewhirst
+10:00) To: Melbourne Python Users Group Subject: Re: [melbourne-pug] Superscript chars are a pain Hi MikeI could be missing something though is there an opportunity to set the encoding when your reading the file. The default is utf-8 though you can set enociding to be the actual encoding of the file th