Comments with Special Charecter

[fifi]

Hi
Could it be that the db doesnt work correct with special charecter (umlaute), äöüß,..
like the comment on my page: www.fifi.at on the first picture. i also saw that when i give the picture a description with such charecter rss doesnt work. i know that such charecter are not used in us.

regards fifi

[GeoS]

Which version of PP do you use?
Do you post images with character encoding set to UTF-8 or Auto-Detect?

[Connie]

I am sure you have not PP 1.5 active
PP 1.5, which is BETA, has more support of Umlaute, because in all versions we are more and more finetuning that

There were 2 small problems still open with PP 1.5 BETA (double quotes and apostrophes in Image title) and these will be fixed by the next release

so upgrading from 1.4.3 to 1.5BETA would help a lot

[fifi]

I am sure you have not PP 1.5 active
PP 1.5, which is BETA, has more support of Umlaute, because in all versions we are more and more finetuning that

There were 2 small problems still open with PP 1.5 BETA (double quotes and apostrophes in Image title) and these will be fixed by the next release

so upgrading from 1.4.3 to 1.5BETA would help a lot
Im using pp1.5 beta.
but mean not the picture name, i mean the COMMENTS to the pictures. Have a look at my site (www.fifi.at (http://www.fifi.at)) the comments of the first pictures:

dein künstlerisch wertvollstes bild!

den tiefenschärfenbereich hättest Du etwas größer wählen können, damit das "cold" auch scharf kommt...
Herwig @ 2006-01-25 19:03:57

regards

[GeoS]

It can be DB char encoding settings error.

There is general problem with special chars :/

[Connie]

I checked the HTML-code of the commentspage and it has UTF-8, so it should be ok, but it is not

there can be problems with the database as well
which characterset is defined for the tables? You can see that with PHPAdmin for example

I saw other points, which does not belong to the problem, but:

the comment-popup-template has the following header-tag:
<link rel="service.feed" type="application/x.atom+xml" href="<ATOM_AUTODETECT>" title="Fifi's Pictures of the Week" />

a) this belongs to image_template.html and not to comment-template
b) it should be
<!-- Link for ATOM feed autodiscovery -->
<ATOM_AUTODETECT_LINK>
<!-- Link for RSS feed autodiscovery -->
<RSS_AUTODETECT_LINK>

c) <IMAGE_THUMBNAIL_ROW> is for image_template, not comment-template as well

please do this finetuning and good luck with the database encoding!

[fifi]

Thanks for your info, where should i look in the phpmyadmin? the comments table (message field) is set to TEXT,
the other code you sent i dont understand really, this site is a template so i didnt modified anything in on the commants site.

regards fifi

[Connie]

Fifi,

1) the template is not ok, but you can open them in a editor and correct the lines

nobody ever swore that templates are without mistakes ;=)

2)http://www.bildgier.de/bilder/screenshot.jpg

tell us what you see in the colon "Collation"

[fifi]

I cant see the row:

http://www.fifi.at/screenshot.jpg

[Connie]

ah, so you have a different version, release of PHPAdmin installed...
it was a try, to find out with which character set the database is installed

can you ask your hoster?

[lilactree]

Hi,
i am experiencing the same problem with any Umlauts in the comments as well as in the info ever since i upgraded to pp 1.5
as far as i am aware, i do have all settings to utf-8 (since kde is prefering that)
in version 1.4.3 all characters were encoded properly.
thank you already for your help,
christoph

--
www.lilactree.de/blog

[raminia]

you have problem with new posts or older posts?

add line $str = UTF8_encode($str); to clean function in file includes/functions.php
and also add line $str = UTF8_decode($str); to pullout function in side the same file.

actually the code in 1.4 was wrong but changing it has caused backward-incompatibility.

[fifi]

you have problem with new posts or older posts?

add line $str = UTF8_encode($str); to clean function in file includes/functions.php
and also add line $str = UTF8_decode($str); to pullout function in side the same file.

actually the code in 1.4 was wrong but changing it has caused backward-incompatibility.
I had the problem with new postst.

where should i enter this commands? i have made the changes in the functions.php file under:
function clean($str)
{
$str = UTF8_encode($str);
$str = addslashes($str);
return $str;
}

or should it be everywhere in the file?

[io]

hi

I've just upgraded PP 1.4.3 to 1.5 beta. That works well now.

But there is a problem on the past-posted comments' Japanese characters, I mean all Japanese characters that were posted in the past become garbled characters after upgrading PP.

Is there anything wrong on it?

[fifi]

Does anybody has a solution for the problem? it still exist in my 1.5 verion.

[GeoS]

Check if all files are up to date - if you did full update.

PS If you did any own modification make backup of it and try to replace all files to oryginal PP's.