[website try2] Simplified Chinese translation for release 1.5.27

[Jactry Zeng]

From 72f3d5b7021472bf4a2aa6cc2c973319bbc786d4 Mon Sep 17 00:00:00 2001
From: Jactry Zeng 
Date: Sun, 31 Mar 2013 10:39:28 +0800
Subject: Simplified Chinese translation for release 1.5.27
To: wine-patches 
Reply-To: wine-devel 

---
 news/zh-cn/2013032901.xml | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 news/zh-cn/2013032901.xml

diff --git a/news/zh-cn/2013032901.xml b/news/zh-cn/2013032901.xml
new file mode 100644
index 000..2e4e31b
--- /dev/null
+++ b/news/zh-cn/2013032901.xml
@@ -0,0 +1,15 @@
+
+三月 29, 2013
+Wine 1.5.27 发布
+
+ Wine 开发版 1.5.27 现在可以使用了。
+ 本次更新：
+
+  Mac 后端驱动对系统托盘的支持。
+  一些 C runtime 的改进。
+  为内建程序提供更高分辨率的图标。
+  各种 bug 修复。
+
+源代码可以从http://prdownloads.sourceforge.net/wine/wine-1.5.27.tar.bz2";>这里获取。
+二进制包正在构建中，稍后将出现在各自相应的下载位置。
+
-- 
1.8.1.3

Fresh WineWiki Theme, Straight from the Farm

[Kyle Auble]

So as usual, my estimate of how long it would take was way off, but
I'm finally done adapting the WineHQ theme to Moinmoin.

It's not perfect, but I feel it's ready to submit for switching over.
I've tested it in Firefox, Chromium, Midori, and Opera (briefly in
IE8 & IE9 too). I did do everything through Moinmoin's stand-alone
server, but while I know there always seem to be ghosts in the
machine, I'm guessing that Apache shouldn't interfere with layout
issues.

I mostly followed the WineHQ & current WineWiki theme for large
things, just tweaking the CSS to make it fit what Moinmoin spits out.
I did make more design choices of my own on the smaller stuff though.
After wrestling with Moinmoin's theme system, I was surprised how
many things are still hard-coded (at least as of v1.5).

For example, Moinmoin wraps some things in divs without providing a
CSS class for the div, just the child element. The fortune cookie on
the RecentChanges page & the edit page are two cases of that. The
dummy content in the search bar is another tricky one. It's set in
the javascript for the search bar (don't remember where it was in the
source tree) so I left that one alone.

One other tricky issue was handling overflows & RTL support. They
both seem to work ok in isolation, but go crazy when you mix them. I
haven't checked RTL in IE, but if you force an RTL page to overflow
in Webkit, it positions things based on what's actually in the window
(so the sidebar winds up floating in the middle of the page). Firefox
simply doesn't try to apply any of the overflow rules in RTL (which I
guess is nice in a Hippocratic sense). Opera alone handled things
exactly like I hoped.

As for the tables, I think they should display ok now, although I
don't know if everyone wants my exact values for paddings & such. The
old theme had some table-based layout that may have had conflicting
CSS rules, but I've div-vied everything up so the only table tags now
should be when Moinmoin itself chooses them over a div and well...
tables.

I've pushed all of the changes to my Bitbucket repo at:
https://bitbucket.org/kauble/wine-wiki-migration
The "refined" branch is the one you want although I expect that once
the code is hosted at WineHQ's git repo, it would become the new
master branch. At that point, I can just reset my repo to point to
the WineHQ one as the origin.

- Kyle

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

[Juan Lang]

Hi Jacek,

On Sat, Mar 30, 2013 at 8:36 AM, Jacek Caban  wrote:

>  Most of the argument could be used against enabling TLS 1.1 and TLS 1.2,
> because it's not present on older Macs (nor enabled by default on Windows),
> so we'll have different behaviour. That's sadly something we have to live
> with. Anyway, I'm all for trying to avoid using SSL2, but I'd like to be a
> bit less extreme. How about this patch:
>
> http://source.winehq.org/patches/data/95298
>
> With this patch, SSL2 will be completely disabled in default Wine config,
> but it will be still possible to enable by registries, if someone really
> needs it.
>

Thanks, this approach looks good to me.
--Juan

Re: Windows API on Linux

[Vincent Povirk]

Mono on non-Windows platforms ships with a static library called
io-layer that implements a small subset of the Windows API for
compatibility reasons, without any server processes or a registry. It
does not (normally) attempt to do any path translation, so I think
that's as close as possible to what you want to achieve for those
low-level api's.

Of course, there's a limit to the level of compatibility (even if
you're only looking for source compatibility) you can achieve without
the sort of architecture Wine has to simulate services that are
available on a real Windows system. Combine this with the fact that
the Windows API just isn't very nice to program against, and it leads
to little interest in a project like this.

But maybe it would be possible for one person to pull this off for a
large enough win32 subset to run a GUI application, using the code
already available in Mono and Wine.

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

[Jacek Caban]

Hi Juan,

