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

Re: [website] Simplified Chinese translation for release 1.5.27

by Hin-Tak Leung

--- On Sat, 30/3/13, Jactry Zeng <jactry92(a)gmail.com> wrote: From: Jactry Zeng <jactry92(a)gmail.com> Subject: Re: [website] Simplified Chinese translation for release 1.5.27 To: htl10(a)users.sourceforge.net Cc: "Wine Devel" <wine-devel(a)winehq.org>, "Qian Hong" <fracting(a)gmail.com> Date: Saturday, 30 March, 2013, 10:41 2013/3/30 Hin-Tak Leung <htl10(a)users.sourceforge.net> > > > I think both are terrible translations but could not think of a better alternative off my head, so I went to consult google translate. It defaults to 運行時庫 for "runtime library" but allow me to choose a few other alternatives, among which is > > "執行階段程式庫" > > Don't you think that's much better!? Hi Hin-Tak, Thanks for your review. I also think both "运行时" or "运行时库" was not best translation. But I have seen a lot of documents in Simplified Chinese translated it in this way. Maybe it was not too accurate... And in my opinion, "运行时" meaning some function, "运行时库" meaning a runtime library. To be honest, I think a lot of Chinese translations of technical topics (or even not-technical topics) are quite poor, and little beyond a word-for-word substitution. run -> 运行 ("to convey/process", the more common use of "run", of 'using your legs faster than walking' is obviously wrong) time -> 时 ("hour", "during") library -> 库 ("storage container", the more common use of "library" to mean "collection of books" obviously wrong). Whereas "執行階段程式庫" meaning "the program/routine library of/in the execute stage" is quite a lot more fitting to what 'runtime library' actually means. As I was saying, one needs to be vigilant about automated translations being 'not quite correct'. I suspect it is a much abused practice in China, so you see the same (mis-)usage over and over. There are entire web sites devoted to poorly translated public signs in China and making fun of them. It is quite educational - one gets lazy and and accepts the occasional poor translation, but seeing similar but slightly different mistakes collected in a large quantity really makes one think. 2013/3/30 Jactry Zeng <jactry92(a)gmail.com> > > I translated it as "高质量" meaning a picture have hight resolution. Here has a typo, hight -> higher .... -- Regards, Jactry Zeng

March 30, 2013

Re: [website] Simplified Chinese translation for release 1.5.27

by Hin-Tak Leung

This one I do without google translate, "high resolution" would be 高解像 . --- On Sat, 30/3/13, Jactry Zeng <jactry92(a)gmail.com> wrote: From: Jactry Zeng <jactry92(a)gmail.com> Subject: Re: [website] Simplified Chinese translation for release 1.5.27 To: "Qian Hong" <fracting(a)gmail.com> Cc: "Wine Devel" <wine-devel(a)winehq.org> Date: Saturday, 30 March, 2013, 10:23 2013/3/30 Qian Hong <fracting(a)gmail.com> > 2013/3/30 Jactry Zeng <jactry92(a)gmail.com>: > > + <li>一些 C 运行时的改进。</li> > > I think it is better to translate "C runtime" to “C 运行时库“ rather than > just ”C 运行时“。 > > + <li>为内建程序提供更高质量的图标。</li> > > Large icon means 大图标，not 高质量图标。You can verify this by the git commits。In fact, I have verified it before I commit this patch. I translated it as "高质量" meaning a picture have hight resolution. For a example, programs/wordpad/wordpad.ico, had a 48x48 resolution before, and now it is 256x256. > Thanks for the work. Thanks for your review. I will commit a newer patch. :-) -- Regards, Jactry Zeng -----Inline Attachment Follows-----

March 30, 2013

Re: Windows API on Linux

by Joris Huizer

On 03/29/2013 01:27 PM, Abhinav Jangda wrote: > Hello everyone, I'm working on a project which aims to develop a port > of Windows API on Linux, so that programs written using Windows API > could directly be compiled and executed on Linux with its native look > and feel. > Anyone, interested in working on this project. I think some Wine > developers will be as they would be having a good knowledge of Windows > API. Reminds me of Winelib Joris

March 30, 2013

Re: [website] Simplified Chinese translation for release 1.5.27

by Jactry Zeng

2013/3/30 Qian Hong <fracting(a)gmail.com> > 2013/3/30 Jactry Zeng <jactry92(a)gmail.com>: > > + <li>一些 C 运行时的改进。</li> > > I think it is better to translate "C runtime" to “C 运行时库“ rather than > just ”C 运行时“。 > > + <li>为内建程序提供更高质量的图标。</li> > > Large icon means 大图标，not 高质量图标。You can verify this by the git commits。 In fact, I have verified it before I commit this patch. I translated it as "高质量" meaning a picture have hight resolution. For a example, programs/wordpad/wordpad.ico, had a 48x48 resolution before, and now it is 256x256. > Thanks for the work. Thanks for your review. I will commit a newer patch. :-) -- Regards, Jactry Zeng

March 30, 2013

Re: [website] Simplified Chinese translation for release 1.5.27

by Hin-Tak Leung

I was not very happy with "大型 ..." for "large icon", so I expanded the meaning a bit and did 'large size icon'. I think it should be 大規格 or 大尺寸 or 大碼 . All of them are more precise about "size", whereas "大型" is less precise and more generic as in 'large format'/'large style'. So I would opt for "大碼圖標" . --- On Sat, 30/3/13, Hin-Tak Leung <htl10(a)users.sourceforge.net> wrote: > From: Hin-Tak Leung <htl10(a)users.sourceforge.net> > Subject: Re: [website] Simplified Chinese translation for release 1.5.27 > To: "Wine Devel" <wine-devel(a)winehq.org>, fracting(a)gmail.com, "Jactry Zeng" <jactry92(a)gmail.com> > Date: Saturday, 30 March, 2013, 10:02 > --- On Sat, 30/3/13, Qian Hong <fracting(a)gmail.com> > wrote: > > > Hi Jactry, > > > > 2013/3/30 Jactry Zeng <jactry92(a)gmail.com>: > > > + <li>一些 C > 运行时的改进。</li> > > > > I think it is better to translate "C runtime" to “C > > 运行时库“ rather than > > just ”C 运行时“。 > > I think both are terrible translations but could not think > of a better alternative off my head, so I went to consult > google translate. It defaults to 運行時庫 for "runtime > library" but allow me to choose a few other alternatives, > among which is > > "執行階段程式庫" > > Don't you think that's much better!? > > I think google translate is quite useful for technical terms > like these, as long as one is vigilant about not accepting > 'not quite correct' and go through the alternatives. One can > also help it a bit by giving a more verbose version of the > concept ('runtime library' instead of just 'runtime'), and > even occasionally some context (e.g. a full > sentence with '...loading in a runtime library...'). > > > + > > > <li>为内建程序提供更高质量的图标。</li> > > > > Large icon means 大图标，not 高质量图标。You > can > > verify this by the git commits。 > > 大型圖示 or 大型圖標 ? > > > Thanks for the work. > > > > -- > > Regards, > > Qian Hong > > > > - > > http://www.winehq.org > >

March 30, 2013

Re: [website] Simplified Chinese translation for release 1.5.27

by Hin-Tak Leung

--- On Sat, 30/3/13, Qian Hong <fracting(a)gmail.com> wrote: > Hi Jactry, > > 2013/3/30 Jactry Zeng <jactry92(a)gmail.com>: > > + <li>一些 C 运行时的改进。</li> > > I think it is better to translate "C runtime" to “C > 运行时库“ rather than > just ”C 运行时“。 I think both are terrible translations but could not think of a better alternative off my head, so I went to consult google translate. It defaults to 運行時庫 for "runtime library" but allow me to choose a few other alternatives, among which is "執行階段程式庫" Don't you think that's much better!? I think google translate is quite useful for technical terms like these, as long as one is vigilant about not accepting 'not quite correct' and go through the alternatives. One can also help it a bit by giving a more verbose version of the concept ('runtime library' instead of just 'runtime'), and even occasionally some context (e.g. a full sentence with '...loading in a runtime library...'). > + > <li>为内建程序提供更高质量的图标。</li> > > Large icon means 大图标，not 高质量图标。You can > verify this by the git commits。大型圖示 or 大型圖標 ? > Thanks for the work. > > -- > Regards, > Qian Hong > > - > http://www.winehq.org

