Context Navigation

Changes between Initial Version and Version 1 of Ticket #62995, comment 8

initial	v1
9	9	It looks like it has to do with the data tables. The original site where the error is happening is a very old installation. It's running 6.7.2, but it was originally created with WordPress 2.1 in 2007.
10	10
11		I noticed the installations where this was successful did not replace the narrow no-break space character in the filename. I checked the database and the core WP tables have "latin1_swedish_ci" collation, so they're not UTF-8. That would explain the question marks.
	11	I noticed the installations where this was successful did not replace the narrow no-break space character in the filename. I checked the database, and the core WP tables have "latin1_swedish_ci" collation, so they're not UTF-8. That would explain the question marks.
12	12
13	13	Anyway… I do think this still points to an issue that should be addressed. Since WordPress is already modifying Media Library filenames to be maximally compatible for URLs, I would think ideally it would strip out UTF-8 characters, at least non-essential ones like the narrow no-break space.