Hi,
On 08.07.2014 00:58, Mario Domenech Goulart wrote:
To properly handle UTF-8, we have the utf8 egg. If I understand
correctly, the only way for eggs to properly support UTF-8 is by using
the utf8 egg (or an equivalent implementation).
Best wishes.
Mario
Why don`t just add *(use utf8)* lin
On Tue, Jul 8, 2014 at 12:59 PM, John Cowan wrote:
>
> > The same approaches also apply to eggs needing the full
> > numeric tower, though with UTF-8 there's less chance of
> > breakage when mixing eggs which do and don't use the utf8 egg.
>
> I would say that UTF-8 has *more* chance of causing u
Alex Shinn scripsit:
> On Tue, Jul 8, 2014 at 5:58 AM, Mario Domenech Goulart
> wrote:
>
> It might help the discussion if we had a list of eggs which
> are known to break on UTF-8 inputs.
Indeed.
> > 1. Have and -utf8 variants. Or, more generally, and
> >- variants. That would turn ou
Hi,
On Tue, Jul 8, 2014 at 5:58 AM, Mario Domenech Goulart <
mario.goul...@gmail.com> wrote:
> Hi,
>
> I want to use some eggs and I need them to handle UTF-8. By "handle
> UTF-8" I mean "treat strings as UTF-8", so that
>
>(string (string-ref "ç" 0)) => "ç"
>
> for example.
>
> CHICKEN's st
Hi,
I want to use some eggs and I need them to handle UTF-8. By "handle
UTF-8" I mean "treat strings as UTF-8", so that
(string (string-ref "ç" 0)) => "ç"
for example.
CHICKEN's string-related procedures "accept" UTF-8 strings, but it
doesn't mean they will correctly handle them.
To proper
Dear Chicken users,
if any of you uses the lz4 egg in your application, it's time to
do an upgrade to the 0.2 version I have just released. This includes
the upstream version r119, which fixes the latest security issues
as you are being able to watch the whole internet drama around it.
There is n
