View Full Version : Strange signs in the database (å,ä,ö)
Anonymous
03-26-2005, 03:43 PM
For some strange reasons the information in the MySQL Database the swedish letters å, å, ö is replaced with strange signs like Ã¥ for å and ä for ä.
Is there any way to configure the script to show the letters correct in the database?
Connie
03-26-2005, 04:00 PM
dear guest,
we worked hard on that and the new version will be completely clean with special characters etc.
everything, every text will be in UTF-8-format
in the moment, as the new version will be released very soon, there is only one way to get clean entries: don't use the "plain" characters, but enter "html-encoded" characters
I know, that is awful, and that is why I worked a lot to repair this :wink:
Anonymous
03-26-2005, 06:39 PM
So in the next version i will be able to enter "plain" characters? Or will i still be able to use "html-encoded" characters?
How soon will the next version be released?
Will it be possible to use locale names of day. I'd want the script to write out Måndag rather then Monday.
dear guest,
we worked hard on that and the new version will be completely clean with special characters etc.
everything, every text will be in UTF-8-format
in the moment, as the new version will be released very soon, there is only one way to get clean entries: don't use the "plain" characters, but enter "html-encoded" characters
I know, that is awful, and that is why I worked a lot to repair this :wink:
raminia
03-26-2005, 07:49 PM
you'll have them all!
I've just compiled these features which are available with Connie's great efforts into the (beta) version. It is in the final test phase. If you want to have this beta version please PM me.
miledd
03-26-2005, 07:54 PM
That would be nice. I'll send you a PM.
you'll have them all!
I've just compiled these features which are available with Connie's great efforts into the (beta) version. It is in the final test phase. If you want to have this beta version please PM me.
geoff
04-15-2005, 08:41 AM
I still get these strange characters with 1.4. Using swedish characters (language is set to swedish in pixelpost). Any ideas. What settings do I have to set in PHP, Apache, MySQL ? Thanks
You've got it in old posts or in new made??
What MySQL DB setting do you have??
What browser do you use??
What is URL to see this in action??
I can tell that I've got DB with such settings:
character set client latin1 latin1
character set connection latin1 latin1
character set database latin1 latin1
character set results latin1 latin1
character set server latin1 latin1
character set system utf8 utf8
collation connection latin1_swedish_ci latin1_swedish_ci
collation database latin1_swedish_ci latin1_swedish_ci
collation server latin1_swedish_ci latin1_swedish_ci
and there is no problem with UTF-8 caused by MySQL.
On 2 blogs which I've tested it (with PP 1.4 on board) everything was OK (with RU, DE and PL national special characters).
geoff
04-15-2005, 10:20 AM
Pixelpost 1.4
MySQL 4.0.22
PHP 4.3.11
Apache 2.0.52
In new made posts, browser: Firefox.
Check out http://kling.mine.nu. At the bottom of image text you se the strange characters. Should be å ä ö Å Ä Ö
Now I know that in current downloadable version is problem in admin side with commenting persons name.
In image "Text / description" I don't see any problems.
When did you made last update of PP (date of last download of PP package)?
geoff
04-15-2005, 11:16 AM
Now I know that in current downloadable version is problem in admin side with commenting persons name.
In image "Text / description" I don't see any problems.
When did you made last update of PP (date of last download of PP package)?
The strange characters are in the <IMAGE_NOTES> tag. Below "Cirera - Roadtrippin'" in the aformentioned webpage.
The downloaded PixelPost is from april 11th.
EDIT: Another thing/question: What version of MySQL do you have, and how did you list the variables you posted before?
MySQL 4.1.8
All stuff I got from phpMyAdmin 2.6.2-rc1.
I found problem with UTF8 support and now we are working on solution.
PS Now on main page in newer version of PP dated on 13.04.2005 :) Try it.
geoff
04-15-2005, 11:43 AM
MySQL 4.1.8
It seems that MySQL < 4.1 handles character sets very differently from MySQL 4.1 and up.. that might be the problem.
Connie
04-18-2005, 02:33 PM
Geoff,
I am watching your photos and I do see really good swedish characters
which image has the problem?
I see that your template has the right UTF-encoding
but is your browser detecting the codepage ok?
did you check that?
please tell me the URL of the site with the wrong characters
geoff
04-18-2005, 02:59 PM
Geoff,
I am watching your photos and I do see really good swedish characters
which image has the problem?
I see that your template has the right UTF-encoding
but is your browser detecting the codepage ok?
did you check that?
please tell me the URL of the site with the wrong characters
The "good" characters are html-coded (&auml; etc). I've added what should be å ä ö Å Ä Ö to the current (Blue sign) page now. Check it out. I've checked and the characters are garbled in the database so the problem is inserting the characters to the database.
Connie
04-18-2005, 06:49 PM
Geoff,
no, thats not right. The data which goes into the database is encoded and recoded, so the data in the database is not the same as the data at the webpage
when I look at my website, the characters are ok
when I open MySQL with PHPAdmin and look at the entries, the data is strange
I checked your website now and I did what I asked you: I made my browser either autodetect the character encoding or use UTF-encoding, and what did I see???
http://www.photografitti.de/bilder/king1.jpg
http://www.photografitti.de/bilder/king2.jpg
do you believe me now? It#s not a mistake of pixelpost at all
it happens that the server overwrites the character encoding settings of a website (your template uses UTF-8 encoding in the header)
so the server delivers wrong code and automatic detection gets wrong results
but configuring the browser to read UTF-8, you get the right encoding as my screenshots show..
nothing is wrong, everything is ok (at our side..)
by the way, please change
<link rel="alternate" type="application/rss+xml" title="kling.mine.nu - RSS feed" href="/index.php?x=rss"> to
<link rel="alternate" type="application/rss+xml" title="kling.mine.nu - RSS feed" href="/index.php?x=rss" /> in your template (closing slash)
that was a mistake I made with the templates :cry:
Connie you gave me idea what can be a reason of it.
At many servers in php.ini admins uncomment some of lines near 413:
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"
If they uncomment default_charset then all content will be sent with this encoding excluding scripts in which you send correct header:
<?
header("Content-Type: text/plain; charset=utf8");
?>
It would be the best to send this header always before sending any content of PixelPost. This should give 100% of correct Charset used by browser.
doffer
04-27-2005, 05:10 PM
Hi GeoS! Thanks for answering my other post, but i can't figure this out... I've read through this thread but don't really understand it... An explanation of what do would be highly appreciated :)
OK.
Your server sent all PHP data as ISO-8859-1. You can tell to the ISP, that he should change php.ini file and get this (lines near 413):
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"
If he can't do it then you must add this as first line in index.php (after <?):
header("Content-Type: text/plain; charset=utf8");
doffer
04-28-2005, 05:25 AM
I've done it now, and my code looks like this:
<?php
header("Content-Type: text/plain; charset=utf8");
/*
Pixelpost version 1.4.1
index.php version 1.7
Pixelpost www: http://www.pixelpost.org/
Version 1.4.1:
Developer Team:
Ramin Mehran, Connie Mueller-Goedecke and Robert Prouse
Version 1.1 to Version 1.3: Linus
....
....
But of some reason, it only displays the HTML code when i open the index.php from the server... Knoy why?
<?php
header("Content-Type: charset=utf8");
/*
Pixelpost version 1.4.1
index.php version 1.7
....
....
Do it like this. It should be OK.
doffer
04-28-2005, 02:06 PM
Splenid! Works right now, and everything is cool :D
Of some reason, the page showed up as normal and with those special caracters in IE, but it only showed text in FF. Might the reason be "text/plain"?
header("Content-Type: text/html; charset=utf8");
doffer
04-28-2005, 03:39 PM
Hi again! I were just told that my side was "fucked up" and I didn't understand, because it worked fine for me :p Then i took a second look at the header code, and thought something like... Strange, it doesn't looks right... And when i opened this thread the answer were there even before i asked! Great, thanks :)
smlgphotos
06-11-2005, 04:13 AM
I'm having touble with visualex not updating as well and I inserted the above line of text into my index.php file. Now when I try to load my site, it asked me if I want to download the index.php file... Help!
It seems that your your machine doesn't treat index.php as PHP script (or don't execute it).
smlgphotos
06-11-2005, 01:50 PM
It was working fine until I added
header("Content-Type: text/html; charset=utf8");
to it. Is there a reason why that might have "broken" it?
smlgphotos
06-11-2005, 02:31 PM
I just removed the line and it seems to work fine. :-)
So don't add anything if it's not necessary & you don't know what your are adding!!
rollinger
04-06-2006, 11:57 PM
It works ..it works it works. Since three nights im searching the whole web for this problem. And now it works!
Now I searching for an beer and i will salute you!
Thanks
rollinger
04-07-2006, 11:21 AM
Im back again.
The problems with the Umlauts are away. But now there is in this way a new problem.
Sound funny but IE could not parse the page. IE try to download the index.php!
I look around and found that the problems come from the MIME things or so. Opera, Mozilla my page have no problems. I read something that the problem is that IE can not work with this xhtml.
Some hints for me? What can i do? Pardon, i have no idea by myself.
Thanks
Connie
04-07-2006, 06:28 PM
Rollinger,
first: congratulation that it works for you
second: this is the old dilemma: you must either accept that IE is not presenting how you want it to be or you must "down-code" your code to have it compliant with IE, too
we all know that IE is ... but what can we do?
At my place all is OK and IE can handle content of PixelPost without any problem.
Please give us link to code which makes to you problems.
vBulletin® v3.7.3, Copyright ©2000-2013, Jelsoft Enterprises Ltd.