The attachment seems to have been mangled: when I looked at it here I
only got question marks in the translations. So unless the mangling only
happened here, that would be one reason why the patch has not been
applied.
Also, although the translation comes from Transifex.com, it looks like
you're the only author behind the changes in that patch, i.e. there's
presumably no copyright attribution issue. That may be worth noting in
the patch submission.
Could you resubmit your patch?
--
…
[View More]Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/
1 + e ^ ( i * pi ) = 0
[View Less]
2013/11/25 Lucas Zawacki <lfzawacki(a)gmail.com>:
> From: Lucas Zawacki <lfzawacki(a)gmail.com>
>
> ---
> news/pt/2013112201.xml | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> create mode 100644 news/pt/2013112201.xml
>
> diff --git a/news/pt/2013112201.xml b/news/pt/2013112201.xml
> new file mode 100644
> index 0000000..3fbff21
> --- /dev/null
> +++ b/news/pt/2013112201.xml
> @@ -0,0 +1,15 @@
> +<news>
> +<date&…
[View More]gt;22 de Novembro de 2013</date>
> +<title>Wine 1.7.7 lançado</title>
> +<body>
> +<p> A versão de desenvolvimento 1.7.7 já está disponível agora.</p>
> +<p> <a href="{$root}/announce/1.7.7">Novidades</a> desta versão:
> +<ul>
> + <li>Suporte a configuração de comportilhamente remote usando a biblioteca NetAPI do Samba.</li>
The word "remote" was not translated.
> + <li>Suporte a múltiplos layouts de teclado no driver de Mac.</li>
> + <li>Melhor suporte a uso embutido com XEMBED.</li>
> + <li>Suporte a arrays em VBScript.</li>
> + <li>Várias correções de bugs.</li>
> +<p><p>O código fonte está <a href="http://prdownloads.sourceforge.net/wine/wine-1.7.7.tar.bz2">disponível agora</a>.
> +Pacotes binários estão em processo de construção e irão aparecer em breve em suas respectivas <a href="{$root}/download">sessões da área de downloads</a>.
> +</p></body></news>
> --
> 1.7.10.4
Best wishes,
Bruno
[View Less]
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=3537
Your paranoid android.
=== wvista (32 bit htmldoc) ===
No test summary line found
=== w7pro64 (32 bit htmldoc) ===
No test summary line found
=== w8 (32 bit htmldoc) ===
htmldoc.c:2872: Test failed: unexpected command 74
On 11/25/2013 10:23, Sebastian Lackner wrote:
> + hr = CoCreateInstance(&CLSID_VideoRenderer, NULL, CLSCTX_INPROC_SERVER,
> + &IID_IUnknown, (LPVOID*)&pVideoRenderer);
> + ok(hr != S_OK || pVideoRenderer != NULL, "CoCreateInstance returned S_OK, but pVideoRenderer is NULL.\n");
> + if (hr != S_OK || !pVideoRenderer)
> + {
> + skip("VideoRenderer is not available, skipping QI test.\n");
> + return;
> + }
&…
[View More]gt; +
> QI_SUCCEED(pVideoRenderer, IID_IBaseFilter, pBaseFilter);
> RELEASE_EXPECT(pBaseFilter, 1);
It's enough to test for return value, also if wine supports this class
this should be win_skip(). What's a point of separate QI here? You could
CoCreateInstance with IID_IBaseFilter.
> + hr = IUnknown_QueryInterface(pVMR7, &IID_IVMRMonitorConfig, (LPVOID*)&pMonitorConfig);
> + ok(hr == S_OK, "IUnknown_QueryInterface returned %x.\n", hr);
> + ok(pMonitorConfig != NULL, "pMonitorConfig is NULL.\n");
> + if (!pMonitorConfig) goto out;
Is it really possible to fail here?
> + ok(info[numdev].guid.pGUID != &info[numdev].guid.GUID || memcmp(&info[numdev].guid.GUID, &max_guid, sizeof(max_guid)) != 0,
> + "GetAvailableMonitors returned info[%d].GUID = {FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF}, expected any other value.\n", numdev);
It's shorter to just print resulting guid.
> + /* check that result is filled out, we do not check if the values actually make any sense */
> + while (numdev--)
> + {
> + ok(info[numdev].uDevID != (UINT)-1,
> + "GetAvailableMonitors returned info[%d].uDevID = -1, expected != -1.\n", numdev);
> + ok(memcmp(&info[numdev].rcMonitor, &max_rect, sizeof(max_rect)) != 0,
> + "GetAvailableMonitors returned info[%d].rcMonitor = {-1, -1, -1, -1}, expected any other value.\n", numdev);
> + ok(info[numdev].hMon != (HMONITOR)0 && info[numdev].hMon != (HMONITOR)-1,
> + "GetAvailableMonitors returned info[%d].hMon = %p, expected != 0 and != -1.\n", numdev, info[numdev].hMon);
> + ok(info[numdev].dwFlags != (DWORD)-1,
> + "GetAvailableMonitors returned info[%d].dwFlags = -1, expected != -1.\n", numdev);
> + ok(info[numdev].szDevice[0] != 0 && info[numdev].szDevice[0] != (WCHAR)-1,
> + "GetAvailableMonitors returned info[%d].szDevice[0] = %d, expected != 0 and != -1.\n", numdev, info[numdev].szDevice[0]);
> + todo_wine ok(info[numdev].szDescription[0] != 0 && info[numdev].szDescription[0] != (WCHAR)-1,
> + "GetAvailableMonitors returned info[%d].szDescription[0] = %d, expected != 0 and != -1.\n", numdev, info[numdev].szDescription[0]);
> + ok(info[numdev].dwVendorId != (DWORD)-1,
> + "GetAvailableMonitors returned info[%d].dwVendorId = -1, expected != -1.\n", numdev);
> + ok(info[numdev].dwDeviceId != (DWORD)-1,
> + "GetAvailableMonitors returned info[%d].dwDeviceId = -1, expected != -1.\n", numdev);
> + ok(info[numdev].dwSubSysId != (DWORD)-1,
> + "GetAvailableMonitors returned info[%d].dwSubSysId = -1, expected != -1.\n", numdev);
> + ok(info[numdev].dwRevision != (DWORD)-1,
> + "GetAvailableMonitors returned info[%d].dwRevision = -1, expected != -1.\n", numdev);
> + }
Personally I don't like this, I think this should be more explicit - set
fields separately to some invalid value that shouldn't happen and check
it back. For example for string field it makes no sense setting it to -1
if it's always filled.
[View Less]
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=3510
Your paranoid android.
=== wxppro (32 bit) ===
No test summary line found
=== wvista (32 bit) ===
No test summary line found
=== w2008s64 (32 bit) ===
No test summary line found
=== w7pro64 (32 bit) ===
No test …
[View More]summary line found
=== w8 (32 bit) ===
No test summary line found
=== w864 (32 bit) ===
No test summary line found
=== w2008s64 (64 bit) ===
No test summary line found
=== w7pro64 (64 bit) ===
No test summary line found
=== w864 (64 bit) ===
No test summary line found
[View Less]
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=3506
Your paranoid android.
=== w2008s64 (64 bit http) ===
http.c:3615: Test failed: HttpQueryInfo failed 0
=== w7pro64 (64 bit http) ===
http.c:3615: Test failed: HttpQueryInfo failed 0
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://newtestbot.winehq.org/JobDetails.pl?Key=3505
Your paranoid android.
=== w7pro64 (32 bit http) ===
http.c:4450: Test failed: HttpSendRequest failed: 12057
http.c:4455: Test failed: expected secure flag to be set
=== w2008s64 (64 bit http) ===
http.c:3615: Test …
[View More]failed: HttpQueryInfo failed 0
=== w7pro64 (64 bit http) ===
http.c:3615: Test failed: HttpQueryInfo failed 0
[View Less]