What do these messages mean: “invalid byte #x94 in CHARSET:ASCII conversion” and “character #u00B3 cannot be represented in the character set CHARSET:ASCII”?
This means that you are trying to read (“invalid byte”) or write (“character cannot be represented”) a non-ASCII character from (or to) a character stream which has ASCII :EXTERNAL-FORMAT. The default is described in -Edomain encoding. This may also be caused by filesystem access. If you have files with names incompatible with your CUSTOM:*PATHNAME-ENCODING*, filesystem access (e.g., DIRECTORY) will signal this error. You will need to set CUSTOM:*PATHNAME-ENCODING* or pass -Edomain encoding to CLISP. Using a “1:1” encoding, such as CHARSET:ISO-8859-1, should help you avoid this error. Note that this error may be signaled by the Print part of the read-eval-print loop and not by the function you call. E.g.
Related Questions
- What do these error messages mean: "invalid byte #x94 in CHARSET:ASCII conversion" and "character #u00B3 cannot be represented in the character set CHARSET:ASCII"?
- What do these messages mean: "invalid byte #x94 in CHARSET:ASCII conversion" and "character #u00B3 cannot be represented in the character set CHARSET:ASCII"?
- What do the Interlibrary Loan status messages mean?