June 2013 - Wine-Devel - list.winehq.org

Re: winex11.drv: When skipping unknown attribute also skip it's value.

by Michael Stefaniuc

On 06/30/2013 11:29 PM, Ričardas Barkauskas wrote: > --- > dlls/winex11.drv/opengl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > 0001-winex11.drv-When-skipping-unknown-attribute-also-skip-.txt > > > diff --git a/dlls/winex11.drv/opengl.c b/dlls/winex11.drv/opengl.c > index 0f937cb..c7f78c5 100644 > --- a/dlls/winex11.drv/opengl.c > +++ b/dlls/winex11.drv/opengl.c > @@ -921,7 +921,7 @@ static int ConvertAttribWGLtoGLX(const int* iWGLAttr, int* oGLXAttr, struct wgl_ > TRACE("pAttr[%d] = GLX_RGBA_UNSIGNED_FLOAT_TYPE_EXT: %x\n", cur, pop); > break ; > default: > - FIXME("unsupported %x WGL Attribute\n", iWGLAttr[cur]); > + FIXME("unsupported %x WGL Attribute\n", iWGLAttr[cur++]); Side effects in the debug output functions should be avoided. > break; > } > ++cur; > bye michael

June 30, 2013

Duplicate UUID in oleaut32:tmarshal test

by Thomas Faber

I just tried running midl on dlls/oleaut32/tests/tmarshal.idl and it complained: tmarshal.idl(83) : error MIDL2270 : duplicate UUID. Same as : ItestDual [ Interface 'ITestSecondDisp' ] This doesn't seem like it's intentional. But just giving ITestSecondDisp a new uuid causes the following test failures on Windows: tmarshal.c:1861: Test failed: external_connections = 2 tmarshal.c:1864: Test failed: external_connections = 2 tmarshal.c:192: Test failed: fLastReleaseCloses = 1 I could try to figure this out, but it's probably better if someone familiar with the subject could have a look instead. (also, assuming this is a bug in the test, we might want to add that check to widl, it seems pretty useful ;]) Thanks, Thomas

June 30, 2013

Re: widl: Do not generate C structure for empty interfaces. (try 2)

by Thomas Faber

On 2013-06-27 13:33, Jacek Caban wrote: > That > said, if such interfaces are just obscure special case, I would say we > shouldn't care. We may easily avoid them (I just sent a patch avoiding > it in mshtml). Ah, I hadn't even considered changing the interface. Seemed like it was something mandated by Mozilla's use of it. This indeed seems to be the best solution to the immediate problem of mshtml not building with MSVC. Thanks! > If you want a better solution to avoid such problems in the future, I > would suggest adding an error, like midl does. This will, however, > require some more changes in Wine. At least MSHTML already has an > interface identical to IUnknown (nsISupports), which would cause the > error. This should be solvable with some tricks. That sounds like the smart thing to do. I've attached the simplest version that comes to mind. The interfaces I needed to exempt were IUnknown (naturally), ID3DInclude (which PSDK seems to define via cpp_quote), and nsISupports as you already mentioned. Midl also seems to have an "if not inside a library" condition, which I'll try to add as well. I'd have liked to use is_object in widl, but that also triggers on the odl attribute. I'll send it to -patches once I'm satisfied with it, but I'm pretty fond of the simple approach already. Let me know if you have any comments. Thanks a lot. -Thomas

June 30, 2013

Re: [patch]update po/ja.po for wine ver.1.6-rc4

by Akihiro Sagawa

