Re: mlang.dll implementation fix
Hi. Here is the patch attached to mail. I will prepare tests soon. Best Regards Bartosz 2013/6/19 Christian Costa : > Hi and welcome, > > Patches should be sent included in the mail. Adding tests is recommended. > You can follow status at http://source.winehq.org/patches/. But currently > we're in code freeze so you may have to wait Wine 1.6. > > Christian > > > > 2013/6/19 Bartosz >> >> My name is Bartosz and I would like to start hacking wine. >> At beginning I implemented BreakLine methods (available in mlang.dll): >> http://msdn.microsoft.com/en-us/library/aa741037%28v=vs.85%29.aspx >> >> I prepared patch which is available at: >> http://bugs.winehq.org/attachment.cgi?id=44854&action=diff >> http://bugs.winehq.org/show_bug.cgi?id=32126 >> >> Could you please take a look at these methods and push it into git repo? >> >> Should I write tests for that? >> >> Thanks in advance >> Bartosz >> >> > mlang_fix.patch Description: Binary data
Re: [website] Added Portuguese translation for call for translators
On Wed, Jun 19, 2013 at 5:22 PM, Frédéric Delanoy < frederic.dela...@gmail.com> wrote: > Just wondering: does it make sense to translate a call for translators? > I mean, if a volunteer can't understand the English from the call, > (s)he wouldn't be able to translate correctly anyway. I though about that, but ended up deciding that it should be translated for coherence as everything in the page is in portuguese too. Luckily I resisted the urge to translate the wiki page :)
Re: [website] Added Portuguese translation for call for translators
2013/6/19 Lucas Zawacki : > From: Lucas Zawacki > > --- > news/pt/2013061601.xml |9 + > 1 file changed, 9 insertions(+) > create mode 100644 news/pt/2013061601.xml > > diff --git a/news/pt/2013061601.xml b/news/pt/2013061601.xml > new file mode 100644 > index 000..86bf5a8 > --- /dev/null > +++ b/news/pt/2013061601.xml > @@ -0,0 +1,9 @@ > + > +16 de Junho de 2013 > +Procura-se tradutores! > + Just wondering: does it make sense to translate a call for translators? I mean, if a volunteer can't understand the English from the call, (s)he wouldn't be able to translate correctly anyway. Frédéric
Re: [Wine] German translation - netstat.exe
On Tuesday, 18 Jun 2013 at 19:35:02 André Hentschel wrote: > when you scroll down a bit on that page, you see everything needed to get rid > of false positives. Ah, I didn't scrolled down sooo deep. :( > Oh and fgouget is Fran?ois Gouget Thanks for this hint. I will deal with it in the right manner. -- Kindly regards Joerg Schiermeier Bielefeld/Germany
Re: gdi32: Get the default character index, not its value.
Akihiro Sagawa writes: > --- > dlls/gdi32/freetype.c |2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) It doesn't work here: ../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so font.c && touch font.ok font.c:1356: Test failed: GetGlyphIndicesW should have returned a 0080 not -- Alexandre Julliard julli...@winehq.org
Re: po: Update Italian translation (try 3)
2013/6/17 Fabian Ebner : > Typo fixed (finally) > --- > po/it.po | 40 ++-- > 1 file changed, 14 insertions(+), 26 deletions(-) > This one looks good to me, thanks :)
Re: mlang.dll implementation fix
Hi and welcome, Patches should be sent included in the mail. Adding tests is recommended. You can follow status at http://source.winehq.org/patches/. But currently we're in code freeze so you may have to wait Wine 1.6. Christian 2013/6/19 Bartosz > My name is Bartosz and I would like to start hacking wine. > At beginning I implemented BreakLine methods (available in mlang.dll): > http://msdn.microsoft.com/en-us/library/aa741037%28v=vs.85%29.aspx > > I prepared patch which is available at: > http://bugs.winehq.org/attachment.cgi?id=44854&action=diff > http://bugs.winehq.org/show_bug.cgi?id=32126 > > Could you please take a look at these methods and push it into git repo? > > Should I write tests for that? > > Thanks in advance > Bartosz > > >
Re: oledb32: Add more database tests
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 http://testbot.winehq.org/JobDetails.pl?Key=26031 Your paranoid android. === WXPX64 (64 bit database) === database.c:166: Test failed: got L"Provider=SQLOLEDB.1;Data Source=dummy" === WVISTAX64 (64 bit database) === database.c:166: Test failed: got L"Provider=SQLOLEDB.1;Data Source=dummy" === W7PROX64 (64 bit database) === database.c:166: Test failed: got L"Provider=SQLOLEDB.1;Data Source=dummy" === TEST64_W7SP1 (64 bit database) === database.c:166: Test failed: got L"Provider=SQLOLEDB.1;Data Source=dummy"
