Jean-François Mertens wrote: [] > The suggestion I made should work _ just > tried it : as is, I get the usual build, and substituting > "C" there by "fr" reproduces your error ..
Here is another test that shows that this is indeed a clisp bug. This one can easily be tried by anybody, so maybe someone will have an idea how to close in on the bug: Run clisp so that it gives an error message, for example clisp -c / Or run just "clisp" and type "1/0" or "bug" at the prompt. Then do the same thing with "clisp" replaced by "env LANG=fr clisp", for example env LANG=fr clisp -c / You will see that there is something wrong with message handling. It goes ballistic as soon as it sees a non-us-ascii character. In fact, if I try LANG=de, I can get similar errors (not with the same tests, because the German error messages use fewer non-ascii characters than the French ones). The error message is then clearer: Zeichen #\u00F6 kann im Zeichensatz CHARSET:ASCII nicht dargestellt werden. It tries to represent unicode characters in ascii and complains when this doesn't work. -- Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
