don't decode messages

new db design and improved migration script. if you ran before the migration please remove you old logs.db as it is incompatible with the new one and rerun migration if you care about old logs. a print on show is on purpose, bonus of the first to traceback and give us the value of show that causes the tb. yea svn got unstable these days. sorry about that but big changes

in join_gc, when typing '@' focus goes to server_entry, and back in room_entry when I press backspace in enpty server_entry

in join_gc, when typing '@' focus goes to server_entry, and back in room_entry when I press backspace in enpty server_entry

fix so we store send stuff in the same place we store recv stuffed. todo: we need one more column in jids table called type_of_msg to store tc or gc and then migration needs fixing. this means people who migrated will have to migrate again by first removing the current log db. this also means until migration script is ready and after the migration u did logs will be lost

inform user about wiki page. give him to time to read the message and inform him he cancel and read wiki more carefully. start migration after 40 secs of first informative message

initial stuff at mark day that has logs. atm it is slow and has some bugs I will fix soon. I commit this nonetheless

add scripts/migrate_logs_to_dot9_db.py to makefile so we distribute it in snaps and releases. thanks Jim++!

add ACE log_contact_status_changes and expose to UI in advanced tab in misc. this replaces the previous options and imo is good to expose to that place (used to have log-related stuff)

sec text should not be escaped for pango as it is put in pango formatting. apostrophe etc show ok now in file req window

log system rewrite to use sqlite database instead of plain ascii files. this allows us to scale better (be faster), provide search in history, and save logs for JIDs that are non-ASCII. PLEASE read http://trac.gajim.org/wiki/MigrateLogToDot9DB