Hi Akira, Thank you for your contribution. Regarding Japanese translation, please consider following things. Firstly, those untranslated terms cannot be fully translated into Japanese. This is the reason why I didn't translate 100% message. In po file, please keep untranslated if we don't need to translate the message. Secondly, I don't translate the message before nearly 100% sure about message context. We should learn the conetext and test how the message is shown in the application. In my opinion, untranslated English terms are easy to search web pages. This helps a user who don't familiar to technical words. If we translate to ill-defined message, a user cannot help himself/herself with search engines. Thirdly, these untranslated messages are not so important for average applications... Did you notice these untranslated messages on some applications? Anyway, I continue to commented on this. On Sun, 30 Jun 2013 22:03:21 +0900, Akira Nakagawa wrote: > #: crypt32.rc:83 > msgid "Serialized Signature Serial Number" > -msgstr "" > +msgstr "整序された署名の順番" This translated message doesn't mean "Serial Number". > #: crypt32.rc:84 > msgid "Principal Name" > -msgstr "" > +msgstr "主要名称" "主要名称" looks like Chinese term. Not used in Japan at all. How about プリンシパル名? > #: crypt32.rc:94 > msgid "Policy Mappings" > -msgstr "" > +msgstr "ポリシーの表示" Mappings doesn't mean 表示 (=display?). > #: crypt32.rc:96 > msgid "Cross-Certificate Distribution Points" > -msgstr "" > +msgstr "複数の署名の配布ポイント" Cross-Certificate doesn't mean 複数の署名 (=multiple signatures?). > #: crypt32.rc:98 > msgid "Application Policy Mappings" > -msgstr "" > +msgstr "アプリケーションのポリシーの表示" Mappings doesn't mean 表示. (ditto) Please avoid ～の～の～ form. > #: crypt32.rc:99 > msgid "Application Policy Constraints" > -msgstr "" > +msgstr "アプリケーションのポリシーの制約" ditto. > #: crypt32.rc:107 > msgid "PKCS 7 Signed" > -msgstr "" > +msgstr "署名付きのPKCS 7" PKCS #7 is Cryptographic Message Syntax Standard and updated in RFC 5652. RFC 5652 defines six content types: data, signed-data, enveloped-data, digested-data, encrypted-data, and authenticated-data. So, "PKCS 7 Signed" means the second data type. > #: crypt32.rc:108 > msgid "PKCS 7 Enveloped" > -msgstr "" > +msgstr "保護されたPKCS 7" ditto. PKCS 7 is not enveloped. The data is enveloped by PKCS 7. > #: crypt32.rc:109 > msgid "PKCS 7 Signed Enveloped" > -msgstr "" > +msgstr "保護された署名付きのPKCS 7" ditto. > #: crypt32.rc:110 > msgid "PKCS 7 Digested" > -msgstr "" > +msgstr "ダイジェストのPKCS 7" ditto. > #: crypt32.rc:111 > msgid "PKCS 7 Encrypted" > -msgstr "" > +msgstr "暗号化されたPKCS 7" ditto. > #: crypt32.rc:112 > msgid "Previous CA Certificate Hash" > -msgstr "" > +msgstr "以前のCA 署名のハッシュ" Certificate doesn't mean "署名" (signature). A space character is needed before "CA". > #: crypt32.rc:113 > msgid "Virtual Base CRL Number" > -msgstr "" > +msgstr "仮想CRLナンバー" This message doesn't contain "Base" term. A space character is needed both sides of "CRL". > #: crypt32.rc:114 > msgid "Next CRL Publish" > -msgstr "" > +msgstr "次のCRL 公開" A space character is needed before "CRL". > #: crypt32.rc:119 > msgid "Dummy Signer" > -msgstr "" > +msgstr "ダミーの署名" Signer is a person or an authority. Please don't confuse signer with sign. > #: crypt32.rc:122 > msgid "Enforce Certificate Chain Policy" > -msgstr "" > +msgstr "証明書チェーンのポリシーを適用" Enforce is more powerful word. > #: crypt32.rc:193 > msgid "End Entity" > -msgstr "" > +msgstr "終了値" In this case "End" might not mean closure. This might mean "End user"'s end. > #: cryptdlg.rc:29 > msgid "Policy Qualifier Info" > -msgstr "" > +msgstr "ポリシーの修飾子情報" This message doesn't need space between words. > #: cryptui.rc:298 > msgid "Personal Information Exchange/PKCS #12 (*.pfx; *.p12)" > -msgstr "" > +msgstr "個人情報交換ファイル/PKCS #12 (*.pfx; *.p12)" "個人情報交換ファイル" isn't commonly used term. Where is the source of this term? I searched this term with google, only 9 pages are found. But "Personal Information Exchange" is used over 47,000 pages --- of course, I limited to Japanese pages. Thus I ask you to keep this term untranslated. > #: cryptui.rc:405 > msgid "&DER-encoded X.509 (*.cer)" > -msgstr "&DER符号化された X.509 (*.cer)" > +msgstr "DER符号化された X.509(&D) (*.cer)" I think this style is redundant. > #: cryptui.rc:407 > msgid "Ba&se64-encoded X.509 (*.cer):" > -msgstr "Ba&se64符号化された X.509 (*.cer):" > +msgstr "Base64で符号化された X.509(&S) (*.cer):" ditto. > #: cryptui.rc:409 > msgid "&Cryptographic Message Syntax Standard/PKCS #7 Message (*.p7b)" > -msgstr "&Cryptographic Message Syntax Standard/PKCS #7 メッセージ (*.p7b)" > +msgstr "暗号メッセージ構文/PKCS #7 メッセージ(&C) (*.p7b)" "Standard" term is omitted. > #: cryptui.rc:413 > msgid "&Personal Information Exchange/PKCS #12 (*.pfx)" > -msgstr "" > +msgstr "個人情報交換ファイル(&P)/PKCS #12 (*.pfx)" "個人情報交換ファイル" is not common usage. (ditto) (&P) position doesn't match previous message. > #: cryptui.rc:75 > msgid "Personal Information Exchange (*.pfx; *.p12)" > -msgstr "" > +msgstr "個人情報交換ファイル (*.pfx; *.p12)" ditto. > #: cryptui.rc:94 > msgid "Personal Information Exchange" > -msgstr "" > +msgstr "個人情報変換ファイル" Why not use 交換 for Exchange as in previous message? This message use 変換 for Exchange term. > #: cryptui.rc:158 > msgid "Personal Information Exchange (*.pfx)" > -msgstr "" > +msgstr "個人情報変換ファイル (*.pfx)" ditto. ------------------- Following shell directory names are not translated in Windows Vista Japanese edition. Wine follows Vista's notation. We discussed about this two years ago [1]. [1] http://www.winehq.org/pipermail/wine-devel/2011-January/088390.html So, you don't need translate into Japanese for now. > #: shell32.rc:201 > msgid "My Documents" > -msgstr "" > +msgstr "マイドキュメント" > > #: shell32.rc:202 > msgid "Favorites" > -msgstr "" > +msgstr "お気に入り" > > #: shell32.rc:203 > msgid "StartUp" > -msgstr "" > +msgstr "スタートアップ" > > #: shell32.rc:204 > msgid "Start Menu" > -msgstr "" > +msgstr "スタートメニュー" > > #: shell32.rc:205 > msgid "My Music" > -msgstr "" > +msgstr "マイミュージック" > > #: shell32.rc:206 > msgid "My Videos" > -msgstr "" > +msgstr "マイビデオ" > > #: shell32.rc:207 > msgctxt "directory" > msgid "Desktop" > -msgstr "" > +msgstr "デスクトップ" > > #: shell32.rc:208 > msgid "NetHood" > -msgstr "" > +msgstr "ネットワーク内" > > #: shell32.rc:209 > msgid "Templates" > -msgstr "" > +msgstr "テンプレート" > > #: shell32.rc:210 > msgid "PrintHood" > -msgstr "" > +msgstr "プリンタ内" > > #: shell32.rc:211 winhlp32.rc:45 > msgid "History" > -msgstr "" > +msgstr "ヒストリ" > > #: shell32.rc:212 > msgid "Program Files" > @@ -7959,7 +7962,7 @@ msgstr "Program Files" > > #: shell32.rc:214 > msgid "My Pictures" > -msgstr "" > +msgstr "マイピクチャ" > > #: shell32.rc:215 > msgid "Common Files" > @@ -7967,23 +7970,23 @@ msgstr "Common Files" > > #: shell32.rc:216 shell32.rc:147 shell32.rc:232 > msgid "Documents" > -msgstr "" > +msgstr "ドキュメント" > > #: shell32.rc:217 > msgid "Administrative Tools" > -msgstr "" > +msgstr "管理者用ツール" > > #: shell32.rc:218 > msgid "Music" > -msgstr "" > +msgstr "ミュージック" > > #: shell32.rc:219 > msgid "Pictures" > -msgstr "" > +msgstr "ピクチャ" > > #: shell32.rc:220 > msgid "Videos" > -msgstr "" > +msgstr "ビデオ" > > #: shell32.rc:213 > msgid "Program Files (x86)" > @@ -7991,19 +7994,19 @@ msgstr "Program Files (x86)" > > #: shell32.rc:221 > msgid "Contacts" > -msgstr "" > +msgstr "連絡先" > > #: shell32.rc:222 winefile.rc:110 > msgid "Links" > -msgstr "" > +msgstr "リンク" > > #: shell32.rc:223 > msgid "Slide Shows" > -msgstr "" > +msgstr "スライドショー" > > #: shell32.rc:224 > msgid "Playlists" > -msgstr "" > +msgstr "プレイリスト" > > #: shell32.rc:148 taskmgr.rc:326 > msgid "Status" > @@ -8019,35 +8022,35 @@ msgstr "機種名" > > #: shell32.rc:225 > msgid "Sample Music" > -msgstr "" > +msgstr "サンプルミュージック" > > #: shell32.rc:226 > msgid "Sample Pictures" > -msgstr "" > +msgstr "サンプルピクチャ" > > #: shell32.rc:227 > msgid "Sample Playlists" > -msgstr "" > +msgstr "サンプルプレイリスト" > > #: shell32.rc:228 > msgid "Sample Videos" > -msgstr "" > +msgstr "サンプルビデオ" > > #: shell32.rc:229 > msgid "Saved Games" > -msgstr "" > +msgstr "保存済みのゲーム" > > #: shell32.rc:230 > msgid "Searches" > -msgstr "" > +msgstr "検索" > > #: shell32.rc:231 > msgid "Users" > -msgstr "" > +msgstr "ユーザー" > > #: shell32.rc:233 > msgid "Downloads" > -msgstr "" > +msgstr "ダウンロード" > ------------------- > #: netstat.rc:28 > msgid "Proto" > -msgstr "" > +msgstr "合意" Proto means protocol, but there is no enough space to display it. > #: oleview.rc:138 > msgid "Registry" > -msgstr "" > +msgstr "レジストリ" Oleview has a small issue. When I try this translation before, it can't display well if this message is Japanese. So, please verify that these messages are shown properly in the application. > #: oleview.rc:139 > msgid "Implementation" > -msgstr "" > +msgstr "実装" ditto. > #: oleview.rc:140 > msgid "Activation" > -msgstr "" > +msgstr "発動" ditto. > #: winefile.rc:109 > msgid "Index/Inode" > -msgstr "" > +msgstr "索引・Iノード" Although easily guess it, Iノード is not widely used. iノード might be preferred but more common term is "inode". inode (as Japanese technical term) is used in Wikipedia[1], Linux Japanese Manual (debugfs [2]), WDIC[3]. [1] http://ja.wikipedia.org/wiki/Inode [2] http://linuxjm.sourceforge.jp/html/e2fsprogs/man8/debugfs.8.html [3] http://www.wdic.org/w/TECH/inode Contact me for any questions. Regards, Akihiro Sagawa

