Ach! Of course… thanks for that.
What I have run into, isn’t really a LW problem with character encodings after all… LW seems to handle extended characters in filenames just fine. I spent the entire morning throwing test case at LW and Babel. Not sure what Babel is actually producing, but it differs from LW’s char-code encodings. But that doesn’t really matter for my uses.
The problem arises that when I want to have a shell execute some command using SYS:CALL-SYSTEM, like Apple’s afconvert utility, the shell balks at the extended chars and cannot find the file. You’d think, that if a company were going to allow Unicode filenames, then they’d make their utilities capable of handling such. But no…
- DM
I assume you mean LW:SIMPLE-CHAR?
I'd test for type equivalence with subtype, like so:
(and (subtypep 'lw:simple-char 'cl:character)
(subtypep 'cl:character 'lw:simple-char))