Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language


 
 
Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

C Programming Language

ICU Unicode library


Hi
I am studying the ICU library. Has anyone here
any experience with it?

It is a freely available internationalization library
provided by IBM, with full UNICODE 2.0 support.

It provides support for C, and it looks very impressive.
I was wondering if that would be a good replacement
for the string support in C.

jacob

On May 30, 6:04 am, jacob navia <j@jacob.remcomp.fr> wrote:

> I am studying the ICU library. Has anyone here
> any experience with it?

> It is a freely available internationalization library
> provided by IBM, with full UNICODE 2.0 support.

> It provides support for C, and it looks very impressive.
> I was wondering if that would be a good replacement
> for the string support in C.

It duplicates the idiotic '\0' semantics from the C world.  As far as
I can tell, its really meant as a replacement for wchar_t based
strings.

--
Paul Hsieh
http://www.pobox.com/~qed/
http://bstring.sf.net/

websn@gmail.com wrote:
> On May 30, 6:04 am, jacob navia <j@jacob.remcomp.fr> wrote:
>> I am studying the ICU library. Has anyone here
>> any experience with it?

>> It is a freely available internationalization library
>> provided by IBM, with full UNICODE 2.0 support.

>> It provides support for C, and it looks very impressive.
>> I was wondering if that would be a good replacement
>> for the string support in C.

> It duplicates the idiotic '\0' semantics from the C world.

It has length delimited strings too.
What is impressive is the Unicode and internationalization support.
What I am thinking is replacing most of the string library
like strlower() or strupper() and several others with calls to that
library.

> As far as
> I can tell, its really meant as a replacement for wchar_t based
> strings.

It supports UTF8, UTF16 and UTF32, what is quite a feat.

jacob navia wrote:

> I am studying the ICU library. Has anyone here
> any experience with it?

> It is a freely available internationalization library
> provided by IBM, with full UNICODE 2.0 support.

> It provides support for C, and it looks very impressive.
> I was wondering if that would be a good replacement
> for the string support in C.

This newsgroup discusses the standard C language as defined in the
various C standards and (earlier versions) in K&R.  Not
miscellaneous libraries.  You are off-topic.

--
 <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
 <http://www.securityfocus.com/columnists/423>
 <http://www.aaxnet.com/editor/edit043.html>
 <http://kadaitcha.cx/vista/dogsbreakfast/index.html>
                        cbfalconer at maineline dot net

--
Posted via a free Usenet account from http://www.teranews.com

in comp.lang.c i read:
[re: icu as in <url:http://www.icu-project.org>]

>full UNICODE 2.0 support.

>It provides support for C, and it looks very impressive.  I was wondering
>if that would be a good replacement for the string support in C.

so only 3 major revisions out of date?  sounds like you are setting your
sights fairly low.

also, it forces c code into forms normal for java, and so you might find
some resistance to the changes you would demand of user's code to use your
add-on string library's str_lower function.

that aside, with the right wrappers icu isn't too annoying.

--
a signature

those who know me have no need of my name wrote:

I was always thinking in writing wrappers for it. But the idea
of allowing to specify the language where you want str_lower
to work is obviously a good one, since for instance german sz
is uppercase SS, and similar problems.
On May 30, 7:47 am, jacob navia <j@jacob.remcomp.fr> wrote:

> websn@gmail.com wrote:
> > On May 30, 6:04 am, jacob navia <j@jacob.remcomp.fr> wrote:
> >> I am studying the ICU library. Has anyone here
> >> any experience with it?

> >> It is a freely available internationalization library
> >> provided by IBM, with full UNICODE 2.0 support.

> >> It provides support for C, and it looks very impressive.
> >> I was wondering if that would be a good replacement
> >> for the string support in C.

> > It duplicates the idiotic '\0' semantics from the C world.

> It has length delimited strings too.

I was not aware of this.  Do you know if they are dynamic or if \U+0
is necessarily treated special?  Either way, perhaps I should take
another look at it.

> What is impressive is the Unicode and internationalization support.

Well obviously; its a full implementation of Unicode strings.

> What I am thinking is replacing most of the string library
> like strlower() or strupper() and several others with calls to that
> library.

Well sorting strings is where the real problems begin.  A different
*kind* of strcmp() function has to be designed.  You can't just
replace C's str* functions with ICU.  You want to just support it as a
addition to char * strings, and deprecate the whole wchar_t nonsense.

> > As far as
> > I can tell, its really meant as a replacement for wchar_t based
> > strings.

> It supports UTF8, UTF16 and UTF32, what is quite a feat.

The transfer formats are a triviality.  I'd be slightly more impressed
if they supported UTF-7 and UTF-1 as well.

--
Paul Hsieh
http://www.pobox.com/~qed/
http://bstring.sf.net/

Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc