Neil Hodgson wrote:
> JB:
>
> > as hypens (–) and apostrophes (’) are in an odd encoding. When passed
> > to the database using sqlalchemy they appear as – and other
> > characters.
>
> The encoding is UTF-8. Normally the best way to handle encodings is
> to convert to Unicode strings (unicode
JB:
> as hypens (–) and apostrophes (’) are in an odd encoding. When passed
> to the database using sqlalchemy they appear as – and other
> characters.
The encoding is UTF-8. Normally the best way to handle encodings is
to convert to Unicode strings (unicode(s, "UTF-8")) as soon as possible
I'm working on the webapp of our company intranet and I had a question
about proper handling of user input that's causing encoding issues.
Some of the uesrs take notes in Microsoft Office and copy/paste these
into textarea's of the webapp. Some of the characters from Word such
as hypens (–) and ap
