[Bug 9583] CompareStringW gives incorrect result for some wide strings

http://bugs.winehq.org/show_bug.cgi?id=9583

--- Comment #7 from Dmitry Timoshkov   2007-09-05 05:57:42 ---
> I'm not familiar with LCMapStringW. What kind of flags should I call it with?

LCMAP_SORTKEY
> > Another point that may make the testing easier: most likely just specifying
> > an appropriate locale (0x41d or 0x409) in the 1st argument of CompareStringW
> > and LCMapStringW is enough to avoid system locale changes.
>
> Since the test program prints out the locale at startup, there's no risk of
> mistakes. Using GetUserDefaultLCID() is convenient, since it allows us to test
> different locale just by changing the locale in the control panel, instead of
> having to recompile.

Passing explicit locale to CompareStringW and LCMapStringW makes sure that
you are testing real and not implicit behaviour. Also having a common testing
function that takes a locale id as a parameter helps to avoid recompilations.