Hi all,
Such problem will be solved with just making the source field as *blob*.
Please refer this link for detailed information.
http://www.srijan.in/blog/converting-latin1-charset-tables-utf8-data-set
On Fri, May 27, 2011 at 2:21 PM, Georg Schönweger <
georg.schoenwe...@gmail.com> wrote:
> Hi,
Hello Kay,
thank you for your tip!
Anyway if i connect to DB via cmd (with --default-connection=latin1 for
latin1 DB and --default-connection=utf-8 for utf-8 DB) i do not have
charset problems, all umlauts and special characters are ok.
As i mentioned earlier everything is ok expect 1-2 page visi
Hello Goerg,
write a small script (e.g. in PHP) which runs over all Tables and all
textfields in them and read out the data.
Use the php functions of mb_string or other charset helpers to force
your needed charset -> anyway i suggest you to switch to UTF8.
Test the script on a dev server before u
Hi Gert,
ok i see so you are upgrading your latin1 DB to real utf-8, right? .. i
don't want to do this and i can't make a new dump from the old server
because now the current DB is in use for some time and i can not drop
all new changes ..
Any hints how i can check if my DB is ok?
- Georg
Am 27.
Georg Schönweger schrieb:
Hallo Georg
you should dump your database with an option
look here (it is German)
http://software.rde.de/typo3-6-hilfsprogramme.html
goto Line/Element 108 : Dump old Database
watch the option --compatible
on my servers it did work fine.
--
mit freundlichen Grüßen
Hi,
after moving some of our Typo3 websites to a new server (from openSuse
11.0 to Ubuntu 10.04 LTS) i have strange behaviour with charsets. When i
call the Website in FE *sometimes* special characters are broken. With
sometimes i mean one visit per day. Then after a reload of the page no
charset
