Re: [docs 2/2] winedev: Don't recommend a preprocessor check to comment out code

On Mon, Sep 2, 2013 at 10:34 PM, André Hentschel wrote: > --- > en/winedev-coding.sgml | 9 - > 1 file changed, 4 insertions(+), 5 deletions(-) There's a typo in -block of code. +block of code and it makes sure the code get's maintained. get's => gets -- Frédéric Delanoy

Re: [docs] wineusr: Assorted formatting & tagging fixes (try 2)

Frédéric Delanoy writes: > That's just replacing the Tabs by spaces in the affected lines. The > affected lines were using a mix of tabs and spaces > > It's indented two spaces from the parent listitem tag as it was before > (at least when tabs are displayed as 4 chars) > > Should I keep those t

Re: [docs] wineusr: Assorted formatting & tagging fixes (try 2)

On Fri, Aug 2, 2013 at 2:25 PM, Alexandre Julliard wrote: > Frédéric Delanoy writes: > >> @@ -710,17 +714,18 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\" >> choose between several edition modes: >> >> >> -

Re: [docs] wineusr: Assorted formatting & tagging fixes (try 2)

Frédéric Delanoy writes: > @@ -710,17 +714,18 @@ Path="c:\windows;c:\windows\system;e:\;e:\test;f:\" > choose between several edition modes: > > > - > - Emacs: the same keybind

Re: [docs] "sgml" is not a valid output format

On Tue, 23 Jul 2013, Frédéric Delanoy wrote: [...] > -ALLFORMATS = html pdf sgml ps txt > +ALLFORMATS = html pdf ps txt 'make sgml' can be used to generate the translated SGML source files for our many documentation translations. So I don't think this patch should be applied. -- Francois Gouge

Re: [docs] "sgml" is not a valid output format

On Tue, Jul 23, 2013 at 5:26 PM, Frédéric Delanoy wrote: > --- > Make.rules.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Make.rules.in b/Make.rules.in > index fda8e81..d326247 100644 > --- a/Make.rules.in > +++ b/Make.rules.in > @@ -100,7 +100,7 @@ dummy: > > # Man

Re: [docs] winelib: Use proper entity escaping for '&','<' and '>'

On Fri, Jul 19, 2013 at 5:50 PM, Julian Rüger wrote: > Hi Frédéric, > >> - $(CC) $(CC_OPTS) -DRC_INVOKED -E -x c $< | $(WRC) -N $(WRCFLAGS) >> $(WINELIB_FLAGS) -o $@ >> + $(CC) $(CC_OPTS) -DRC_INVOKED -E -x c $lt; | $(WRC) -N $(WRCFLAGS) >> $(WINELIB_FLAGS) -o $@ > > looks like you forgo

Re: [docs] winelib: Use proper entity escaping for '&','<' and '>'

Hi Frédéric, > - $(CC) $(CC_OPTS) -DRC_INVOKED -E -x c $< | $(WRC) -N $(WRCFLAGS) > $(WINELIB_FLAGS) -o $@ > + $(CC) $(CC_OPTS) -DRC_INVOKED -E -x c $lt; | $(WRC) -N $(WRCFLAGS) > $(WINELIB_FLAGS) -o $@ looks like you forgot the "&". Best, Julian

Re: [docs 2/3] winedev: Use hyphen in bitness

On Sun, Jul 14, 2013 at 7:41 PM, André Hentschel wrote: > --- > en/winedev-architecture.sgml | 56 > ++-- > en/winedev-debugger.sgml | 10 > en/winedev-kernel.sgml | 24 +-- > en/winedev-multimedia.sgml | 36 +++

Re: [docs] winedev: Update backtrace and relay examples

On 03.07.2013 00:02, Frédéric Delanoy wrote: > On Tue, Jul 2, 2013 at 11:39 PM, André Hentschel wrote: >> --- >> en/winedev-debugger.sgml | 269 >> ++- >> 1 file changed, 222 insertions(+), 47 deletions(-) >> >> diff --git a/en/winedev-debugger.sgml b/

Re: [docs] winedev: Update backtrace and relay examples

On Tue, Jul 2, 2013 at 11:39 PM, André Hentschel wrote: > --- > en/winedev-debugger.sgml | 269 > ++- > 1 file changed, 222 insertions(+), 47 deletions(-) > > diff --git a/en/winedev-debugger.sgml b/en/winedev-debugger.sgml > index b877063..31046c0 100

Re: [docs] winedev: Update gcov section (try 2)

