| Type | Bug | Status | submitted | Date | 18-Nov-2014 06:33 |
|---|---|---|---|---|---|
| Version | alpha 111 | Category | Ports | Submitted by | abolka |
| Platform | All | Severity | crash | Priority | normal |
| Summary | READ/string crashes for UCS4 ("UTF-32") LE/BE files with a BOM |
|---|---|
| Description | See the example code. |
| Example code |
>> read %fixtures/umlauts-utf32le.txt
== #{FFFE0000E4000000F6000000FC0000000A000000}
>> read/string %fixtures/umlauts-utf32le.txt
(R3 crashes) ;; Expected: "äöü^/"
--
>> read %fixtures/umlauts-utf32be.txt
== #{0000FEFF000000E4000000F6000000FC0000000A}
>> read %fixtures/umlauts-utf32be.txt
(R3 crashes) ;; Expected: "äöü^/"
|
| Assigned to | n/a | Fixed in | - | Last Update | 20-Jan-2015 06:07 |
|---|
| Comments | |
|---|---|
|
(0004543)
abolka 18-Nov-2014 06:46 |
As we neither internally support UCS4 at the moment nor have a decoder ready (although the latter would be easy to remedy), causing an "unsupported encoding" error is probably the best solution at the moment. |
|
(0004548)
abolka 20-Jan-2015 06:07 |
In the core-tests suite. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 20-Jan-2015 06:07 | abolka | Comment : 0004548 | Added | - |
| 18-Nov-2014 06:46 | abolka | Comment : 0004543 | Added | - |
| 18-Nov-2014 06:33 | abolka | Ticket | Added | - |
