Overview
| Artifact ID: | 685bd28123d9f433f116e2ee4214041e4991b39e |
|---|---|
| Ticket: | 0e92c404f19ede5b2eb06e6db27647d3138cc56f
Side effect on string range command (from encoding and format commands) |
| User & Date: | jan.nijtmans 2014-04-30 20:38:01 |
Changes
- assignee changed to: "jan.nijtmans"
- closedate changed to: "2456778.35973868"
- closer changed to: "jan.nijtmans"
- icomment:
Fixed in [77a7d8d123] (core-8-5-branch). In trunk, the fix was already applied more than 5 years ago ([ee4709ceaf], thanks to dkf), so I just backported dkf's fix. Explanation: The "encoding convertfrom" command creates an internal byte array representation from the string, and "string range" tries to make smart use of the byte array representation. But that shortcut was simply wrong.
- login: "jan.nijtmans"
- mimetype: "text/x-fossil-wiki"
- resolution changed to: "Fixed"
- status changed to: "Closed"