Bridging UTF-8 Coppermine with a non unicode BBS Bridging UTF-8 Coppermine with a non unicode BBS
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Bridging UTF-8 Coppermine with a non unicode BBS

Started by Titooy, December 09, 2005, 12:10:03 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

Titooy

December 09, 2005, 12:10:03 PM
Most of the BBS systems are still in "local" encoding. When Coppermine is bridged with these BBS, if the username contains non-ascii characters, it's not displayed correctly in Coppermine. I fixed it with changing USER_NAME into utf8_encode(USER_NAME) in my theme and in themes.inc.php but maybe a better solution would be to fix it directly in the bridge...

By the way, this should be done also for all the profile informations coming from the BBS tables...
Print
Go Up Pages1
User actions