utf-8 commit messages are displayed as '????????'

Issue #441 resolved
jonigata created an issue

No description provided.

Comments (7)

  1. Marcin Kuzminski repo owner

    They must be not UTF8 than since rhodecode tries to decode them to unicode. What does hg log show up for it ?

  2. jonigata reporter

    According to HGENCODING:

    $ HGENCODING='' hg log

    ???????:   0:7aad14d17d8c
    ???:           hirayama
    ??:             Fri Apr 06 20:34:41 2012 +0900
    ??:             copy from gatherit
    

    $ HGENCODING=utf8 hg log

    チェンジセット:   29:d91d9e2367c9
    ユーザ:           hirayama
    日付:             Mon Apr 23 09:22:44 2012 +0000
    要約:             アイテムを持たずに出発することができなかったのを修正
    
  3. Marcin Kuzminski repo owner

    Can you push this somehow to demo.rhodecode.org so i can take a look at it and possibly debug the problem ? Thanks

  4. Kyrodan

    I had the same problem on Ubuntu 12.04 with the upstart scripts. If I started rhodecode via "paster serve production.ini" with my admin user on console all worked finde.

    The cause was a wrong/missing LANG environment variable in my upstart script(s). It now looks like this:

    description     "RhodeCode Mercurial Server"
    author          "Matt Zuba <matt.zuba@goodwillaz.org"
    
    start on (local-filesystems and runlevel [2345])
    stop on runlevel [!2345]
    
    respawn
    
    umask 0022
    
    env PIDFILE=/opt/rhodecode/data/rhodecode.pid
    env LOGFILE=/opt/rhodecode/data/rhodecode.log
    env APPINI=/opt/rhodecode/production.ini
    env HOME=/opt/rhodecode
    env USER=rhodecode
    env GROUP=rhodecode
    
    script
    
        if [ -r /etc/default/locale ]; then
            . /etc/default/locale
            export LANG LANGUAGE
        elif [ -r /etc/environment ]; then
            . /etc/environment
            export LANG LANGUAGE
        fi
    
        exec /opt/rhodecode/venv/bin/paster serve --user=$USER --group=$GROUP --pid-                                                                                                                       file=$PIDFILE --log-file=$LOGFILE $APPINI
    end script
    
    post-stop script
            rm -f $PIDFILE
    end script
    

    Changed the same for my celery upstart conf.

    @marcinkuzminski: maybe you can add/change it in the upstart samples and/or document this problem. It took several hours to find the problem. I searched the issue tracker and Google Groups to find some hints for this.

    Thanks, Daniel

  5. Log in to comment