UTF8.library, progress and some information about the up coming version 4.

I'm a bit amazed by number of download of my UTF8.library, for library that is not used by any application it gets a lot of downloads, it does make my happy.

47 Downloads currently on version 3, not bad at all,

A new version will be out in today or tomorrow, I think, just need to check that every thing is ok.

The new library will contain 7 more string handling rutins. 1 more routine to check Byte Size.

As you might have noticed, naming of function I use Relefact names used in std:string C++ class function names Microsoft uses on there string class. Of course there are some variation because we need to support for sheard memory, when dealing whit strings.

As I'm nearing completion, I hope that I can return to the project I was working before starting on UTF8.Library.

There might be another 10 to 15 routines we don't have yet in this library to render the other libraries redundant. While your waiting you just need to mix and match what you need for that different libraries.

I will so like some feed back form you developers on what routines you like to see in the next version, what do you think I have forgotten, are there thing you think I should do different?

Better to tell me now before I decide to freeze features.

Also the language alphabet has been a bit annoying, I hope its possible to get this from some where in the OS, or else I will need to ask people provide there Language alphabets in UTF8 format as text file.

Because we will need it do casecmp, upper, lower and sorting, the standard one's only really support English it seams, and thats no good.

Things I'm working on for the mommet.

I have been busy reading about MS C#, and about classes, in order to make it interesting I wanted to make a program, that will be useful to me and maybe others, a cross platform application.

I know C# is not really portable but its more portable then VirtualBasic, at lest it has most of the C++ syntax, even if .Net Framework is different, there are a few different versions of .Net Framework you have XNA a Game API used on XBOX, and then Portable Class Library.

The Portable Class Library is more or less useless, because everything has to be recreated anyway, and its too small to be of any use.

Supporting just XNA does not make lot of senses, if AmigaOS can support some thing, there is no point in limiting it to XNA.

The full .Net Framework is too big of job to support, so what I have basically been doing to create C++ classes for what I have used in my project.

And been trying to get same program to work on AmigaOS whit small modifications, just by implementing the classes need to for the program.

So to make this clear this is not XNA, .NET or Portable Class Library this is some thing new.

Hopefully this will open some door for cross platform applications and portability between the two operating systems.

The only problem is that AmigaOS has yet to come out of the stone age.

Like File Notifications is way better on Windows, then on AmigaOS where its pretty primitive.

UTF8 encoding really sucked on AmigaOS, but works well on Windows, and I believe it has become the standard encoding for text files in windows7.

So I have spent a week trying to figure out how to do things, and ended up whit writing my own UTF8.Library it has now been uploaded to OS4Depot.net.

I'm hopeful that UTF8.Library will make more programs UTF8 friendly. 

 

More information to come on what I'm working on.