wish: detect/skip UTF-8 BOM (Excel CSV files)
Bug #1844892 reported by
R Mark
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HomeBank |
Fix Released
|
Wishlist
|
Maxime DOYEN | ||
Bug Description
Excel writes out a byte-order-mark (0xEF,0xBB,0xBF) when exporting a UTF-8 CSV. This trips up the Homebank importer and corrupts the date on the first row / transaction. Please consider detecting and skipping over the BOM.
Of course, it would be better if Excel didn't do this, but that's unlikely to change.
https:/
OS: Windows 10
HomeBank 5.2.8
Excel: latest Office 365 / 1908 (August 2019)
Revision history for this message
| R Mark (critsec) wrote | #1 |
| summary: |
- Consider detecting and skipping over the UTF-8 BOM at the start of Excel - CSV files + wish: detect/skip UTF-8 BOM (Excel CSV files) |
| Changed in homebank: | |
| importance: | Undecided → Wishlist |
| Changed in homebank: | |
| assignee: | nobody → Maxime DOYEN (mdoyen) |
| milestone: | none → 5.3 |
| status: | New → Fix Committed |
| Changed in homebank: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
