![]() |
#31
|
|||
|
|||
![]()
This is how it's stored in the database
Code:
The prime minister’s official spokesman said Johnson remained “very clear in his determination to get a deal” Code:
The prime minister�s official spokesman said Johnson remained �very clear in his determination to get a deal� Code:
The prime minister’s official spokesman said Johnson remained “very clear in his determination to get a deal” |
#32
|
|||
|
|||
![]() ![]() I can see now that the database could still be ISO-8859-1 if the database engine did the translation to and from UTF-8 at its boundary. That could cause what I see. This translation would happen closer to the database than the swear filter and so the '***' will not be caught as it isn't in the UTF-8 datastream. You say “ is stored in the database. If it is ISO-8859-1 then it must be stored as Unicode in some way as “ isn't in ISO-8859-1. Can you see the raw data as, say, a hex string? |
#33
|
|||
|
|||
![]()
Did a bit more digging and it gets weird.
The data in the database is stored as both Windows-1252 from prior to switching to UTF-8 and UTF-8 thereafter. If I turn on the setting both data stored as Windows-1252 and UTF-8 in the database is displayed correctly on the site however any new posts made are converted to Windows-1252 with any characters outside the set being saved and displayed as ?, so indeed this isn't the solution. I'm thinking now the easiest option would be to just leave the encodings all as they were originally and just remove the &# from the swear filter, but then again the Go Advanced doesn't convert them. Outside that I guess converting the previous Windows-1252 characters to UTF-8 in the database somehow...or I guess just leaving them broken ![]() UPDATE: It's actually even weirder... If I make a new post I get: ![]() If I refresh the page once, I still get the above, but If I refresh the page a second time I get: ![]() Anyway, I give up, it's all too weird. I hope you work it out without your brain exploding ![]() |
#34
|
|||
|
|||
![]()
^ Indeed we are! Apparently the question mark in the diamond will only show up on old posts and not new ones
![]() |
#35
|
|||
|
|||
![]()
^^^ I like weird; for some reason.
![]() It was in interesting diversion from the daily grind but there is a limit to what we can do and deduce from the outside. Dropping the subject would probably be best and the issue will soon be forgotten. |
#37
|
|||
|
|||
![]()
^ ha! I want to use this.
|
#38
|
|||
|
|||
![]()
Are you using an iPhone or apple tablet?
|