View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000807 | XMB1 | New Features | public | 2025-07-05 23:11 | 2025-07-05 23:11 |
Reporter | miqrogroove | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | confirmed | Resolution | open | ||
Target Version | 1.12.00 | ||||
Summary | 0000807: UTF-8 Schema | ||||
Description | The diverse string formats in the schema are one of the last things still driving me crazy in terms of maintaining this code base. This is the path forward: Convert all "double-slashed" strings to unslashed strings, no exceptions. Start brainstorming tools and procedures for conversion to UTF-8 encoding. If helpful, add schema columns that would aid the encoding conversion. Update page headers and templates with the new charset. Start addressing PHP charset use and any security implications. Create new translation files. Determine if non UTF-8 encodings will be supported or dropped completely. | ||||
Additional Information | https://docs.xmbforum2.com/index.php?title=XMB_1.9.12_Schema_String_Audit Also note the bbrulestxt setting is still saved as raw HTML. | ||||
Tags | No tags attached. | ||||
MySQL Version | |||||
PHP Version | |||||
Web Server | |||||
Browser | |||||
Flags | Schema Updates | ||||
Original Reporter | |||||
SVN Revision | |||||
Git Commit | |||||
related to | 0000802 | assigned | miqrogroove | Audit All Schema Value Formats |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-07-05 23:11 | miqrogroove | New Issue | |
2025-07-05 23:11 | miqrogroove | Status | new => assigned |
2025-07-05 23:11 | miqrogroove | Assigned To | => miqrogroove |
2025-07-05 23:11 | miqrogroove | Issue generated from: 0000802 | |
2025-07-05 23:11 | miqrogroove | Relationship added | related to 0000802 |
2025-07-05 23:11 | miqrogroove | Assigned To | miqrogroove => |
2025-07-05 23:11 | miqrogroove | Status | assigned => confirmed |