search

carlosomarrd / clients-oriented-ftp

Automatically exported from code.google.com/p/clients-oriented-ftp
0 stars 0 forks source link

Wrong charset #144

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Filling the description with polish fonts returns wrong charset after 
uploading. Screenshots in attachments.

Original issue reported on code.google.com by Michal.O...@gmail.com on 30 Jul 2012 at 12:03

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for your report! What charset would you normally use?

Original comment by i...@subwaydesign.com.ar on 2 Aug 2012 at 8:15

GoogleCodeExporter commented 9 years ago 
UTF-8.

Original comment by Michal.O...@gmail.com on 2 Aug 2012 at 9:31

GoogleCodeExporter commented 9 years ago 
Confirmed, this goes for all non-latin languages. I am Bulgarian.

I changed /includes/classes/database.php, adding this after mysql_connect():

mysql_set_charset('utf-8', $this->connection);

This DOES change things, but it still doesn't work. My database collation is 
utf8_general_ci. Not sure if this has to do anything with that.

Original comment by drgigg...@gmail.com on 8 Mar 2013 at 8:08

GoogleCodeExporter commented 9 years ago 
I've eliminated all charset issues by applying the following changes (I'm from 
Hungary):

1. install/database.php:
Changed default charset to utf8 for every table and removed all latin1 
collations and charset definitions in text fields. Make sure to create the 
empty database with utf8_general_ci collation before installing the app.

2. includes/classes/database.php:
Add mysql_query("SET NAMES utf8"); after calling mysql_connect();

3. Removed all htmlentities() calls in all php files - there are about ~10 
occurences only.

Thanks for this great app! It saved my day! ;)

Original comment by kosars...@gmail.com on 25 Mar 2013 at 12:56

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have posted a solution which is a mix of this solution and other solutions
see bug 279

Original comment by access_c...@hotmail.com on 2 May 2013 at 4:19

GoogleCodeExporter commented 9 years ago 
This problem arises with Portuguese too. How many of us can't use this great 
software only for this reason? The solutions proposed are not clear (many 
solutions from different sources) and mostly difficult to implement for average 
users. I would give this one a TOP importance because everything else works! 
Thank you and congratulations for a great piece of software!

Original comment by amadei...@gmail.com on 4 Jul 2013 at 12:09

Attachments:

GoogleCodeExporter commented 9 years ago 
The solution : see bug 279 should work for you.
Have you try it?

Original comment by access_c...@hotmail.com on 12 Jul 2013 at 4:40

GoogleCodeExporter commented 9 years ago 
I've seen it before but this is not easy to implement because what I have is an 
outdated Softaculous installation in a hosted server service and I don't have 
full control over the database. I updated projectsend overwriting the old files 
and everything seems to run perfectly, except for the Portuguese characters. 
Anyway I'll give it a try. Thanks for reminding me.

Original comment by amadei...@gmail.com on 12 Jul 2013 at 6:39

GoogleCodeExporter commented 9 years ago 
Just want to add that I couldn't try the above editing solution because what I 
have is a ProjectSend Softaculous installation in a hosted service and the 
database is created by the Softaculous software. So I wasn't able to delete the 
old database neither could create a new one for ProjectSend. Also I don't know 
PHP coding so it is always risky to apply the changes sugested. It would be 
grate if the code could be patched and the database type updated. For me it 
wouldn't matter if I loose database content. Thank you.

Original comment by amadei...@gmail.com on 18 Jul 2013 at 3:57