June 30, 2013

[PATCH] advapi32: RegDeleteKey tests for merged view of HKCR

by George Stephanos

http://newtestbot.winehq.org/JobDetails.pl?Key=1403 --- dlls/advapi32/tests/registry.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/dlls/advapi32/tests/registry.c b/dlls/advapi32/tests/registry.c index 1784118..4e74a07 100644 --- a/dlls/advapi32/tests/registry.c +++ b/dlls/advapi32/tests/registry.c @@ -2341,6 +2341,27 @@ static void test_classesroot(void) ok(res == ERROR_SUCCESS, "RegQueryValueExA failed: %d\n", res); ok(!strcmp( buffer, "hkcr" ), "value set to '%s'\n", buffer ); + /* delete subkey1 from hkcr (should point at user's classes) */ + res = RegDeleteKey(hkcr, "subkey1"); + ok(res == ERROR_SUCCESS, "RegDeleteKey failed: %d\n", res); + + /* confirm key was removed in hkey but not hklm */ + res = RegOpenKeyExA(hkey, "subkey1", 0, KEY_READ, &hkeysub1); + ok(res == ERROR_FILE_NOT_FOUND, "test key found in user's classes: %d\n", res); + RegCloseKey(hkeysub1); + res = RegOpenKeyExA(hklm, "subkey1", 0, KEY_READ, &hklmsub1); + ok(res == ERROR_SUCCESS, "test key not found in hklm: %d\n", res); + RegCloseKey(hklmsub1); + + /* delete subkey1 from hkcr again (which should now point at hklm) */ + res = RegDeleteKey(hkcr, "subkey1"); + ok(res == ERROR_SUCCESS, "RegDeleteKey failed: %d\n", res); + + /* confirm hkey was removed in hklm */ + res = RegOpenKeyExA(hklm, "subkey1", 0, KEY_READ, &hklmsub1); + ok(res == ERROR_FILE_NOT_FOUND, "test key found in hklm: %d\n", res); + RegCloseKey(hklmsub1); + /* final cleanup */ delete_key( hkey ); delete_key( hklm ); -- 1.8.3.msysgit.0

