Interesting, I think we should change that OOTB, I guess it was needed long ago
Or is someone aware of possible drawbacks?
Jacques
Le 20/03/2015 18:09, Mike a écrit :
If you are using mysql, you have to convert your database to UTF8. You
would also have to change the connection settings in entity engine to also
use UTF8. Last time I checked, the default settings were latin1.
On Fri, Mar 20, 2015 at 4:24 AM, paramjit.saini <
[email protected]> wrote:
Hi All,
I have an issue to create/update addresses with *special characters from
front-end*. When i try to create / update address from front-end, it save
text into database with wrong character. I am trying to import
"Skogsgläntevägen" into database but it will save like
"Skogsgläntevägen"
into database.
When i try to create/update addresses with *special characters from
back-end* then it is working properly means special character import into
database properly.
Both request using same service to update address.
Please help me to solve this issue.
Thanks,
Paramjit
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Create-update-addresses-with-special-characters-like-a-tp4665357.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
