Opened 19 years ago
Closed 18 years ago
#788 closed defect (bug) (fixed)
trackbacks can't automatically discover iso-8859-1 charset
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | minor | Version: | |
| Component: | Administration | Keywords: | |
| Focuses: | Cc: |
Description
The current implementation of wp-trackback.php sets the charset to 'auto' if none is specified in the trackback call. But 'auto' only discovers ASCII, UTF-8 and some japanese encodings. It doesn't discover ISO-8859-1 - one of the widest spread encodings. I don't know how those different encodings can be reliably auto discovered, but wouldn't it make sense to tack ISO-8859-1 to the list of encodings and not use 'auto' but explicitely list the encodings for auto discovery?
Maybe the list can be 'ASCII,UTF-8,ISO-8859-1', because most other encodings will sent a charset variable, anyway?
At least in the current situation a trackback without charset= variable (like is done by Coreblog) isn't automatically translated when it's ISO-8859-1 and contains special chars like german umlauts. And that's bad, as that will break the content.