Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] unable to create local copy utf8 encoded Japanese MySQLdata
- Date: Tue, 14 Feb 2006 14:15:25 +0900
- From: Josh Glover <jmglov@example.com>
- Subject: Re: [tlug] unable to create local copy utf8 encoded Japanese MySQLdata
- References: <43F1519E.4010403@example.com>
On 14/02/06, Dave Gutteridge <dave@example.com> wrote: > Most of the Japanese text shows up readable. Some of it, however, shows up as coded > numbers (I'm not sure what the term is when utf displays this way): > メーン・ I think this might be "legacy" data, > held over from the days when MySQL did not have utf8 support. I believe these are known as Unicode entities. If you can detect them in the database, I am sure there is a way in (pick your P) Perl, Python, PHP (or Ruby, etc.) to read them as entities and write them as proper Unicode characters. Try looking at this page for ideas: http://cpan.uwinnipeg.ca/search?query=entity -Josh
- Follow-Ups:
- Re: [tlug] unable to create local copy utf8 encoded Japanese MySQLdata
- From: Edward Middleton
- References:
- [tlug] unable to create local copy utf8 encoded Japanese MySQL data
- From: Dave Gutteridge
Home | Main Index | Thread Index
- Prev by Date: [tlug] unable to create local copy utf8 encoded Japanese MySQL data
- Next by Date: Re: [tlug] unable to create local copy utf8 encoded Japanese MySQLdata
- Previous by thread: [tlug] unable to create local copy utf8 encoded Japanese MySQL data
- Next by thread: Re: [tlug] unable to create local copy utf8 encoded Japanese MySQLdata
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links