Re: Fixed dynamic chat bug regarding special characters

  • From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Fri, 4 Jul 2008 13:02:42 +0300

Well, when using UTF-8, you don't even need to use character entities. You can use simple UTF-8 chars and they display correctly.


Octavian

----- Original Message ----- From: "Bryan Garaventa" <bgaraventa11@xxxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, July 04, 2008 10:52 AM
Subject: Re: Fixed dynamic chat bug regarding special characters


Thanks, I'll look into it. I think I've stumbled across the problem, looks like the characters are being saved correctly, and also retrieved correctly, but the html entities are not being converted to html equivalents.

I found the page at
http://www.prolifique.com/entities.php.txt
which may help fix this, I'll play around with it and see if I can implement something usable within the parser.

----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, July 04, 2008 12:16 AM
Subject: Re: Fixed dynamic chat bug regarding special characters


Those chars are in romanian language, but I don't think this is important, because UTF-8 should treat all unicode chars the same.

Oh, I've re-visited your page and I've seen:

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

I don't think it is sane to use ISO-8859-1 these days.
I think that all the pages should use UTF-8 for beeing able to display correctly special chars in more languages.

I don't know how easy is to use UTF-8 when using PHP, but there are more PHP frameworks and I think most of them should be using UTF-8 as a default...

Octavian

----- Original Message ----- From: "Bryan Garaventa" <bgaraventa11@xxxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, July 04, 2008 8:49 AM
Subject: Re: Fixed dynamic chat bug regarding special characters


Can you tell me which language set the characters belong to? This is turning out to be a bit difficult to track down. What I need to do is convert the special chars into a Unicode string, then convert them back without any data loss. Perhaps a combo of utf8 and base64 encoding might help, but I'm not sure what to test against. Knowing the language and chars that you are entering would help.

Thanks.


----- Original Message ----- From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, July 03, 2008 10:22 PM
Subject: Re: Fixed dynamic chat bug regarding special characters


Hi Brian,

Yes I've tested again and now with Firefox, but the special chars are still not printed correctly.
I guess those chars are send using UTF-8 encoding.

Octavian

----- Original Message ----- From: "Bryan Garaventa" <bgaraventa11@xxxxxxxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, July 04, 2008 5:16 AM
Subject: Fixed dynamic chat bug regarding special characters


Octavian, regarding the issue that you mentioned earlier about the chat app not displaying special characters correctly, could you test this when you have a chance to see if the chat form is now accepting special characters? This should be fixed. I changed the save method from urlencode/urldecode to base64_encode/base64_decode, which should correct the problem. I think...
http://gutterstar.net/dynamic_live_chat.php
Thanks,
Bryan

__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind

Other related posts: