On Mon, Jul 23, 2012 at 9:17 AM, Matthew Mondor wrote:
> Examples using those sequence streams can be found in the
> utf-8-string-encode and utf-8-string-decode functions at
>
> http://cvs.pulsar-zone.net/cgi-bin/cvsweb.cgi/mmondor/mmsoftware/cl/server/character.lisp?rev=1.3;content-type=text%2Fpl
On Mon, 23 Jul 2012 03:17:47 -0400
Matthew Mondor wrote:
> own strings in UBCS-4/UTF-32 if compiled with unicode support. But you
s/UBCS/UCS/
--
Matt
--
Live Security Virtual Conference
Exclusive live event will cove
On Mon, 23 Jul 2012 10:23:16 +0400
Арсений Заостровных wrote:
> But is there any way to force ecl use utf-8 instead of utf-32, and in
> simple english case be the same as ascii? May be it has some special
> functions to work exactly with specified encoding?
I'm not sure if this is what you're lo
Thank you for a solution.
But is there any way to force ecl use utf-8 instead of utf-32, and in
simple english case be the same as ascii? May be it has some special
functions to work exactly with specified encoding?
2012/7/23 Polos Ruetz
> 2012/7/22, Арсений Заостровных :
> > std::string out
2012/7/22, Арсений Заостровных :
> std::string outStr = (char*)princed->base_string.
This code is taken from "EQL" and converts from/to a QString.
(But maybe there's a better way.)
cl_object from_qstring(const QString& s)
{
cl_object l_s = ecl_alloc_simple_extended_string(s.length());
Hi all.
I'm using the latest release of ecl - 12.7.1. The question may be not about
the ecl at all. But there a misunderstanding: what encoding ecl uses by
default during conversation between lisp and c? The nice project
http://createuniverses.blogspot.com/2009/09/qtimagine-skeleton-project-for-liv
