[mythtv] [mythtv-commits] Ticket #6026: mythfilldatabase problem in Japanese

Michael T. Dean mtdean at thirdcontact.com
Sat Dec 27 07:27:26 UTC 2008


On 12/27/2008 12:41 AM, MythTV wrote:
> #6026: mythfilldatabase problem in Japanese
>   

This is not a mythfilldatabase problem.

>  I am running mythtv on gentoo

It is the recently-identified system-configuration issue that Gentoo 
users are likely to have because of the defaults used when emerging MySQL.

>  linux /amd Athlon64X2 4850e
>  mythTV version is 0.21 (0.21_p18314-r1 in portage)
>  mysql is version 5.0.70
>
>  I have trouble showing Japanese in OSD
>  When I checked the values in mysql mythconverg.program,
>  I found most strings become '??????'
>
>  mysql status command shows following message:
>  #####################################
>  mysql  Ver 14.12 Distrib 5.0.70, for pc-linux-gnu (x86_64) using readline
>  5.2
>
>  Connection id:          22
>  Current database:
>  Current user:           root at localhost
>  SSL:                    Not in use
>  Current pager:          /usr/bin/less
>  Using outfile:          ''
>  Using delimiter:        ;
>  Server version:         5.0.70-log Gentoo Linux mysql-5.0.70-r1
>  Protocol version:       10
>  Connection:             Localhost via UNIX socket
>  Server characterset:    utf8
>  Db     characterset:    utf8
>  Client characterset:    utf8
>  Conn.  characterset:    utf8
>  UNIX socket:            /var/run/mysqld/mysqld.sock
>  Uptime:                 54 min 59 sec
>
>  when I run xmltv script tv_grab_jp from shell,
>  it returns xml where strings  are encoded in utf8
>  and which has right attribute 'encoding="UTF-8"' in root xml element.
>   

Just a couple of days ago I wrote up instructions on how to fix the 
issue, but I had planned to find someone in IRC to work through/"verify" 
the fix while I was around to help with issues before "announcing" the 
page on the -users list.  If you'd like to try it on your own (I have 
family visiting, so I don't know when I'll be available--and I'm almost 
positive you're not in the US Eastern time zone, anyway :), the 
instructions should be plenty detailed and should things fail, you can 
simply revert to your current configuration (the broken configuration) 
and continue to use Myth with the status quo.

The instructions for fixing the issue are at: 
http://www.mythtv.org/wiki/index.php/Fixing_Corrupt_Database_Encoding

I'll try to check in frequently on IRC (#mythtv-users) to see if there 
are any questions/issues (mention my nick--sphery--to ensure I see them) 
or feel free to respond to this e-mail--I'll check here, too.

Thanks,
Mike



More information about the mythtv-dev mailing list