3151: post-review is not supporting russial symbols for description and summary fields

in**@lawgu****** (Google Code) (Is this you? Claim this profile.)
Dec. 4, 2013 
What version are you running?

RBTools 0.5.2

What's the URL of the page containing the problem?

N/A

What steps will reproduce the problem?
1. setup RBTools
2. Run 

post-review --revision-range=100:104 --summary='Русский текст' --description="Русский текст" -p -d -o 


What is the expected output? What do you see instead?

Expect to see russian symbols

There are '?' symbols  - instead it

What operating system are you using? What browser?

Chrome, workstation OS = Win7



Please provide any additional information below.

In debug mode can see that symbols are not processed correctly. Please see attachments.
#1 in**@lawgu****** (Google Code) (Is this you? Claim this profile.) 
updated attachments
  • +
    screen1.png
    None
    +
    log.txt 
    c:\ART-QMS>post-review --revision-range=100:104 --summary='Русский текст #1' --description="Русский текст #2" -p -d -o
    >>> RBTools 0.5.2
    >>> Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]
    >>> Running on Windows-7-6.1.7601-SP1
    >>> Home = C:\Users\AXname\AppData\Roaming
    >>> Current Directory = c:\ART-QMS
    >>> Checking the repository type. Errors shown below are mostly harmless.
    DEBUG:root:Checking for a Subversion repository...
    DEBUG:root:Running: svn info --non-interactive
    DEBUG:root:Running: diff --version
    DEBUG:root:repository info: Path: https://vcs1-m.artezio.ru/svn/repos/ART-QMS, Base path: /trunk/art-qms/Wiki-PM-Cards-n
    otifications-plugin, Supports changesets: False
    >>> Finished checking the repository type.
    DEBUG:root:Running: svn propget reviewboard:url c:\ART-QMS
    >>> HTTP GETting api/info/
    DEBUG:root:Running: svn st
    DEBUG:root:Running: svn diff --diff-cmd=diff -r 100:104
    DEBUG:root:Running: svn info test/rev
#2 in**@lawgu****** (Google Code) (Is this you? Claim this profile.)
chipx86
#3 chipx86 
This is generally caused by your database not being set for UTF8. Many MySQL installations, for instance, default to a latin1 encoding.

There are guides for all major databases on converting to UTF8, which you can follow to resolve this issue.

Assuming MySQL, you should be able to do a mysqldump to a file, make a backup, edit the table definitions to use utf8 instead of latin1, and recreate your database from that dump.
  • +SetupIssue