wine-devel June 2009

wine-devel@winehq.org

145 participants
318 discussions

Re: italian translations for winecfg
by Nikolay Sivov 24 Jun '09

24 Jun '09

Davide Pizzetti wrote: > Here are the italian translations for winecfg. > 1. Use 'git diff' format to produce patches 2. Use plain text attachments. Feel free to ask here any related questions.

1 0

Re:
by Austin English 24 Jun '09

24 Jun '09

2009/6/24 Pavel Procházka <pavelvonlostice(a)seznam.cz>: Howdy Pavel, A few minor things: A) Please use a descriptive subject, and put your message in the e-mail body. It's easier for those that don't read every patch but only care about certain areas to skim the mailing list that way. Also, it's hard to search the archives when there's no subject on the e-mail. B) +/*MULTIBUFFERING PART*/ It's not a huge deal, but please add spaces around comments, they're hard to read that way. C) @@ -2716,5 +2909,5 @@ START_TEST(visual) return ; cleanup: - releaseObjects(); + releaseObjects(); } Now sure why that was changed...did you accidentally change the encoding or something? -- -Austin

2 1

Re: Re: wine compatible logo needed
by M. Stefanov 24 Jun '09

24 Jun '09

You're right. I'll use the full version. And an electronic manual wouldn't be practical in my case. Which is: begin "We need this." repeat "Is this what you need?"; "No, modify"; Mod_soft; until Response = "OK, this is it."; write(manual); burn(CD); install_all; end. So basically it's the end of the development cycle for that specifical program. That's why I think to specify the particular version of wine and linux distro that I'm certain it works with and throw in a note that experiences with other wine versions / linux distros / different OS may be different (with other words of course). And when/if the time comes for a v 2.0 of my soft, I'll test that against the latest wine that exists at the time of 2.0 release, and if it works, do the same with the 2.0 manual. Basically I was asking if there was a pre-existing template for such a case - a finished program which works out-of-the-box under wine at the time of the soft finalization...

2 1

free software replacement for MFC?
by karl＠gnu.org 24 Jun '09

24 Jun '09

In the course of reviewing some possible projects for GNU, Richard Stallman asked me if there was any active work going on to write a free software replacement for MFC. >From the MFC pages I found on the Wine web site (http://www.winehq.org/docs/winelib-guide/mfc), which talk about ways of working with the Microsoft classes and don't mention any alternatives, I gather this isn't a current goal of Wine itself. But still, I figured that this would be the most likely place for any such project would be known about, or even find possible developers if one was to be started. Looking on the web, all I found was the old ofc.sf.net, which appears not to have gotten very far and to have been abandoned years ago, judging from the source repository. The other projects I came across, such as wxWidgets and SmartC++, appear not to try to be a compatible replacement for MFC, but rather a functional alternative. If anyone here has corrections, additions, suggestions related to those, I'd be grateful for any replies. Thanks, karl(a)gnu.org

3 2

Re: [put the subject here]
by Dmitry Timoshkov 24 Jun '09

24 Jun '09

"Pavel Procházka" <pavelvonlostice(a)seznam.cz> wrote: > Subject:[2/3] wined3d: IWineGDISwapChainImpl_Present relevant to windows implementation > Making multibuffering working well when flip - sequence is W RGB, R GBW, G BWR, B WRG, W RGB. When W = WHITE, R = > RED, G = GREEN, B = BLUE. It is doing well for any count of backbuffers - for 1 too. Please try to make the patch subject short and clear. All additional comments put in the patch body. > - back = (IWineD3DSurfaceImpl *) This->backBuffer[0]; > + back = *((IWineD3DSurfaceImpl *)This->backBuffer[0]); /*this value can not be pointer*/ Any reason for the above change and comment? > + /*moving data from backbuffers to left - no pointers!*/ > + for(i=0;i<This->presentParms.BackBufferCount-1;i++) Some spaces wouldn't hurt, and would better match the code you are changing. -- Dmitry.

1 0

Re: avifil32: Romanian translation
by Michael Stefaniuc 24 Jun '09

24 Jun '09

Paul, Paul Chitescu wrote: > Changelog: > avifil32: Romanian translation it looks like you are missing the #pragma code_page(65001) around the translation. bye michael

1 0

Re: programs/taskmanager: Fixed missing Dutch translations
by Paul Vriens 24 Jun '09

24 Jun '09

Frans Kool wrote: > > > ------------------------------------------------------------------------ > > Beat you to it ;) http://www.winehq.org/pipermail/wine-patches/2009-June/074719.html -- Cheers, Paul.

1 0

Re: [1/3][resend] wined3d: Allowing infinity count of backbuffers
by paulo lesgaz 24 Jun '09

24 Jun '09

--- En date de : Mer 24.6.09, Henri Verbeet <hverbeet(a)gmail.com> a écrit : De: Henri Verbeet <hverbeet(a)gmail.com> Objet: Re: [1/3][resend] wined3d: Allowing infinity count of backbuffers À: wine-devel(a)winehq.org Date: Mercredi 24 Juin 2009, 11h13 2009/6/24 Pavel Procházka <pavelvonlostice(a)seznam.cz>: > Please set a proper subject on your mails. I think this has been asked before. You can't just remove the check without making it work first, the patch has to make sense on its own. I don't get what you mean. Do you suggest that Pavel merges the two first patches in one single, with a title like "Allows multibuffering in ddraw" ? David

2 1

Re: [1/3][resend] wined3d: Allowing infinity count of backbuffers
by Henri Verbeet 24 Jun '09

24 Jun '09

2009/6/24 Pavel Procházka <pavelvonlostice(a)seznam.cz>: > Please set a proper subject on your mails. I think this has been asked before. You can't just remove the check without making it work first, the patch has to make sense on its own.

1 0

Developers-Hints wiki page: Character encoding in resource file translations
by Frédéric Delanoy 24 Jun '09

24 Jun '09

Hi all, According to http://wiki.winehq.org/Developers-Hints on the "http://wiki.winehq.org/Developers-Hints", AFAICT the resource files should generally - use the default Windows codepage for the specified language or - use UTF-8 surround with "#pragma code_page(65001)" at the top of the file and "#pragma code_page(default)" at the bottom Which of the encoding is preferred? UTF-8 ? Furthermore, - the "65001" should probably be replaced by "utf8" (I checked in tools/wrc/parser.l:373) [ which would be better IMNSHO in new/updated resource file] - the link to the list of codepages is broken; it should be http://msdn.microsoft.com/en-us/library/dd317756(VS.85).aspx Frédéric

4 3

← Newer
1
...
7
8
9
10
11
12
13
...
32
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel June 2009