I started such a thing a while ago, but never got it to the point of
submitting. There is a student interested in enhancing the Unicode support in
SBCL for GSOC 14: perhaps I can integrate that into his project, at least
partially.
-tree
Sent from my iPhone
> On Apr 10, 2014, at 11:05, Antoniotti Marco
> <[email protected]> wrote:
>
>
>> On Apr 10, 2014, at 16:31 , Paul Tarvydas <[email protected]> wrote:
>>
>> I'm using sbcl to write-char a 16-bit unsigned integer to a socket as two
>> separate unsigned 8-bit bytes, for example 141 should appear as
>>
>> #x00 #x8d.
>>
>> SBCL appears to convert the #x8d into a two-byte utf-8 char, resulting in 3
>> bytes written to the stream
>>
>> \#x00 #xcd #x8d.
>>
>> What is the proper incantation to achieve this? (SBCL on Windows, if that
>> matters).
>
> It may not be very helpful, but the “right incantation” would be to write a
> CDR that specified the behavior of implementations that deal with UTF* and
> UNICODE.
>
> Any takers?
>
> Cheers
> ―
> MA
>
>
>
>
>
>
> _______________________________________________
> pro mailing list
> [email protected]
> http://common-lisp.net/cgi-bin/mailman/listinfo/pro
_______________________________________________
pro mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/pro
