Special Characters - custom cell type

Suite and Optimus Suite 5
#1

I am having some difficulty with special characters such as Á. I am using a grid with a php connector. I’ve tried changing everything between UTF-8 and ISO-8859-1 but get the same results - it all looks correct in the grid but is stored incorrectly in the mySQL database. For example, Á is stored as à (with a tilde instead of an acute).
Using the pure text excell types such as edtxt and txttxt works well for some characters - a typed ampersand will be stored correctly as the HTML equivalent - & but this does not seem to work for the accents.

Regardless, for my purposes, what I really want to do is store all the accented characters as their HTML equivalents - for example, I want to store the single character "Á" as the 8-characters “Á”. I tried creating a custom cell type and I know I have created the function correctly because I can identify and change a test character on the fly but it seems that the Á has already been converted to à before this point. How would I “intercept” that input before it is converted, or is there another approach I should be looking at.

#2

Please, try to use enableUTFencoding() method of the dataProcessor:
docs.dhtmlx.com/api__dataprocess … oding.html

#3

That did not make a difference. However, it was one command that I was not aware of and this does seem like some sort of a mismatch.

I have everything (that I am aware of) set to UTF - my database, charset and I’ve got $conn->set_encoding(“utf-8”) in my processor script and so on.
What other settings are there that I should check? Perhaps there is still another setting or command that I have not learned about yet.

#4

Please, make sure that the you have an utf encoding in your database, in your browser and inputing the data in utf also.
If the problem still occurs for you please, provide with a simplified compete demo or share with a demo link, where the problem can be reproduced.

#5

Thanks for your help. I have managed to determine that it is not related to DHTMLX.

I still don’t know what it is but I found that it all works correctly in my local Wamp Server test environment. As far as I can tell, my test and production environments are the same. However, if I remove mysqli_set_charset($conn, "utf8"); from my Wamp connection script, then I can duplicate the problem I am seeing in production. So, it’s definitely some sort of mismatch, I just haven’t spotted it yet.