WingIDE and encoding
WingIDE tries to be clever and interprets the charset I use in my HTML file. So this makes it pretty happy:
But if I want to use this:
... content="text/html;charset={{ DEFAULT_CHARSET }}" />
It tells me:
Unsupported encoding ‘{{ default_charset }}’ found in encoding comment — Wing cannot write this file until the comment is changed
Well that is pretty funny. So I can’t use the Django setting to determine my charset.
Even turning off WingIDE’s file property “Use charset from file” (or what it is called) doesn’t help. Just in case someone is struggling too.
Encolpe said,
February 2, 2007 at 7:29 pm
I haven’t this problem with page template editing.
Does it work if you add <?xml version=”1.0″ encoding=”utf-8″?> before your code ?
Wolfram said,
February 4, 2007 at 3:43 pm
The problem here is that would make IE work in quirks mode
I will try saving the file outside of wingide and not touch this piece, or generate the string “charset=” dynamically, which is absurd too :-). Its definitely a but in my eyes.