Am 06.03.2012 06:13, schrieb Saulius Krasuckas: > * On Mon, 5 Mar 2012, André Hentschel wrote: >> >> en/winedev-otherdebug.sgml | 170 >> >> 1 files changed, 62 insertions(+), 108 deletions(-) > ... >> >> For a further in depth desc

Re: [docs] winedev: Update gcov section (try 2)

* On Mon, 5 Mar 2012, André Hentschel wrote: > > en/winedev-otherdebug.sgml | 170 > > 1 files changed, 62 insertions(+), 108 deletions(-) ... > > For a further in depth description of gcov, the official gcc > compiler sui

Re: [docs] winedev: Update gcov section

usr/share/docbook-utils/docbook-utils.dsl#html Working on: /home/julliard/wine/docs/en/winedev-guide.sgml openjade:/home/julliard/wine/docs/en/winedev-otherdebug.sgml:260:43:W: cannot generate system identifier for general entity "subkey" openjade:/home/julliard/wine/docs/en/winedev-otherd

Re: [docs] winedev: Update code columns limit (resend)

On 07/23/2011 07:05 PM, James McKenzie wrote: On 7/23/11 3:33 PM, Andrew Eikum wrote: On 07/23/2011 05:02 PM, Francois Gouget wrote: On Mon, 4 Jul 2011, André Hentschel wrote: [...] -Code is usually limited to 80 columns. This helps prevent -mailers mangling patches by line wra

Re: [docs] winedev: Update code columns limit (resend)

André Hentschel wrote: > Am 24.07.2011 00:02, schrieb Francois Gouget: >> On Mon, 4 Jul 2011, André Hentschel wrote: >> [...] >>> - Code is usually limited to 80 columns. This helps prevent >>> - mailers mangling patches by line wrap. Also it generally >>> + Code is usually limite

Re: [docs] winedev: Update code columns limit (resend)

Am 24.07.2011 00:02, schrieb Francois Gouget: > On Mon, 4 Jul 2011, André Hentschel wrote: > [...] >> -Code is usually limited to 80 columns. This helps prevent >> -mailers mangling patches by line wrap. Also it generally >> +Code is usually limited to 100 columns. It genera

Re: [docs] winedev: Update code columns limit (resend)

On 7/23/11 3:33 PM, Andrew Eikum wrote: On 07/23/2011 05:02 PM, Francois Gouget wrote: On Mon, 4 Jul 2011, André Hentschel wrote: [...] -Code is usually limited to 80 columns. This helps prevent -mailers mangling patches by line wrap. Also it generally +Code is usually l

Re: [docs] winedev: Update code columns limit (resend)

I believe Julliard already mentioned the column limit was bumped up (I believe it was actually 120?). 1024 resolution isn't exactly "typical" anymore, even for laptops - most developers I know actually have more than one screen nowadays. As for terminal emulators, they may default at 80 but that ca

Re: [docs] winedev: Update code columns limit (resend)

On 07/23/2011 05:02 PM, Francois Gouget wrote: On Mon, 4 Jul 2011, André Hentschel wrote: [...] - Code is usually limited to 80 columns. This helps prevent - mailers mangling patches by line wrap. Also it generally + Code is usually limited to 100 columns. It genera

Re: [docs] winedev: Update code columns limit (resend)

On Mon, 4 Jul 2011, André Hentschel wrote: [...] > - Code is usually limited to 80 columns. This helps prevent > - mailers mangling patches by line wrap. Also it generally > + Code is usually limited to 100 columns. It generally I'd prefer to keep the 80 columns recommandat

Re: [docs] winedev: A hint for patch separation

Am 27.06.2011 11:55, schrieb Jerome Leclanche: > That sounds like we want people to avoid testing wine. How about > "Patches must not break building Wine nor its testsuite. Adding dead > code should also be avoided."? Yes, sounds better. -- Best Regards, André Hentschel

Re: [docs] winedev: A hint for patch separation

That sounds like we want people to avoid testing wine. How about "Patches must not break building Wine nor its testsuite. Adding dead code should also be avoided."? J. Leclanche 2011/6/26 André Hentschel : > --- >  en/winedev-coding.sgml |    4 >  1 files changed, 4 insertions(+), 0 dele

Re: [12/13]docs/wineusr: unix paths are supported

Austin English writes: >> diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml >> index f36383f..106be37 100644 >> --- a/en/wineusr-running.sgml >> +++ b/en/wineusr-running.sgml >> @@ -90,8 +90,8 @@ Usage: wine PROGRAM [ARGUMENTS...]   Run the specified >> program >>         in the Pat

