Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
November 2, 201212 yr Management Legacy reasons really. IP.Board 1.0 to 2.0 used ISO-8859-1 as the default encoding. We've not found a compelling enough reason to convert all the data over to UTF-8. It can be tricky when you consider serialized strings that may contain non UTF-8 characters so converting them over may break them, etc. We do want to convert to UTF-8 at some point.
November 4, 201212 yr Author Legacy reasons really. IP.Board 1.0 to 2.0 used ISO-8859-1 as the default encoding. Thanks We do want to convert to UTF-8 at some point. Yes, it would be good because to special characters problems. When I have some issues with ľščťžýáíéúäô on my utf-8 board, here on iso-8859-1 board I couldn't reproduce it. I didn't have bigger problems with this, but who knows...
November 4, 201212 yr Thats when i manually convert the DB to UTF-8, because when you import some sql files within a DB the encoding doesnt accept the special characters so i just decided to manually change the DB to UTF-8
Archived
This topic is now archived and is closed to further replies.