../../programs/winetest/runtest -q -P wine -M kernel32.dll -T ../.. -p tests/kernel32_test.exe.so tests/locale.c && touch tests/locale.ok fixme:string:OLE_GetFormatA datelen = 0, returning 255 fixme:string:OLE_GetFormatA datelen = 0, returning 255 tests/locale.c:260: Test failed: GetNumberFormat with len=2 got 2 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx instead of 2,xx tests/locale.c:269: Test failed: GetNumberFormat got 2 353,00 instead of 2,353.00 tests/locale.c:214: Test failed: GetCurrencyFormat with len=0: got 8 instead of 7 tests/locale.c:219: Test failed: GetCurrencyFormat got 23xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx instead of $23.53 tests/locale.c:226: Test failed: GetCurrencyFormat got 23,53 ¤ instead of $23.53 tests/locale.c:227: Test failed: GetCurrencyFormat: got 8 instead of 7 make[2]: *** [tests/locale.ok] Erreur 6 make[2]: Quitte le répertoire `/home/wine/dlls/kernel' make[1]: *** [kernel/__test__] Erreur 2 make[1]: Quitte le répertoire `/home/wine/dlls' make: *** [dlls/__test__] Erreur 2
LANG is set to fr_FR, and the '¤' is, I think, the euro symbol.test is ok when LANG is set to en_US for example.
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Tue, 11 Jun 2002, [iso-8859-1] Sylvain Petreolle wrote: [Regression test output w/ locale tests failing under fr_FR]
The tests also fail under en_GB:
tests/locale.c:219: Test failed: GetCurrencyFormat got �2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx^E instead of $23.53 tests/locale.c:226: Test failed: GetCurrencyFormat got �23.53 instead of $23.53
It looks like the regression tests assume you are using a US locale. If you set LANG=en_US it works fine.
BTW, has MS taken down their API reference from the MSDN website? I was looking for the Win32 API reference on the MSDN web-site (to try and fix the regression tests), but I couldn't find them. As far as I can remember, it was available from MSDN Home --> MSDN Library --> Windows Development --> Win32 API ... but there's only a sample chapter from a book there now.
Cheers,
---- Paul Millar
Paul Millar wrote:
BTW, has MS taken down their API reference from the MSDN website? I was looking for the Win32 API reference on the MSDN web-site (to try and fix the regression tests), but I couldn't find them. As far as I can remember, it was available from MSDN Home --> MSDN Library --> Windows Development --> Win32 API ... but there's only a sample chapter from a book there now.
Cheers,
It's still there, just spread out a lot.
Depends on what you are looking for. Usually, what I would do is type in the "search" area the name of the function, and then click on the link (careful not to click where the URL has something along the lines of "ceui", because that's windows CE). From there, everything is cross referenced, and you can click the "up".
The paths to other functions have become much much much much much less convinent, but I believe the same has also happened to the latest MSDNs on CD - they are horrible user interface, to the point where you would usually rather use the online site (or an old MSDN CD). It's really interesting how MS's UI is deteriorating as time goes on (with the sole exception of Win 3.11->Win95). I have had to spend one day with Windows XP (install a friend's computer), and spent the entire time cursing about the UI.
Shachar
Shachar Shemesh a écrit :
Paul Millar wrote:
BTW, has MS taken down their API reference from the MSDN website? I was looking for the Win32 API reference on the MSDN web-site (to try and fix the regression tests), but I couldn't find them. As far as I can remember, it was available from MSDN Home --> MSDN Library --> Windows Development --> Win32 API ... but there's only a sample chapter from a book there now.
Cheers,
It's still there, just spread out a lot.
Depends on what you are looking for. Usually, what I would do is type in the "search" area the name of the function, and then click on the link (careful not to click where the URL has something along the lines of "ceui", because that's windows CE). From there, everything is cross referenced, and you can click the "up".
Doh! Mails crossed each other. Almost the same wording though...
The paths to other functions have become much much much much much less convinent, but I believe the same has also happened to the latest MSDNs on CD - they are horrible user interface, to the point where you would usually rather use the online site (or an old MSDN CD). It's really interesting how MS's UI is deteriorating as time goes on (with the sole exception of Win 3.11->Win95). I have had to spend one day with Windows XP (install a friend's computer), and spent the entire time cursing about the UI.
I tried a few times to get to the Win32 API through the menus on the left. Sometimes I would get there, sometimes not. So I gave up, and now use the search method. Never used an MSDN CD, but your comment doesn't make me want to use one.
Shachar
Vincent
On Wed, 12 Jun 2002, Vincent [iso-8859-1] B�ron wrote:
Shachar Shemesh a �crit :
Paul Millar wrote:
[finding APIs on MSDN?]
It's still there, just spread out a lot.
Depends on what you are looking for. Usually, what I would do is type in the "search" area the name of the function, and then click on the link (careful not to click where the URL has something along the lines of "ceui", because that's windows CE). From there, everything is cross referenced, and you can click the "up".
Doh! Mails crossed each other. Almost the same wording though...
Thanks for the info!
---- Paul Millar
Paul Millar a écrit :
On Tue, 11 Jun 2002, [iso-8859-1] Sylvain Petreolle wrote: [Regression test output w/ locale tests failing under fr_FR]
The tests also fail under en_GB:
tests/locale.c:219: Test failed: GetCurrencyFormat got £2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx^E instead of $23.53 tests/locale.c:226: Test failed: GetCurrencyFormat got £23.53 instead of $23.53
It looks like the regression tests assume you are using a US locale. If you set LANG=en_US it works fine.
BTW, has MS taken down their API reference from the MSDN website? I was looking for the Win32 API reference on the MSDN web-site (to try and fix the regression tests), but I couldn't find them. As far as I can remember, it was available from MSDN Home --> MSDN Library --> Windows Development --> Win32 API ... but there's only a sample chapter from a book there now.
The layout of MSDN has changed over the course of a few months. The way I use it now is to search for a specific API on the frontpage, skipping the WinCE references that sometimes manage to get on top of the results. If you want something more generic (categories rather than a particular API), I suggest you to find a specific API of that category and then to go up a level.
Cheers,
Paul Millar
Vincent
-
Paul Millar -
Shachar Shemesh -
Sylvain Petreolle -
Vincent Béron