2013-06-22 - Re: [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL
Header Data
From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 10ee38205bc090a568d378bd9ac8f73a824de0c5d042419fdb38441f0f501b9c
Message ID: <054.be6ebf98183d5ba7344a0d2c37959c2a@grasehotspot.org>
Reply To: <039.e7ee49450031548d3fc2e8d0c2427eae@grasehotspot.org>
UTC Datetime: 2013-06-22 06:58:08 UTC
Raw Date: Sat, 22 Jun 2013 13:58:08 -0000
Raw message
#47: Investigate UTF8 .vs. latin1 in MySQL
----------------------------+-------------------------
Reporter: tim | Owner: tim
Type: enhancement | Status: new
Priority: major | Milestone: 4.0
Component: Other Backend | Version: 3.6
Resolution: | Keywords: utf8, mysql
----------------------------+-------------------------
Comment (by stomper):
Yeah this is going to delay the korean translation I can give you. Right
now I have to get vietnamese characters working in latin1, which is going
to be fun.....
--
Ticket URL: <http://trac.grasehotspot.org/ticket/47#comment:1>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker
Thread
- Return to January 2012
-
Return to June 2013
-
Return to “GRASE Trac <tr***c@grasehotspot.org>”
- 2012-01-23 (Tue, 24 Jan 2012 00:17:43 -0000) - [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL - GRASE Trac <tr***c@grasehotspot.org>
- 2013-06-22 (Sat, 22 Jun 2013 13:58:08 -0000) - Re: [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL - GRASE Trac <tr***c@grasehotspot.org>