🕸Fergus Duniho wrote on Thu, Jun 14, 2018 08:50 PM UTC:
One problem with my old unicode conversions is that to get the text to appear as unicode on the page, it had to look like gobbeldygook in the database. By setting the charset to utf8mb4 when opening a PDO connection, I am able to have text appear as unicode on the page while also appearing as unicode in the database. This is a good thing, but it also means that I have to do the unicode conversions over. I just did names of inventors. But to do this, I had to temporarily delete "charset=utf8mb4" from connect_to_database(), so that the text would appear correctly on the page so that I could copy and paste it to the database. When I'm not doing more conversions, I'll set it back to utf8mb4. Until the conversions are done, I'll be alternating between making the charset utf8mb4 and not making it that, and some non-ASCII strings will look weird. When it's all done, I'll set the charset to utf8mb4 for good, and all non-ASCII text should look correct.
One problem with my old unicode conversions is that to get the text to appear as unicode on the page, it had to look like gobbeldygook in the database. By setting the charset to utf8mb4 when opening a PDO connection, I am able to have text appear as unicode on the page while also appearing as unicode in the database. This is a good thing, but it also means that I have to do the unicode conversions over. I just did names of inventors. But to do this, I had to temporarily delete "charset=utf8mb4" from connect_to_database(), so that the text would appear correctly on the page so that I could copy and paste it to the database. When I'm not doing more conversions, I'll set it back to utf8mb4. Until the conversions are done, I'll be alternating between making the charset utf8mb4 and not making it that, and some non-ASCII strings will look weird. When it's all done, I'll set the charset to utf8mb4 for good, and all non-ASCII text should look correct.