[Mono-list] OCL 0.2.0 Released

[Smith, Scott D]

Hi Dietmar,

It looks like there are two encoding schemes used within OCL.  In taking a
quick random sample, I found some files encoded as Unicode, while others are
encoded as Western European.  I think the pattern is as follows: classes
that are defined in the ECMA standard are unicode (baselined from output of
the OCXT tool), while additional classes that were added to implement the
standard are Western European (created by our dev environment).  This is
invisible to us in our environment, but we will go through and convert them
all to one encoding.  Are you able to read some files?

For example, I suspect you will be able to read:
System.IO.Stream.cs

but not:
System.IO.StdOutputStream.cs


Thanks for the catch.

Have a nice weekend,
Scott

-----Original Message-----
From: Dietmar Maurer [mailto:dietmar@maurer-it.com]
Sent: Wednesday, November 21, 2001 11:24 AM
To: Smith, Scott D
Cc: 'mono-list@ximian.com'
Subject: Re: [Mono-list] OCL 0.2.0 Released


On Wed, 2001-11-21 at 18:25, Smith, Scott D wrote:
> Hi All,
> 
> OCL 0.2.0 has just been released, which is based on the final draft ECMA
CLI
> XML library definition file.  No changes are expected in the final draft
> ECMA CLI standard, so OCL 0.2.0 signatures should match the official ECMA
> CLI standard when it is approved by the ECMA General Assembly.  In
addition,
> OCL now contains stub code or implementation and hyperlinked HTML
> documentation for all Compact and Kernel library classes (BCL, RIL, XML,
> Networking, and Reflection).  For details, visit:
> 
> http://sourceforge.net/projects/ocl
> 

I am unable to read the source files contained in the package. It seems
they are UTF16 encoded?

- Dietmar