Ah!, right. Thanks! ... if I remember correctly, that was also discussed in
the older mail thread about parsing Japanese, when Moritz said that he
didn't want to make comparse users dependent on utf8.
Works well now, and also thanks for mentioning the ,d trick!
On Tue, Feb 18, 2020 at 12:44 PM
Christoph Lange wrote:
> Yes, this helps. Kind of ;-) ... using the character set
> char-set:alphabetic, my umlauts are now parsed. But I don't get them back
> in my result, at least not as printable characters. Instead, the following
> happens, and utterly confuses me:
Hmm, indeed. From what I
Yes, this helps. Kind of ;-) ... using the character set
char-set:alphabetic, my umlauts are now parsed. But I don't get them back
in my result, at least not as printable characters. Instead, the following
happens, and utterly confuses me:
#;2> (define s3 (parse letters (string->list s)))
#;3> s3
Christoph Lange wrote:
> meaning, that the ä isn't recognized as being a letter within the
> 'char-set:letter'.
The utf8 egg’s srfi-14 character sets are designed to be compatible with the
original srfi-14 and only contain ASCII characters, as stated in the
documentation:
Hi Christoph,
On 17 February 2020 14:31 +01, Christoph Lange wrote:
> meaning, that the ä isn't recognized as being a letter within the
> 'char-set:letter'. (The UTF8 aspect of correct character width works on the
> other hand: in the remaining string, the ä is represented by only one #\.
> If I