June 30, 2013

[website] Wine 1.6-rc4 freigegeben

by André Hentschel

--- news/de/2013062801.xml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 news/de/2013062801.xml

June 30, 2013

Re: [wine-devel] Re: Bug 24018 which appears to be a showstopper for running Cygwin on Wine

by André Hentschel

On 29.06.2013 23:34, Hin-Tak Leung wrote: > --- On Sat, 29/6/13, Alan W. Irwin <irwin(a)beluga.phys.uvic.ca> wrote: > > ... >>> Also, running cygwin on wine, compared to other windows >> software >> which has no unix/linux equivalents, is hardly a priority. >> >> That is obviously personally true for you. And for my >> personal needs >> Cygwin on Wine is a "would be nice" software build and test >> platform. > ... > > No. Just the fact that nobody else bothered to respond to this thread should convince you that getting cygwin is not a priority to most people who is knowledgeable and capable of hacking wine. > I've been following this thread. What i would like to point you all to is: http://wiki.winehq.org/CygwinSupport It describes why running cygwin on wine is not that senseless low priority thing. Further it's mentioned at: http://wiki.winehq.org/TodoList and http://wiki.winehq.org/UnitTestSuites

June 30, 2013

Re: [patch] full translation update for 16 rc4

by Frédéric Delanoy

