Bug #79
Correct encoding
| Status: | New | Start: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Cambell Prince | % Done: | 0% |
|
| Category: | application | Spent time: | - | |
| Target version: | V2.0.x | |||
| Resolution: |
Description
Solid is putting out illegal XML at this point. Encoding conversion is crucial for valid XML files.
Example SFM hacked 8-bit: ef bf bd 6c ef bf bd 2e
Correctly converted to UTF-8: ef 14a bd 6c ef 14a bd 2e
SOLID fake UTF-8: fffd 6c fffd
The last line is actually valid UTF-8 code points in this particular sample (although obviously not the correct ones), but similar unconverted codes will be illegal, causing various crashes with transforms, FW import, and some XML editors.
History
Updated by Cambell Prince over 4 years ago
See also #73
Updated by Cambell Prince over 4 years ago
The encoding is now correct (mixed) in SFM. Encoding is also correct in Flat and Structured XML. However, the data is not necessarily unicode, which is bad. We still need to address the issue of how to present hacked font data in XML.