Re: [clisp-list] Where does this encoding come from?

[Pascal B. <pj...@in...>]

Sam Steingold writes:
> Pascal Bourguignon wrote:
> >=20
> > I have a dribble open, and while the terminal is in utf-8, the files
> > are in iso-8859-15 by default.
> >=20
> > *DEFAULT-FILE-ENCODING*          #<ENCODING ISO-8859-15 UNIX>
> > *TERMINAL-ENCODING*              #<ENCODING UTF-8 UNIX>
> >=20
> >=20
> > Now, the problem is that DRIBBLE doesn't take an external-format
> > argument, so I cannot portably specify the encoding for the dribble
> > file...
> >=20
> > The above error message is signaled even before
> > CONVERT-STRING-TO-BYTES is called, by the input processing of
> > DRIBBLE.=20
> >=20
> > Perhaps DRIBBLE should use CUSTOM:*TERMINAL-ENCODING* ?
>=20
> I am not sure this is a good idea.
> dribble file is a *file*, after all.
> How about a warning in DRIBBLE:
>=20
> (unless (or (eq *DEFAULT-FILE-ENCODING* *TERMINAL-ENCODING*)
>              (and (subtypep *DEFAULT-FILE-ENCODING* *TERMINAL-ENCODING*=
)
>                   (subtypep *TERMINAL-ENCODING* *DEFAULT-FILE-ENCODING*=
)))
>    (warn "~S: ~S and ~S cover different character ranges, you will be=20
> restricted to their intersection while dribbling is in effect" 'dribble=
=20
> *DEFAULT-FILE-ENCODING* *TERMINAL-ENCODING*))

That would be good enough to prevent other people losing too much time
on this problem.

This warning:

   (warn "~S: CUSTOM:*DEFAULT-FILE-ENCODING* and CUSTOM:*TERMINAL-ENCODIN=
G*=20
cover different character ranges, you will be restricted to their interse=
ction
while dribbling is in effect" 'dribble)

would even allow them to know what "variable" can be modified to
correct the problem.

--=20
__Pascal Bourguignon__                     http://www.informatimago.com/

PLEASE NOTE: Some quantum physics theories suggest that when the
consumer is not directly observing this product, it may cease to
exist or will exist only in a vague and undetermined state.