On Sun, Jun 30, 2013 at 6:08 AM, 中川祥 <matyapiro31(a)gmail.com> wrote: > Hi, please resubmit this patch with your full name transliterated in English.

June 30, 2013

Re: [wine-devel] Re: Bug 24018 which appears to be a showstopper for running Cygwin on Wine

by Hin-Tak Leung

--- On Sat, 29/6/13, Alan W. Irwin <irwin(a)beluga.phys.uvic.ca> wrote: ... > > Also, running cygwin on wine, compared to other windows > software > which has no unix/linux equivalents, is hardly a priority. > > That is obviously personally true for you. And for my > personal needs > Cygwin on Wine is a "would be nice" software build and test > platform. ... No. Just the fact that nobody else bothered to respond to this thread should convince you that getting cygwin is not a priority to most people who is knowledgeable and capable of hacking wine. As for true for me - well, I have fixed or help fixed a few issue of wine with running microsoft products - embedded IE rendering, and Microsoft's development tool chain (yes, I am talking about Visual C++, and nmake, [Microsoft's make], and microsoft's manifest modification tool whose name I forget - the tool for Microsoft's way of modifying executable binaries post-compilation). Obviously my interests lies elsewhere. Mingw works alright. Cygwin is just not a priority for my time, and I sincerely hope that other people who are capable of improving wine would spend their time on more worthwhile causes. p.s. using words like "showstopper" actually put people off.

