Matthew Mondor <mm_li...@pulsar-zone.net> writes: > > Possible solutions: > > - Carefully check other possibly affected code in the tree. > Perhaps replace the checks like that for bug 290 to explicit > coercions to base_string, which may signal a condition as needed if a > character cannot be encoded to ASCII. > Another possibility would be to encode to UTF-8 instead in the > future, although this may cause other problems depending on libc/OS. > A configurable, system-specific default FFI encoding could perhaps be > used in the future (i.e. using a dynamic variable to define the > encoding for FFI/C external encoding)...
clisp distinguishes the following encodings: CUSTOM:*DEFAULT-FILE-ENCODING* for :external-format :default CUSTOM:*FOREIGN-ENCODING* for FFI CUSTOM:*MISC-ENCODING* for the rest CUSTOM:*PATHNAME-ENCODING* for pathnames CUSTOM:*TERMINAL-ENCODING* for the terminal -- __Pascal Bourguignon__ http://www.informatimago.com/ "Le mercure monte ? C'est le moment d'acheter !" ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
