Re: CGI: PRINC: Character #\u0106 cannot be represented in the character set CHARSET:ASCII

On Mon, Mar 20, 2017 at 11:33:47AM -0400, Sam Steingold wrote:
> > already set custom:*misc-encoding* "utf-8" and
> > custom:*terminal-encoding* "utf-8", but yet, each time I try to decode
> > the value I get this information when POST-ing UTF-8 characters:
> >
> > ** - PRINC: Character #\u0106 cannot be represented in the character set CHARSET:ASCII
> 
> I don't know enough about CGI to figure out which encoding is used here.
> The "generic" recommendation is "-E utf-8" command line option which
> sets _ALL_ of them.  Please take a look at
> http://clisp.org/impnotes/clisp.html#opt-enc and links therefrom.
> 
> > [/sources/gnu/clisp-clisp/src/eval.d:573] reset() found no driver frame
> > (sp=0x7ffe1cfc5090-0x7ffe1cfb5730)
> > Exiting on signal 6
> 
> I suspect that this is a bug ("reset found no driver frame").
> If you can create a reproducible test case (not using things like CGI
> &c), you should file a bug report.

Thank you Sam. Regarding found no driver frame, it happens sometimes,
and I did not know it is a bug, cannot make conclusion on that one.

I was debugging one by one, then I found, if I use
make-pipe-io-stream, I had to set the custom:*default-file-encoding*
to t, as when piping into the stream, that is somehow related. I was
thinking standard input and output is enough. Now it works well.

Jean

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list