View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001552 | Double Commander | Plugins | public | 2016-09-22 20:17 | 2020-06-19 21:52 |
| Reporter | daniel | Assigned To | Alexx2000 | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Projection | none | ETA | none | ||
| Product Version | 0.7.5 | Product Build | 7092M | ||
| Target Version | 0.7.6 | Fixed in Version | 0.7.6 | ||
| Summary | 0001552: WDX: Encode path components in 8.3 format, if possible | ||||
| Description | I have noticed that WDX plugins don't work if a path contains characters that cannot be represented in current encoding. At the same time, all is OK in Total Commander. I wrote a small test plugin and found that when Total Commander pass FileName to ContentGetValue, it uses 8.3 format for a path component if it cannot be converted losslessly to the system's codepage. Double Commander, however, converts UTF-8 to system's codepage directly, so all unsupported characters are replaces by ?. For example, a path "d:\ˁ˚ᴥ˚ˀ\ALGER.TTF" is: "d:\A4C2~1\ALGER.TTF" in Total Commander "d:\?????\ALGER.TTF" in Double Commander | ||||
| Tags | No tags attached. | ||||
| Fixed in Revision | 7115,7131 | ||||
| Operating system | Windows | ||||
| Widgetset | Win32 | ||||
| Architecture | 64-bit | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-09-22 20:17 | daniel | New Issue | |
| 2016-09-23 18:59 | Alexx2000 | Fixed in Revision | => 7115 |
| 2016-09-23 18:59 | Alexx2000 | Assigned To | => Alexx2000 |
| 2016-09-23 18:59 | Alexx2000 | Status | new => resolved |
| 2016-09-23 18:59 | Alexx2000 | Resolution | open => fixed |
| 2016-09-23 18:59 | Alexx2000 | Target Version | => 0.7.6 |
| 2016-10-03 20:49 | Alexx2000 | Fixed in Revision | 7115 => 7115,7131 |
| 2016-10-03 20:49 | Alexx2000 | Fixed in Version | => 0.7.6 |
| 2020-06-19 21:52 | Alexx2000 | Status | resolved => closed |
