Unicode string normalization in C/C++

Question

Am wondering how to normalize strings (containing utf-8/utf-16) in C/C++. In .NET there is a function String.Normalize .

I used UTF8-CPP in the past but it does not provide such a function. ICU and Qt provide string normalization but I prefer lightweight solutions.

Is there any "lightweight" solution for this?

Raber

Answer 1

As I wrote in another question, utf8proc is a very nice, lightweight, library for basic Unicode functionality, including Unicode string normalization.

Bilge

I have problems in visual studio 2010 with utf8proc. typedef unsigned char bool; -> dosen't compile in C++ – Raber

I don't have familiarity with VS 2010, but can't you compile the library as a C library, and link it in that way? – Bilge

The problem is in the header file that's why we can't use it even as a static library. A simple workaround is to replace bool, true, false to _bool, _true, _false occurences. Example : typedef unsigned char _bool; enum {_false, _true}; – Raber

Yes, you could probably do that without too much trouble - it isn't a very complicated library. We also had to make one or two minor changes like that. – Bilge

The Julia team has an updated fork of utf8proc called libmojibake (github.com/JuliaLang/libmojibake) which is updated for Unicode 7 support. (It also has some other small fixes, e.g. it fixed C++ compatibility.) – Andiron

Answer 2

For Windows, there is the NormalizeString() function (unfortunately for Vista and later only - as far as I see on MSDN):

http://msdn.microsoft.com/en-us/library/windows/desktop/dd319093%28v=vs.85%29.aspx

It's the simplest way to go that I have found so far. I guess it's quite lightweight too.

int NormalizeString(
    _In_      NORM_FORM NormForm,
    _In_      LPCWSTR   lpSrcString,
    _In_      int       cwSrcLength,
    _Out_opt_ LPWSTR    lpDstString,
    _In_      int       cwDstLength
);

Ocher

Answer 3

A good UTF-8 solution is glib's g_utf8_normalize() function. Would require to convert std::wstring to std::string (utf16 to utf8) if you need this for wstring too (which would make it quite an expensive solution, hence I'm looking myself for a better solution, if possible with pure C++(11) means).

Hiragana

Answer 4

You could build ICU with minimal (or possibly, no other data- I think all of the normalization data is now internal), and then statically link. I haven't tried this recently, but I believe the total size is pretty small in that case.

Sigh

Answer 5

"Lightweight" in your context means "with limited functionality". I would use ICU source as an example, and reference http://unicode.org/reports/tr15/ to implement this "lightweight" functionality.

Ungainly