March 30, 2013

Re: [website] Simplified Chinese translation for release 1.5.27

by Qian Hong

Hi Jactry, 2013/3/30 Jactry Zeng <jactry92(a)gmail.com>: > + <li>一些 C 运行时的改进。</li> I think it is better to translate "C runtime" to “C 运行时库“ rather than just ”C 运行时“。 + <li>为内建程序提供更高质量的图标。</li> Large icon means 大图标，not 高质量图标。You can verify this by the git commits。 Thanks for the work. -- Regards, Qian Hong - http://www.winehq.org

March 30, 2013

Re: secur32: Take schannel backend capabilities into account when configuring enabled protocols.

by Juan Lang

Hi Jacek, thanks for the detailed reply. On Fri, Mar 29, 2013 at 3:02 AM, Jacek Caban <jacek(a)codeweavers.com> wrote: > Each protocol has two kinds of enable/disable flags: "enabled" and > "disabled by default". Those have different default values for each > protocol and there are registry setting allowing to change each of them. > Only "enabled" protocols are used at all. This patch limits "enabled" > protocols to those that we can really support. If an application asks > schannel to use default set of protocols (which I'd expect them to do > unless they have a good reason), schannel will use all "enabled" protocols > that are not "disabled by default". An alternative to default set of > protocols is listing each allowed separately. > > This means that if protocol is "enabled" and "disabled by default" it > won't be used unless application explicitly asks for it. SSL2 is such a > protocol by default. Do you think we should do this differently? > Yes, my suggestion here is to explicitly disable SSL2 support altogether. GnuTLS doesn't support it, and having behavior that differs between Linux and Mac can be kind of maddening. I can imagine something like, "embedded browser doesn't work for game X", with lots of "works for me" reports and the occasional "fails here too", only to discover that it works on Mac but not Linux. The additional cost of a difference in behavior doesn't seem worth it, especially when the protocol itself really should have died long ago. --Juan

March 29, 2013

Re: [PATCH 1/3] jscript: Use helpers to access string buffers in jsregexp.c.

by Alexandre Julliard

Jacek Caban <jacek(a)codeweavers.com> writes: > --- > dlls/jscript/jsregexp.c | 114 > +++++++++++++++++++++++++++++++----------------- > 1 file changed, 73 insertions(+), 41 deletions(-) It breaks the tests: ../../../tools/runtest -q -P wine -M jscript.dll -T ../../.. -p jscript_test.exe.so run.c && touch run.ok run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 run.c:1804: Test failed: expected global_success_d run.c:1805: Test failed: expected global_success_i run.c:1807: Test failed: parse_script failed: 80004005 make: *** [run.ok] Error 18 -- Alexandre Julliard julliard(a)winehq.org

March 29, 2013

Re: d3dx9 [patch 1/2, try 4]: Implement D3DXSHEvalSphericalLight

by Alexandre Julliard

Nozomi Kodama <nozomi.kodama(a)yahoo.com> writes: > From bb40ba80a24a954d21c44cbe55b4b9c79e2087c5 Mon Sep 17 00:00:00 2001 > From: "nozomi.kodama" <nozomi.kodama(a)yahoo.com> > Date: Wed, 27 Mar 2013 22:38:51 -1000 > Subject: d3dx9: Implement D3DXSHEvalSphericalLight It still fails the same way... -- Alexandre Julliard julliard(a)winehq.org

March 29, 2013