Maybe feed your templates through a call to unicode.decode, with the errors arg set to 'replace'? This will replace all sequences that can't be decoded with a '?'. At least that lets you render the template. Depending on how far you want to go, you could also write your own error handler and replace the '?' with whatever you want, including a hot pink flashy exclamation point. You could automate this by writing your own template loader.
On Mar 19, 2:44 pm, Steven L Smith <ssmit...@naz.edu> wrote: > We have a freelance designer that, for various political reasons, we need to > give access to our templates directory. The problem is, he frequently pastes > from Microsoft Word, and other sources, and then we're seeing HTTP 500 errors > because the output contains unescaped UTF-8 / unicode characters. > > For example, "UnicodeDecodeError: 'utf8' codec can't decode byte 0x94 in > position 30076: unexpected code byte". > > Is there a way to prevent these errors, other than revisiting the level of > access we give folks like this? Some kind of middleware that would filter > these characters out? Some kind of way to replace weird characters with a > bright pink blinking exclamation point? Something else? > > Thanks! > > Steven L Smith > Web Developer > Nazareth College of Rochesterhttp://www.naz.edu/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
