Overview
| Artifact ID: | c312c1bb2d1c849da9ae26f320474eb1ad695d270b92d66aa4d6cfa6b8582ad7 |
|---|---|
| Ticket: | 4961066ba23474cd26b113996dd18f2a594dfca0
V2.2 seems to be fully broken |
| User & Date: | anonymous on 2024-11-24 18:43:41 |
Changes
- icomment:
Hi, Strange, your command works well for me under Debian testing (actually using Python 3.12.6). On the other hand, the trace under Windows points at a charset error: the used terminal is simply not compatible with UTF-8 or not configured to handle UTF-8 strings. Such an error under GNU/Linux systems would be quite strange. my 2¢
- login: "anonymous"
- mimetype: "text/x-fossil-plain"
- priority changed to: "Immediate"
- resolution changed to: "Open"
- subsystem changed to: "Grammalecte_Core"