From: rm@fabula.de
Cc: rm@fabula.de, "Lars J. Aas" <larsa@sim.no>, guile-user@gnu.org
Subject: Re: defining new character names?
Date: Wed, 21 Aug 2002 12:00:01 +0200 [thread overview]
Message-ID: <20020821100001.GD23971@www> (raw)
In-Reply-To: <uw51y8slg9v.fsf@saturn.math.uni-magdeburg.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1884 bytes --]
On Wed, Aug 21, 2002 at 11:20:28AM +0200, Matthias Koeppe wrote:
> rm@fabula.de writes:
>
> > I have to admit that i toyed with the idea of extending guiles
> > scm_charnames[] array in chars.c myself. My idea was to extend the
> > table to use the names also used for ISO 8879 character entities
> > (mostly known from their use in HTML pages). Since such entities are
> > specific to an encoding it would make sense to make the table extensible
> > (i guess this would need to be done by extending the read-options inter-
> > face).
>
> I think that it is a bad idea to make Guile's characters
> encoding-specific. This is not the right way to internationalize
> Guile.
Hmm, as i understand it right now, a character in guile is never
encoding-specific (and i never suggested making it so).
What i (and Lars, i guess) suggest, is to make guile's list of _named_
character literals configurable. Nothing more. Since this is a question
of the _reader_ it won't change anything. Whether i type #\Auml or 'Ä'
(that's an capital 'a' with a german umlaut accent for those non-iso-8859-1ers)
doesn't make any difference to the guile interpreter, or?
> Instead, we should change Guile's characters to Unicode. Then, of
> course, it makes sense to allow Unicode character names (and ISO 8879
> character entities) for #\ syntax.
>
> The encoding of characters should only be an issue for input/output
> and interaction with C libraries.
>
> Is anyone working on Unicode support for Guile?
Good question! The current state of unicode support makes it impossible to
use guile with XML, i'm affraid :-(
Ralf
> Regards,
>
> --
> Matthias K?ppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-08-21 10:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 10:07 defining new character names? Lars J. Aas
2002-08-19 23:36 ` Marius Vollmer
2002-08-20 3:40 ` Keith Wright
2002-08-21 4:01 ` Keith Wright
2002-08-21 8:12 ` Lars J. Aas
2002-08-21 8:43 ` rm
2002-08-21 8:51 ` Matthias Koeppe
2002-08-21 9:17 ` Lars J. Aas
2002-08-21 9:54 ` rm
2002-08-27 15:09 ` Matthias Koeppe
2002-09-01 16:24 ` Rob Browning
2002-09-01 16:49 ` Marius Vollmer
2002-08-20 8:20 ` Matthias Koeppe
2002-08-20 10:18 ` rm
2002-08-21 9:20 ` Matthias Koeppe
2002-08-21 10:00 ` rm [this message]
2002-08-21 18:01 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 15:24 Lynn Winebarger
2002-08-21 17:33 ` Keith Wright
2002-08-21 18:27 ` Lynn Winebarger
2002-08-21 19:06 ` rm
2002-08-21 19:47 ` Lynn Winebarger
2002-08-21 23:04 ` Keith Wright
2002-08-21 23:07 ` Keith Wright
2002-08-21 19:40 ` Marius Vollmer
2002-08-22 4:12 ` Keith Wright
2002-08-22 5:16 ` Lynn Winebarger
2002-08-22 7:42 ` rm
2002-08-22 8:39 ` Lynn Winebarger
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=20020821100001.GD23971@www \
--to=rm@fabula.de \
--cc=guile-user@gnu.org \
--cc=larsa@sim.no \
/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).