Opened 12 years ago
Last modified 11 years ago
#1556 new defect
Properly handle UTF-8 files in reference check tool
Reported by: | historic_bruno | Owned by: | |
---|---|---|---|
Priority: | If Time Permits | Milestone: | Backlog |
Component: | Non-game systems | Keywords: | perl |
Cc: | Patch: |
Description
We have a Perl script for finding unused and missing assets. For JSON files, it uses JSON::decode_json which expects a binary UTF-8 encoded string, but we don't do any encoding and we don't strip a potential BOM so the JSON parsing fails.
maur.json is an example that fails due to its BOM.
Attachments (1)
Change History (6)
by , 12 years ago
Attachment: | utf8-bom.patch added |
---|
comment:1 by , 12 years ago
comment:4 by , 11 years ago
comment:5 by , 11 years ago
Note:
See TracTickets
for help on using tickets.
Either remove all BOMs and never use them again (they are not recommended anyways when using utf-8) or do something like in the attached patch.