Re: [12/13]docs/wineusr: unix paths are supported

2010/5/4 André Hentschel : > --- >  en/wineusr-running.sgml |    8 ++-- >  1 files changed, 6 insertions(+), 2 deletions(-) > > diff --git a/en/wineusr-running.sgml b/en/wineusr-running.sgml > index f36383f..106be37 100644 > --- a/en/wineusr-running.sgml > +++ b/en/wineusr-running.sgml > @@ -90

Re: On bugs and docs

Tom Spear wrote: > On 3/20/07, James Hawkins <[EMAIL PROTECTED]> wrote: >> On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: >> >> What's wrong with the components (besides the possible lack of >> components for some dlls) and the search page? > > Well just that some of them are not very clear, win

Re: On bugs and docs

On 3/20/07, James Hawkins <[EMAIL PROTECTED]> wrote: On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: You shouldn't be searching all bugs when filing a new bug...the reason to search for bugs (in the case of a new bug report) is to make sure you're not making a duplicate report. A new bug can't

Re: On bugs and docs

On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: On 3/20/07, James Hawkins <[EMAIL PROTECTED]> wrote: > On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: > > What's wrong with the components (besides the possible lack of > components for some dlls) and the search page? Well just that some of them

Re: On bugs and docs

On 3/20/07, Louis Lenders <[EMAIL PROTECTED]> wrote: James Hawkins gmail.com> writes: > > However, the components could use a major revamping and should be > > fairly trivial. However I think that one component for each dll might > > be a bit much.. Maybe narrow the dll's down to categories

Re: On bugs and docs

James Hawkins gmail.com> writes: > > However, the components could use a major revamping and should be > > fairly trivial. However I think that one component for each dll might > > be a bit much.. Maybe narrow the dll's down to categories such as > > wine-common-controls, and wine-riched.. > >

Re: On bugs and docs

On Tue, Mar 20, 2007 at 01:32:30PM -0500, Tom Spear wrote: > On 3/20/07, James Hawkins <[EMAIL PROTECTED]> wrote: > I just think that mozilla (since we cant/wont) should give 2 search > pages with google-like functionality, 1 search box, you type what you > want to find, and hit search and it searc

Re: On bugs and docs

On 3/20/07, James Hawkins <[EMAIL PROTECTED]> wrote: On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: What's wrong with the components (besides the possible lack of components for some dlls) and the search page? Well just that some of them are not very clear, wine-binary for one. What would be

Re: On bugs and docs

On 3/20/07, Tom Spear <[EMAIL PROTECTED]> wrote: On 3/20/07, Jan Zerebecki <[EMAIL PROTECTED]> wrote: > Yea it would be good to collect information on winehq.org and not > scatter it all over the web. I think there are all the (web)tools > on winehq.org one needs for that, or is anyone missing so

Re: On bugs and docs

