Internal error when trying to save kn_IN letters

[vincentvikram@…]

Steps to reproduce the error:

1. I tried to save a section which had a kn_IN script characters and obtained the below error.
2. Removed the offending language characters and the content was saved.

Error Reproducible.

Traceback (most recent call last):
  File "/var/lib/python-support/python2.4/trac/web/main.py", line 387, in dispatch_request
    dispatcher.dispatch(req)
  File "/var/lib/python-support/python2.4/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/var/lib/python-support/python2.4/trac/wiki/web_ui.py", line 113, in process_request
    self._do_save(req, db, page)
  File "/var/lib/python-support/python2.4/trac/wiki/web_ui.py", line 239, in _do_save
    req.remote_addr)
  File "/var/lib/python-support/python2.4/trac/wiki/model.py", line 126, in save
    "%s,%s)", (self.name, self.version + 1, t, author,
  File "/var/lib/python-support/python2.4/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/var/lib/python-support/python2.4/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: character 0xe0b297 of encoding "UNICODE" has no equivalent in "LATIN1"

[Christian Boos]

Which db backend are you using? If it's MySQL, please check the db requirements listed in MySqlDb page, only utf8 charsets are supported.

[Christian Boos]

Was likely a problem with a non-unicode MySQL database.

Unicode issues with MySQL are believed to be fixed now when using recent 0.11-stable (≥ r7286) and trunk (≥ r7222) and the database was created according to the explanations found in MySqlDb.