> What do people think about this attached patch?
>
> Andy
If you find the word
"coding" by scanning 8-bit char by 8-bit char, it can't
be UTF-16, since that would be more like
"c o d i n g :" with nulls interspersed.
While rather unlikely, it is a theoretical possibility
that a doc in encoding
What do people think about this attached patch?
Andy
>From 831c3418941f2d643f91e3076ef9458f700a2c59 Mon Sep 17 00:00:00 2001
From: Andy Wingo
Date: Mon, 28 Jan 2013 22:41:34 +0100
Subject: [PATCH] detect and consume byte-order marks for textual ports
* libguile/read.c (scm_i_scan_for_encoding):
Thanks David!
It's nice to know that, I thought Guile use PCRE, but I realized it's
posix RE.
On Mon, Jan 28, 2013 at 9:58 PM, David Pirotte wrote:
> Hello,
>
> > But I have some trouble with the regexp in Guile, seems "\\d+" can't
> > work, others, like "\\w+" works.
>
> i also had this 'prob
Hello,
> But I have some trouble with the regexp in Guile, seems "\\d+" can't
> work, others, like "\\w+" works.
i also had this 'problem' and someone suggested to rather use [[:digit:]]+
and friends - [:blank:] [:alpha:] ...
Cheers,
David
Yes, I can add documentation for it.
/Stefan
On Sun, Jan 27, 2013 at 11:17 AM, Andy Wingo wrote:
> On Sat 26 Jan 2013 14:03, Stefan Israelsson Tampe
> writes:
>
>> I will assume that you are familliar with th ck macro, included in
>> recent guile releases or else consider looking it up at
>>
>
Hi,
I just pushed some changes to (sxml simple)'s xml->sxml. Basically it
has keyword arguments now that do most of what people have been
requesting for a while (non-significant whitespace, easier handling of
entities, declaration of namespaces). We can add handling of some
doctype fragments as
Move test func to test-case.
And I think all the issues fixed.
Updated things attached.
Thanks!
;; Copyright (C) 2013 Free Software Foundation, Inc.
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as p
