Renaming sal_Unicode to a less misleading name?

[Norbert Thiebaud]

On Mon, Feb 15, 2016 at 10:57 AM, Stephan Bergmann <sbergman at redhat.com> wrote:
>
>
> Instead of introducing yet more typedefs, we'll more and more move to C++11
> char16_t, char32_t (which already started, now that sal_Unicode is a typedef
> for char16_t, for non-WNT LIBO_INTERNAL).

Oh, sure absolutely...  the only intention here is to distinguish
unicode representing type from regular scalar.
I am absolutely not in love with the sal_* typedef scheme... If there
are 'standard' type, lets use them.

Norbert