Re: Fw: Unicode & space in programming & l10n

From: Steve Summit (scs@eskimo.com)
Date: Fri Sep 22 2006 - 18:00:16 CDT

  • Next message: Richard Wordingham: "Re: Fw: Unicode & space in programming & l10n"

    Ken Whistler wrote:
    > It is perfectly fine for UTF-32, if you do this correctly.
    > For example:
    >
    > typedef unsigned short UShort16;
    > typedef unsigned int UInt32;
    >
    > typedef UShort16 utf16char;
    > typedef UInt32 utf32char;

    Please don't do this! Please do

            #include <stdint.h>

            typedef uint16_t utf16char;
            typedef uint32_t utf32char;

    instead.

    > At that point, you can safely port your entire code to *any*
    > platform, with at most one compiler-specific #ifdef in your
    > fundamental header file.

    With at most zero compiler-specific #ifdefs.



    This archive was generated by hypermail 2.1.5 : Fri Sep 22 2006 - 18:02:17 CDT