On 3/20/07, Jan Zerebecki <[EMAIL PROTECTED]> wrote: Yea it would be good to collect information on winehq.org and not scatter it all over the web. I think there are all the (web)tools on winehq.org one needs for that, or is anyone missing something? (Other than that the bugzilla could really use

Re: On bugs and docs

On 3/20/07, Jan Zerebecki <[EMAIL PROTECTED]> wrote: On Mon, Mar 19, 2007 at 11:04:58AM -0500, Tom Spear wrote: > Is it just me or has anyone else noticed that the documentation for > wine is kind of scattered all over the place? I mean personally I can > name about 8 different places (that are

Re: On bugs and docs

On Mon, Mar 19, 2007 at 11:04:58AM -0500, Tom Spear wrote: > Is it just me or has anyone else noticed that the documentation for > wine is kind of scattered all over the place? I mean personally I can > name about 8 different places (that are affiliated with winehq) that > people can go to get inf

re: On bugs and docs

Tom wrote: Basically my idea was to make several tasklists to link to 1434 (bugs like dinput9, d3d8, etc), and then link individual games to each of those, so that someone working on games, and in specific on dinput9 for example could easily find bugs related to dinput 9 without having to do a qu

Re: On bugs and docs

Tom Spear wrote: > Hi all, just some quick questions. > > Also, is it against the rules in bugzilla to try to organize the bugs > some way? IOW The very old games metabug that I created (bug 1434).. Bad idea. Metabugs are hard to follow and hard to use. Especially if _every game in the whole wide

On bugs and docs

Hi all, just some quick questions. Is it just me or has anyone else noticed that the documentation for wine is kind of scattered all over the place? I mean personally I can name about 8 different places (that are affiliated with winehq) that people can go to get information, not including the ma

Re: docs

f registry > > keys and values. Bonus points for explaining what they do. It's not > > terribly difficult to generate, but I was getting sleepy as I got to > > that section. > > > > I just started a list on the wiki. When it's complete enough (anyone is > mo

Re: [DOCS] winedlloverrides

- Original Message - From: "Jonathan Ernst" <[EMAIL PROTECTED]> > For more informations about DLL overrides, please refer to section 3.1.2.1 of this guide. This 3.1.2.1 is likely to change, can we have a symbolic reference instead? -- Dimi Paun <[EMAIL PROTECTED]> Lattica, Inc.

Re: docs

> terribly difficult to generate, but I was getting sleepy as I got to > that section. > I just started a list on the wiki. When it's complete enough (anyone is more than welcome to add things in it) we can put it in the docs. http://wiki.winehq.org/UsefulRegistryKeys -- Jonathan Erns

Re: docs

On 10/14/05, Brian Vincent <[EMAIL PROTECTED]> wrote: > I don't want to step on any toes, but I plan on redoing the User Guide > this weekend. Mostly it'll just be an extension of the existing stuff > I wrote and bringing it up to date. I figure I can probably bang it > out in a few hours. Just

docs

I don't want to step on any toes, but I plan on redoing the User Guide this weekend. Mostly it'll just be an extension of the existing stuff I wrote and bringing it up to date. I figure I can probably bang it out in a few hours. Is anyone else close to having docs completed? -Brian

Re: [DOCS, POLICY] Documenting stuff that doesn't work right?

Holly Bostick <[EMAIL PROTECTED]> writes: > Well I *thought* I had-- I renamed my current .wine directory (I have > several previous renamed .wine directories in my ~/ folder; the names > all start with .wine, though, such as .wine.borked, .wine.borkedmaybe, > .wine.old and the like. I try to pres

Re: [DOCS, POLICY] Documenting stuff that doesn't work right?

Alexandre Julliard schreef: > Holly Bostick <[EMAIL PROTECTED]> writes: > > >> I was installing Icewind Dale, and like all games and >> Wine-installed programs, I meant to install to the partition I have >> set aside for that purpose, which is mounted to /usr/local/games, >> with a symlink in my

Re: [DOCS, POLICY] Documenting stuff that doesn't work right?

e so, but is > this appropriate to document? Or is it likely to be fixed before the > updated docs go 'live'? I only ask because I can't think of a way to > write this up atm without explicitly exposing a flaw in Wine, and Wine > doesn't really deserve that--

Re: [DOCS, POLICY] Documenting stuff that doesn't work right?

On Wed, 2005-09-21 at 22:01 +0200, Holly Bostick wrote: > Obviously I know how to get around this, having just done so, but is > this appropriate to document? I have no idea why you encountered that sort of behavior, but it doesn't seem right. Unless Alexandre tells us this is the way it should wo

[DOCS, POLICY] Documenting stuff that doesn't work right?

Hey, So I just blew away my previous install of Wine and reinstalled from yesterday's CVS, and went to install a program, so I could take notes on the most current user experience for the docs. I immediately realized that I hadn't run winecfg to set my drives, so I went to do that--

Re: docs/. configure.ac

On Thu, 2005-05-26 at 13:38 +0200, Francois Gouget wrote: > Hmm, you forgot to regenerate the configure script. My bad, fixed. Thanks. -- Dimi Paun <[EMAIL PROTECTED]> Lattica, Inc.

Re: docs/. configure.ac

h 1.2 1.3 +12 -0 docs/configure.ac Hmm, you forgot to regenerate the configure script. The problem is my autoconf version is a bit different which results in extra changes. So I prefer not to send my configure diff and let you regenerate it... -- Francois Gouget

Docs at SourceForge

Hi folks, As most of you already noticed, the SGML docs have moved over to the CVS SourceForge: http://sourceforge.net/cvs/?group_id=6241 They clearly did not belong in the tree, and we decided at WineConf05 to move them out of there. So we did. I have renamed the files for a more

Re: Do we need one of those on our docs?

Hi, On Mon, Nov 08, 2004 at 10:10:46AM +0200, Shachar Shemesh wrote: > From the samba developer's guide, http://us1.samba.org/samba/devel/ > > >*Important:* In order to avoid any potential licensing issues we > >also ask that anyone who has signed the Microsoft CIFS Royalty > >Free Ag

Do we need one of those on our docs?

From the samba developer's guide, http://us1.samba.org/samba/devel/ *Important:* In order to avoid any potential licensing issues we also ask that anyone who has signed the Microsoft CIFS Royalty Free Agreement

Re: SEH docs

Mike Hearn wrote: + No, it isn't. It's not handled in Wine because pthread_attr_setstacksize (for pthread case) or wine_anon_mmap (for kthread case) is used to allocate the stack and the rest is handled by the guest OS (AFAIK). Regards, Filip

Re: Remove winesetuptk and wineinstall from docs

> I thought wineinstall handled loading the wine.inf? I think wineprefixcreate does that now. Ivan. Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

Re: Remove winesetuptk and wineinstall from docs

Hi, --- Vincent Béron <[EMAIL PROTECTED]> wrote: > Winesetuptk hasn't been updated for a while (new drive scheme, etc.), > and it's not even listed on our sf.net download page anymore (where > it > was last seen). > tools/wineinstall doesn't do more than what wineprefixcreate does for > configurat

Re: Docs

On January 1, 2004 12:20 pm, Ivan Leo Murray-Smith wrote: > in getting.sgml, I've recently changed a few things in it, but there isn't > a cvs.sgml file, should this warning go? Yes, it should, cvs.sgml is no longer. But there may be things on WineHQ that may need updating instead. -- Dimi.

Docs

Hi list, I've noticed this in getting.sgml, I've recently changed a few things in it, but there isn't a cvs.sgml file, should this warning go? Ivan.

Re: building wine docs

On November 21, 2003 12:16 pm, Ivan Leo Murray-Smith wrote: > make doc generates one big file, but this isn't what I want. Do not pass the -u flag to the db2xxx tools. -- Dimi.

Re: building wine docs

Le ven 21/11/2003 à 12:16, Ivan Leo Murray-Smith a écrit : > Hi list, > how can I build the wine docs in different little files (index.html, > wine-stats.html and so on, like the docs for download on the web site) instead > of one big file? > make doc generates one big file, but th

building wine docs

Hi list, how can I build the wine docs in different little files (index.html, wine-stats.html and so on, like the docs for download on the web site) instead of one big file? make doc generates one big file, but this isn't what I want. Ivan.

Re: docs: wine-devel [11/16]

On Mon, 22 Sep 2003, Marcelo Duarte wrote: [...] > In this list, some times I see acronyms that I do not understand, some I try > to imagine. For the majority of the people who had not been born speaking > English this also must be complicated. Don't worry. Most off-line english-speaking people ha

Re: docs: wine-devel [11/16]

Marcelo Duarte wrote: - Original Message - From: "Eric Pouech" <[EMAIL PROTECTED]> To: "Dimitrie O. Paun" <[EMAIL PROTECTED]> Dimitrie O. Paun wrote: Eric, a lot of stuff in here looks like it's in need of some TLC, if you can take a look... TLC ? tender & loving care

Re: docs: wine-devel [11/16]

- Original Message - From: "Eric Pouech" <[EMAIL PROTECTED]> To: "Dimitrie O. Paun" <[EMAIL PROTECTED]> > Dimitrie O. Paun wrote: > > Eric, a lot of stuff in here looks like it's in > > need of some TLC, if you can take a look... > TLC ? tender & loving care > is that what you're look

Re: docs: wine-devel [11/16]

On September 21, 2003 02:44 pm, Eric Pouech wrote: > is that what you're looking for ? (even if everything is not filled in yet) Yes, thanks! Now it's up to Alexandre to merge everything in, and then I'll review it again to see where we stand. -- Dimi.

docs: wine-devel [0/16]

ing a lot of documentation may give us a warm and fuzzy feeling, but in fact it just shows how we have failed to make Wine transparent, and/or we haven't refined the docs. Nobody likes to read documentation, so let's keep it short, sweet, and interesting. Second, we have to avoid at al

Re: docs: faq build

On Thu, 18 Sep 2003, Alexandre Julliard wrote: > I'm not sure I agree with that. If we make the documentation available > for download then we should have the FAQ there too, we shouldn't > require people to go to WineHQ to get it. I don't know, it maybe just me, for I never expect to see FAQs wi

Re: docs: faq build

"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes: > The fact that the FAQ is now SGML does not warant > building it in all sorts of formats, and including > it in the docs tarball. Just because we can, does > not mean we should. > > In fact, theoretically we should