Re: unicode apps?

From:

"Tom Serface" <tserface@msn.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 7 Aug 2006 07:55:05 -0700

Message-ID:

<eiSt5FjuGHA.4384@TK2MSFTNGP04.phx.gbl>

I also use internationalized versions of date and number formatting routines
regardless of whether or not I'm using Unicode. The time difference when
formating is reasonable. For example:

//
// Format a date in the locale convention, short format. If tm is 0 the
current date is returned.
//
CString NLSDateFormat(CTime tm)
{
    SYSTEMTIME systime;
    if (tm == 0) {
        // get the current time
        GetSystemTime(&systime);
    }
    else {
        // convert the CTime
        tm.GetAsSystemTime(systime);
    }

    int size;
    CString cs;
    size = ::GetDateFormat(LOCALE_USER_DEFAULT, DATE_SHORTDATE, &systime,
NULL, NULL, 0);
    ::GetDateFormat(LOCALE_USER_DEFAULT, DATE_SHORTDATE, &systime, NULL,
cs.GetBuffer(size), size);
    cs.ReleaseBuffer();
    return cs;
}

PTCHAR Comma(LONGLONG value,PTCHAR bufout, UINT nSize)
{
    TCHAR bufin[30]; // 30 digits is a really big number
    TCHAR dsep[5], tsep[5];
    NUMBERFMT fmt;
    fmt.NumDigits = 0;
    ::GetLocaleInfo(LOCALE_USER_DEFAULT,LOCALE_ILZERO,bufin,2);
    fmt.LeadingZero = _ttoi(bufin);
    fmt.Grouping = 3;
    ::GetLocaleInfo(LOCALE_USER_DEFAULT,LOCALE_SDECIMAL,dsep,4);
    fmt.lpDecimalSep = dsep;
    ::GetLocaleInfo(LOCALE_USER_DEFAULT,LOCALE_STHOUSAND ,tsep,4);
    fmt.lpThousandSep = tsep;
    ::GetLocaleInfo(LOCALE_USER_DEFAULT,LOCALE_INEGNUMBER ,bufin,2);
    fmt.NegativeOrder = _ttoi(bufin);
    _stprintf_s(bufin, _T("%I64d"), value);
    ::GetNumberFormat(LOCALE_USER_DEFAULT, 0, bufin, &fmt, bufout, nSize);
    return bufout;
}

Tom

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:pcfdd2pl53j21qnvrqdjbsvbpt258vidim@4ax.com...

Key here is to do what I've been doing for about 7 years now: coding
"Unicode-aware". This
makes transition to Unicode trivial. I'm also tending these days to code
"locale-aware"
and use NLS functions for formatting numbers, dates, etc. because Unicode
is about 10% of
the internationalization effort.
joe

On Thu, 3 Aug 2006 12:04:37 -0600, "Jonathan Wood"
<jwood@softcircuits.com> wrote:

In addition to my other comments, I will also recommend you do things
like:

TCHAR c;
CString s = _T("This is a string.");

There is no reason not to make your application compatible with both
Unicode
and multibyte builds. You can always switch over and recompile to ensure
you
have done this.

Using these T macros, etc. is a good habit.

Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm