[wp-meta] [Making WordPress.org] #5117: WP dashboard city locations (encoding?) wrong
Making WordPress.org
noreply at wordpress.org
Sat Mar 28 15:41:58 UTC 2020
#5117: WP dashboard city locations (encoding?) wrong
-----------------------------------------+---------------------
Reporter: ramon fincken | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone: Q2
Component: Events API | Resolution:
Keywords: has-screenshots needs-patch |
-----------------------------------------+---------------------
Comment (by Otto42):
The problem appears to lie in the summary table that we're creating for
the purposes of faster searching. It's getting the name from there, but
the name there is not the canonical version of what we should be
returning.
So, for example, the summary table has Amsterdam, Àmsterdam, and Àmsterdam
in it. It also has:
AMS,Amesterdam,Amesterdao,Amesterdão,Amistardam,Amstardam,Amstedam,Amstelodamum,Amsterdam,Amsterdama,Amsterdamas,Amsterdami,Amsterdamo,Amsterdams,Amsterdan,Amsterntam,Amstèdam,Amszterdam,Damsko,Gorad
Amstehrdam,I-Amsterdami,Mokum,a mu si te
dan,aimstardaima,amasataradama,amastaradama... and so on. You get the
idea.
Basically, every alternate name exists in that table for fast searching.
Now, searching on name=Amsterdam in the summary table comes back with five
rows, and it essentially picks the first one it sees, which happens to
have the grave in this one.
I'm not 100% sure on this, but I think this happens because the table has
the latin1_general_ci collation set for it. Think the table needs a
restructure to be fully utf8mb4 for all rows and the collation.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5117#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list