to list as well!
---------- Forwarded message ----------
From: David Gerard <dgerard(a)gmail.com>
Date: 28 May 2010 21:07
Subject: Re: Call for translators
To: Paul Vriens <paul.vriens.wine(a)gmail.com>
2010/5/28 Paul Vriens <paul.vriens.wine(a)gmail.com>:
> I totally agree (and have already talked to Francois a few times about this)
> that we need a nicer/better way for translators to help us out.
Participate in TranslateWiki? http://translatewiki.net - started doing
translations for Wikimedia projects, now does them for other people
too.
- d.
Am 28.05.2010 21:24, schrieb Paul Vriens:
> On 05/28/2010 07:25 PM, André Hentschel wrote:
>> Am 28.05.2010 19:14, schrieb GOUJON Alexandre:
>>> Hi,
>>>
>>> There is a Win API Stats page available at
>>> http://www.winehq.org/winapi_stats.
>>> But as you can see, it's not updated since about a year.
>>>
>>> So here is my question : (as wine-1.2 is coming) Should we update the
>>> page or simply remove it ?
>>> I think a cleanup is preferable to avoid confusion but an updated table
>>> may interest some people.
>>>
>>> What do you think ?
>>>
>>>
>> +1 for update
>> It's obvious that a script does that, so someone should run it :)
>> Further i'd say that the data are facts, so it should not be too much
>> confusing.
>>
>
> There were some changes in July last year:
>
> http://www.winehq.org/pipermail/wine-devel/2009-July/077481.html
>
I sent some patches, that fixed it for me.
Library API count % implemented Total stubs Real stubs Pseudo stubs Forwards Year
Total 33512 66% 11301 9782 1519 10017 2009
Total 40241 69% 12169 12169 0 13623 2010
But now i see what was ment with "pseudo", my patches ignores the pseudo stubs...
--
Best Regards, André Hentschel
Hi,
There is a Win API Stats page available at
http://www.winehq.org/winapi_stats.
But as you can see, it's not updated since about a year.
So here is my question : (as wine-1.2 is coming) Should we update the
page or simply remove it ?
I think a cleanup is preferable to avoid confusion but an updated table
may interest some people.
What do you think ?
Hi,
No don't have time to bisect this also I'm no trained to do it I'm also
fed up being told it's so easy cos its not and why don't you have one
guy trained who can be contacted to do it for others? or show others how
to do it? I'm the maintainer for Rome total war latest report is the
install fails got to be a regression fix it worked on 1.44
Regards,
Keith
Someone, obviously another admin, has removed me as supermaintainer of the Microsoft Office installer entry.
I would like to know who, and why.
Yes, I am royally pissed off.
--
Rosanne DiMesio <dimesio(a)earthlink.net>
Nikolay Sivov <nsivov(a)codeweavers.com> wrote:
> + Wine должен работать на большинстве файловых системах.
This one sounds wrong, I'd change it to
Wine должен работать на большинстве файловых систем.
--
Dmitry.
Another month, another Winetricks.
Online as always at
http://kegel.com/wine/winetricks
or
http://winezeug.googlecode.com
(Bug reports to the issue tracker at the above URL, please.)
Changes:
Dan Kegel:
- Added mmdevapi=disabled verb
- Don't require ~/.winetrickscache to be owned by the user, to allow a
readonly cache owned by root.
- Sandbox: disable updating of wineprefix when wine version changes to
keep unix shell filesystem from being re-enabled.
- Mention that steam crashes if corefonts not installed
- Steam now defaults to embedded chrome instead of ie, so don't need
as many prereqs.
- Add alldlls=builtin, alldlls=default verbs
Eleazar Galano:
- Added utorrent verb (patch by eg)
Austin English:
- Update shockwave sha1sum
- Add 'forcemono' to aid in dotnet/mono debugging
- Update Mono to 2.6.4
Andrew Nguyen:
- Register the extracted wsh57 dll's.
I've been running with this set for... it's been so long, I can't
remember! What's preventing it from being committed? (I know it's not
the impending release, because otherwise the Patch list would say
they're "Deferred".)
Chip
Hi AJ,
I isolated and fixed the gcc bug, but it will take some time before the
changes make it into wine stable. Should I add a testcase to configure
to detect a broken version of gcc, and refuse to build wine64 if this is
the case?
See this link for the fix, and the testcase:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43869
gdiplus tests seem to pass now, no weird test failures any more. I put
my test results at:
http://test.winehq.org/data/033bb8a2f9bd57000e64d5566f1b52a1cdf3f730/index_…
I have no idea why it claims to have crashed, a few of them that claimed
to have crashed ran succesfully till the end, but apart from that a few
more testcases succeed. A few tests crash for me, but this appears to be
a side effect from running gcc-svn, since it happens with and without
the patch. I'm getting a lot of fixmes about
DW_CFA_remember_state/DW_CFA_restore_state not being implemented.
Cheers,
Maarten