On 03/29/13 18:19, Juan Lang wrote:
> Hi Jacek,
>
> thanks for the detailed reply.
>
> On Fri, Mar 29, 2013 at 3:02 AM, Jacek Caban  > 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.

Most of the argument could be used against enabling TLS 1.1 and TLS 1.2,
because it's not present on older Macs (nor enabled by default on
Windows), so we'll have different behaviour. That's sadly something we
have to live with. Anyway, I'm all for trying to avoid using SSL2, but
I'd like to be a bit less extreme. How about this patch:

http://source.winehq.org/patches/data/95298

With this patch, SSL2 will be completely disabled in default Wine
config, but it will be still possible to enable by registries, if
someone really needs it.


Jacek

Re: [website] Simplified Chinese translation for release 1.5.27

[Hin-Tak Leung]

--- On Sat, 30/3/13, Jactry Zeng  wrote:

From: Jactry Zeng 
Subject: Re: [website] Simplified Chinese translation for release 1.5.27
To: ht...@users.sourceforge.net
Cc: "Wine Devel" , "Qian Hong" 
Date: Saturday, 30 March, 2013, 10:41


2013/3/30 Hin-Tak Leung 
>
>
> 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 
>
> I translated it as "高质量" meaning a picture have hight resolution. 
Here has a typo, hight -> higher  -- 
Regards,
Jactry Zeng

Re: [website] Simplified Chinese translation for release 1.5.27

[Hin-Tak Leung]

This one I do without google translate, "high resolution" would be
高解像
.

--- On Sat, 30/3/13, Jactry Zeng  wrote:

From: Jactry Zeng 
Subject: Re: [website] Simplified Chinese translation for release 1.5.27
To: "Qian Hong" 
Cc: "Wine Devel" 
Date: Saturday, 30 March, 2013, 10:23

2013/3/30 Qian Hong 
> 2013/3/30 Jactry Zeng :



> > + 一些 C 运行时的改进。
>
> I think it is better to translate "C runtime" to “C 运行时库“ rather than
> just ”C 运行时“。
>
> + 为内建程序提供更高质量的图标。



>
> 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-

Re: Windows API on Linux

[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

Re: [website] Simplified Chinese translation for release 1.5.27

[Jactry Zeng]

2013/3/30 Hin-Tak Leung 
>
>
> 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 �\行�r�� for "runtime library" but allow me to choose a few other
alternatives, among which is
>
> "�绦须A段程式��"
>
> 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.


2013/3/30 Jactry Zeng 
>
> I translated it as "高质量" meaning a picture have hight resolution.
Here has a typo, hight -> higher 
-- 
Regards,
Jactry Zeng

Re: [website] Simplified Chinese translation for release 1.5.27

[Jactry Zeng]

2013/3/30 Qian Hong 
> 2013/3/30 Jactry Zeng :
> > + 一些 C 运行时的改进。
>
> I think it is better to translate "C runtime" to “C 运行时库“ rather than
> just ”C 运行时“。
>
> + 为内建程序提供更高质量的图标。
>
> 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

Re: [website] Simplified Chinese translation for release 1.5.27

[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  wrote:

> From: Hin-Tak Leung 
> Subject: Re: [website] Simplified Chinese translation for release 1.5.27
> To: "Wine Devel" , fract...@gmail.com, "Jactry Zeng" 
> 
> Date: Saturday, 30 March, 2013, 10:02
> --- On Sat, 30/3/13, Qian Hong 
> wrote:
> 
> > Hi Jactry,
> > 
> > 2013/3/30 Jactry Zeng :
> > > + 一些 C
> 运行时的改进。
> > 
> > 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...').  
> 
> > +
> >
> 为内建程序提供更高质量的图标。
> > 
> > Large icon means 大图标，not 高质量图标。You
> can
> > verify this by the git commits。
> 
> 大型圖示 or 大型圖標 ?
> 
> > Thanks for the work.
> > 
> > --
> > Regards,
> > Qian Hong
> > 
> > -
> > http://www.winehq.org
> 
> 

Re: [website] Simplified Chinese translation for release 1.5.27

[Hin-Tak Leung]

--- On Sat, 30/3/13, Qian Hong  wrote:

> Hi Jactry,
> 
> 2013/3/30 Jactry Zeng :
> > + 一些 C 运行时的改进。
> 
> 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...').  

> +
> 为内建程序提供更高质量的图标。
> 
> Large icon means 大图标，not 高质量图标。You can
> verify this by the git commits。

大型圖示 or 大型圖標 ?

> Thanks for the work.
> 
> --
> Regards,
> Qian Hong
> 
> -
> http://www.winehq.org

Re: [website] Simplified Chinese translation for release 1.5.27

[Qian Hong]

Hi Jactry,

2013/3/30 Jactry Zeng :
> + 一些 C 运行时的改进。

I think it is better to translate "C runtime" to “C 运行时库“ rather than
just ”C 运行时“。

+ 为内建程序提供更高质量的图标。

Large icon means 大图标，not 高质量图标。You can verify this by the git commits。

Thanks for the work.

--
Regards,
Qian Hong

-
http://www.winehq.org