Grognak wrote:You are likely saving as UTF-8 when you should be saving as ANSI.
Yes! I freakin' love you!
I'm pretty sure all those XML editors I have been trying (all of which failed, for reasons cited upthread) changed the format of my .append files without informing me/me noticing.
Back to work.
Contribute to help save the Whales from their various diseases! *DELAYED* Should release the skeleton with the main quests attached by the end of the week (By NOV 9)! *DELAYED* Don't listen to my dates! Things always seem to come up!
Grognak wrote:You are likely saving as UTF-8 when you should be saving as ANSI.
Silly question, but what is the difference in encoding between the two formats that causes this issue? Seems like something that could be easily checked/fixed within Python, since it looks to be happening fairly often. (Especially since UTF-8 is a more widespread/modern encoding standard than ANSI.)
Grognak wrote:You are likely saving as UTF-8 when you should be saving as ANSI.
Silly question, but what is the difference in encoding between the two formats that causes this issue? Seems like something that could be easily checked/fixed within Python, since it looks to be happening fairly often. (Especially since UTF-8 is a more widespread/modern encoding standard than ANSI.)
As far as I'm aware, it's an issue in every python program that doesn't use python 3.x.
Looks like the 'BOM' section indicates what you're talking about, with Python 2.x decoding UTF-8 byte-order marker as an actual character (and then sticking it back in to the new file), which then explodes FTL. Prolly can write a simple function that just takes a filename and reads/strips the BOM, closes the file, then returns a string of the contents.
But I think I can get around that. Another problem is that my Python install keeps giving me "/usr/bin/env python
: No such file or directory" whenever I try to open up the main.py file. Any workaround for that?
HeliosRX wrote:Another problem is that my Python install keeps giving me "/usr/bin/env python
: No such file or directory" whenever I try to open up the main.py file. Any workaround for that?
Trying change the shebang line (first line, the #!/usr/bin/env python) to