Modify ↓
#10872 closed defect (fixed)
Please ignore BOM as first character on preset files
Reported by: | sommerluk | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.12 |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
Presets are UTF8 encoded XML files.
If this file starts with BOM (Byte order mark), JOSM doesn’t accept it and reports an error.
Could JOSM simply ommit the BOM as first character?
Attachments (2)
Change History (6)
comment:1 Changed 9 years ago by
Owner: | changed from team to sommerluk |
---|---|
Status: | new → needinfo |
comment:2 Changed 9 years ago by
Owner: | changed from sommerluk to team |
---|---|
Status: | needinfo → new |
preset_bom.xml cannot be loaded with JOSM.
If you try to do so, when you click on “OK” in the settings dialog, you get:
“Preset cannot be readed: <filename>. Use it anyway? Error is: [1:1] Content not allowed in Prolog.]”
However, with preset.xml (same content, but without leading BOM) it works fine.
comment:4 Changed 9 years ago by
Milestone: | → 14.12 |
---|
Note: See
TracTickets for help on using
tickets.
can you please post your preset file and status report? Thanks.