June 29, 2013

Re: [wine-devel] Re: Bug 24018 which appears to be a showstopper for running Cygwin on Wine

by Alan W. Irwin

On 2013-06-29 11:57+0100 Hin-Tak Leung wrote: > --- On Sat, 29/6/13, Alan W. Irwin <irwin(a)beluga.phys.uvic.ca> wrote: > > ... >>> The Mingw GNU toolchain works wells under wine. The >> cygwin GNU toolchain don't, the last time I checked. >> >> That may be true, but the best way to make that point about >> the Cygwin >> GNU toolchain is with official Cygwin bug reports rather >> than >> asserting stuff here in an anecdotal way. > > Anytime that a piece of windows software (including Cygwin) works on windows but not on wine, is a wine problem. No question. In fact I stated bug reports to Cygwin would probably only be taken seriously if they included a demonstration of the problem on the Microsoft version of Windows. > The fact that the such software developers (cygwin people) are nice enough to respond and adjust their software (cygwin) to fit a *flaw in wine* does not make the problem less a wine one. This statement misrepresents what has recently occurred with regard to bug 24018. Arjen Markus's bug report demonstrated the Cygwin fork problem on Microsoft Windows. Because of that the Cygwin developers were quickly able to verify and fix the problem. > The various problems of running cygwin in wine are already well-documented - just do a search on wine's bugzilla (there are over a dozen of those). Those have been mentioned before here, and I have looked at them. Cygwin is a very large collection of software so the number of bugs that are reported does not seem excessive to me, and for my personal needs (building and testing software on the Cygwin platform) I will only be using a subset of Cygwin so I may avoid encountering some of these bugs. Furthermore, some of these bugs (e.g., problems resizing a GUI) are not showstoppers, and most of them are quite old. At the same time the latest Wine is far superior to Wine-1.4 so some of those bugs may have just disappeared. I hope to find out about the actual status of Cygwin on Wine bugs once I can get setup.exe to work on Wine. > So the mere fact that the installer does not work correctly, is just another such problem. That's been covered already. We obviously disagree on this issue. > Also, running cygwin on wine, compared to other windows software which has no unix/linux equivalents, is hardly a priority. That is obviously personally true for you. And for my personal needs Cygwin on Wine is a "would be nice" software build and test platform. That is, it is actually a medium to low priority for me since I already have plenty to do extending my builds and tests of free software on the MinGW/MSYS/Wine platform to additional software packages. But our personal needs are not what is important here. From the more general perspective any problems running open-source software on Wine should be easier to debug (since all the details of the exact Windows system calls are known) than trying to debug problems with running proprietary software (e.g., some random game) on Wine where you have to guess at the details. As an illustration of that, three times during the 1.5.x series I have found Wine bugs or regressions as a result of running open source software on Wine. (Thankfully, all of those have been fixed by the Wine developers.) Cygwin is the largest distribution of open-source software that runs on Windows. It follows that Cygwin represents a good opportunity to find and fix Wine issues. In sum you have expressed your opinions on Cygwin and Wine and I have mostly disagreed with those opinions. Therefore, I think we have covered everything, and it is time to call a halt to this side-topic. So from now on my contributions to this thread will focus on the original topic which is problems in running setup.exe on Wine, i.e., bug 24018, and I urge you to do the same. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net) the Time Ephemerides project (timeephem.sf.net) PLplot scientific plotting software package (plplot.sf.net) the libLASi project (unifont.org/lasi) the Loads of Linux Links project (loll.sf.net) and the Linux Brochure Project (lbproject.sf.net) __________________________ Linux-powered Science __________________________

June 29, 2013