From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Unicode and Guile
Date: Wed, 12 Nov 2003 01:29:29 +0100 [thread overview]
Message-ID: <87znf2ig46.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200311111902.LAA25202@morrowfield.regexps.com> (Tom Lord's message of "Tue, 11 Nov 2003 11:02:55 -0800 (PST)")
Tom Lord <lord@emf.net> writes:
> ~ (grapheme=? g1 g2 [locale]) => <boolean>
> ~ (grapheme<? g1 g2 [locale])
> ~ (grapheme>? g1 g2 [locale])
> [...]
> ~ (grapheme-ci=? g1 g2 [locale])
> ~ (grapheme-ci<? g1 g2 [locale])
> ~ (grapheme-ci>? g1 g2 [locale])
>
> The usual orderings.
Is it a good idea to have an ordering among graphemes, or would it be
better to only order texts, i.e., to allow for the context of a
grapheme to determine the order?
> ~ (make-text-marker text index) => <marker>
What about having _only_ markers and not allow integers as indices?
Also, what about making TEXTs unmutable by default and instead let
TEXT-REPLACE, etc return a new text object?
> The new TEXT? and GRAPHEME? types present a simple and traditional
> interface to "conceptual strings" and "conceptual characters".
> They make it easy to express simple algorithms simply and without
> reference to the internal structure of Unicode.
Indeed.
> There is no essential difference between a grapheme and a text
> object of length 1, and thus the proposal makes GRAPHEME? a
> subtype of TYPE.
Do we need the concept of grapheme at all, then?
> The proposal also makes it possible to pass strings everywhere that
> text can be used. I think that's the more interesting direction:
> just use text- and grapheme- procedures from now on except where you
> _really_ want to refer to octets.
Could we make strings/chars go away completely over time? For vectors
of octets, there is u8vector? from SRFI-4.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-12 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 17:15 Unicode and Guile Andy Wingo
2003-10-25 17:08 ` Stephen Compall
2003-10-26 0:03 ` Tom Lord
2003-10-26 12:34 ` Which Encoding? (was Re: Unicode and Guile) Stephen Compall
2003-10-31 13:25 ` Unicode and Guile Andy Wingo
2003-11-03 13:35 ` text buffers (was Re: Unicode and Guile) Stephen Compall
2003-11-03 20:34 ` Tom Lord
2003-11-04 10:04 ` Stephen Compall
2003-11-03 20:31 ` Unicode and Guile Tom Lord
2003-11-06 18:16 ` Andy Wingo
2003-11-11 19:02 ` Tom Lord
2003-11-12 0:29 ` Marius Vollmer [this message]
2003-11-12 1:40 ` Tom Lord
2003-11-12 2:30 ` Marius Vollmer
2003-11-12 4:03 ` Tom Lord
2003-11-12 16:59 ` Marius Vollmer
2003-11-17 16:17 ` Andy Wingo
2003-11-12 0:06 ` Marius Vollmer
2003-11-12 1:27 ` Tom Lord
2003-10-31 13:16 ` Andy Wingo
2003-11-02 21:23 ` Kevin Ryde
2003-11-26 20:35 ` Mikael Djurfeldt
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=87znf2ig46.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/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).