From: Martin Grabmueller <mgrabmue@cs.tu-berlin.de>
Cc: mvo@zagadka.ping.de, guile-user@gnu.org
Subject: Re: guile-1.7.0 - srfi-13 - Segmentation fault
Date: Tue, 12 Mar 2002 13:23:04 +0100 (MET) [thread overview]
Message-ID: <200203121223.g2CCN4n02240@siesta.cs.tu-berlin.de> (raw)
In-Reply-To: <3C8D7569.E2AE6D0F@altosw.be> (message from David Pirotte on Tue, 12 Mar 2002 00:26:33 -0300)
> From: David Pirotte <david@altosw.be>
> Date: Tue, 12 Mar 2002 00:26:33 -0300
>
> I just downloaded the latest guile-1.7 cvs and:
>
> guile> (use-modules (srfi srfi-13))
> guile> (string-titlecase "LIège")
> "LièGe" <== should be "Liège"
> guile> (string-capitalize "LIège")
> "LièGe" <== should be "Liège"
> guile> (string-capitalize "LIege")
> "Liege" ok
> guile> (string-capitalize "L'ECLUSE")
> "L'Ecluse" ok
> guile> (string-capitalize "L'éCLUSE")
> "L'éCluse" <== should be "L'écluse"
>
> it appears that anything folling an 8-bit char is capitalised, where it should
> not necessarily (I think)
string-titlecase (and string-capitalize as well, I think) capitalise
every alphabetic character after a non-alphabetic character, and they
are only prepared for 7-bit ASCII for now. They use the function
scm_char_alphabetic_p to check whether a character is alphabetic or
not, and this is unfortunately not enough for anyone outside US and
GB...
I thought I had mentioned that in the docs, but apparently not.
Unfortunately, I don't have the time right now, but maybe someone else
could add an explanation to the docs for the string case mapping
procedures.
'martin
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
parent reply other threads:[~2002-03-12 12:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3C8D7569.E2AE6D0F@altosw.be>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203121223.g2CCN4n02240@siesta.cs.tu-berlin.de \
--to=mgrabmue@cs.tu-berlin.de \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).