This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.

Source for ticket #525

cc


    
changetime

    
2013-07-07 03:20:44

    
component

    
WG1 - Core

    
description

    
Peter Bex writes:

  Adding Unicode is perhaps too big of a change (but at least it's optional).

    
id

    
525

    
keywords

    

    
milestone

    

    
owner

    
alexshinn

    
priority

    
major

    
reporter

    
cowan

    
resolution

    
wontfix

    
severity

    

    
status

    
closed

    
summary

    
Adding Unicode is too big a change from R5RS

    
time

    
2013-05-13 17:17:21

    
type

    
defect

    
Changes

    
Change at time 2013-07-07 03:20:44

    
author

    
cowan

    
field

    
comment

    
newvalue

    
The WG decided by unanimous consent to take no action on this ticket.

    
oldvalue

    
2

    
raw-time

    
1373142044410382

    
ticket

    
525

    
time

    
2013-07-07 03:20:44

    
Change at time 2013-07-07 03:20:44

    
author

    
cowan

    
field

    
resolution

    
newvalue

    
wontfix

    
oldvalue

    

    
raw-time

    
1373142044410382

    
ticket

    
525

    
time

    
2013-07-07 03:20:44

    
Change at time 2013-07-07 03:20:44

    
author

    
cowan

    
field

    
status

    
newvalue

    
closed

    
oldvalue

    
new

    
raw-time

    
1373142044410382

    
ticket

    
525

    
time

    
2013-07-07 03:20:44

    
Change at time 2013-05-13 17:22:03

    
author

    
cowan

    
field

    
comment

    
newvalue

    
Well, you can't please everybody: ticket #493 complains because Unicode isn't mandatory, this one because it isn't omitted altogether.  I proposed UnicodeCowan, which is substantially what WG1 adopted, on the following principles:

1. No small Scheme implementation is required to support any specific Unicode character or repertoire (collection of characters), with the obvious exception of the ASCII repertoire.

2. Unicode is the predominant character standard today, and a small Scheme implementation's treatment of characters must conform to it, insofar as this does not conflict with Principle 1.

I think that's the best that a small language that is also a modern language can do.  Again, see [http://lists.scheme-reports.org/pipermail/scheme-reports/2013-May/003396.html ​my ballot] for a discussion of the difference between the "best possible result" and "the best result possible".

    
oldvalue

    
1

    
raw-time

    
1368440523805415

    
ticket

    
525

    
time

    
2013-05-13 17:22:03