From pjb@imaginet.fr  Tue Jun 13 21:47:23 2000
Received: from triton.local.net (IDENT:postfix@65-MURC-X12.libre.retevision.es [62.82.105.65])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id VAA16933
	for <prolog@swi.psy.uva.nl>; Tue, 13 Jun 2000 21:47:20 +0200 (MET DST)
Received: by triton.local.net (Postfix, from userid 1000)
	id A86253B193; Tue, 13 Jun 2000 14:54:39 +0200 (CEST)
From: "Pascal J. Bourguignon" <pjb@imaginet.fr>
To: ok@atlas.otago.ac.nz
Cc: prolog@swi.psy.uva.nl
In-reply-to: <200006112259.KAA31710@atlas.otago.ac.nz> (ok@atlas.otago.ac.nz)
Subject: Re: Suggestion regarding the classification of the characters.
X-PGP-Key-ID: 0xEF5E9966
X-PGP-fingerprint: 00 F5 7B DB CA 51 8A AD 04 5B 6C DE 32 60 16 8E EF 5E 99 66
X-PGP-Key-URL: http://www.imaginet.fr/~pjb/pgpkey
X-URL: http://www.imaginet.fr/~pjb/index
X-Accept-Language: fr, es, en
Organization: Latymer Designs Ltd.
Disposition-Notification-To: <pjb@imaginet.fr>
Return-Receipt-To: <pjb@imaginet.fr>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Content-Type: text/plain; charset=iso-8859-1
Reply-To: <pjb@imaginet.fr>
References:  <200006112259.KAA31710@atlas.otago.ac.nz>
Message-Id: <20000613125439.A86253B193@triton.local.net>
Date: Tue, 13 Jun 2000 14:54:39 +0200 (CEST)


> Date: Mon, 12 Jun 2000 10:59:19 +1200 (NZST)
> From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
> 
> The intent of C/UNIX locales and their aspects such as LC_ALL
> LC_MESSAGES LC_MONETARY LC_COLLATE LC_TIME LC_NUMERIC LC_CTYPE
> is so that a program can adapt its *data* handling.
> 
> To set the *syntax* of the programming language from the locale
> is a bad idea.  There are plenty of excellent reasons why Quintus
> Prolog decoupled its data character classification predicates
> from its syntax tables.
> 
> Instead of everyone coming up with their own ideas about which characters
> are "more like alpha" and which characters are "more like punct", let's
> appeal to unidata*.txt.  For example, the SUPERSCRIPT DIGIT characters
> are classified as 'Nd'.  That way we'll all have the _same_ way of
> classifying characters, and be able to share code and data.
> 
> It could be quite simple.  Prolog should use the number and
> identifier syntax spelled out in the Unicode book, and should
> accept a
> :- text_encoding(<coded character set name>).
> directive at the top of a file to tell it how the bytes in the
> file map to Unicode characters.  (ISO 2022 is the official mechanism
> for things like that, but for something like a source file, it is better
> to be readable.)

Yes, it's probably best to use the static classification from UNICODE.

Remains to correct the  inconsistencies in the currrent implementation
of SWI-Prolog  regarding the character classification, and  to make it
match the UNICODE classification.


-- 
__Pascal Bourguignon__    PGP Key ID:      0xEF5E9966
mailto:pjb@imaginet.fr    PGP fingerprint: 00 F5 7B DB CA 51 8A AD 04 5B 
http://www.imaginet.fr/~pjb/               6C DE 32 60 16 8E EF 5E 99 66

