Jason Orendorff wrote:
You could fix both by providing higher-level APIs: (string-first s) ===> the first grapheme cluster (string-rest s) ===> everything else and so on. The way this leads is to a realignment of all the string/character APIs toward grapheme clusters, away from scalar values. I offer this because if the editors want to do something unconventional, I think this is the way to go.
If you go back to some SRFIs that put forward early R6 proposals re unicode, in the discussions, you'll find that bear (on this list) put forward something similar. A grapheme-cluster orientation would at least be consistent with a "this is for human text" conception of what CHAR is for but it raises the interesting issue of a countably infinite character set.... -t _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
