WineConf todo list
vberon at mecano.gme.usherb.ca
Fri May 6 20:53:54 CDT 2005
Le ven 06/05/2005 à 21:23, Francois Gouget a écrit :
> I'm trying to gather a list of stuff we said needed to be done at
> WineConf. Of course the initial list is going to be horribly incomplete
> but I'm sure others will contribute the missing pieces.
> * Add a list of companies providing Wine services and support
> This discussion/flameware is in full swing.
Spelling fix: flamewar
> * Moving the Wine doc to SourceForge
> The documentation, i.e. the SGML files in documentation/, uses
> completely different tools from the rest of Wine. Also Alexandre does
> not want to deal with its translations. So move the SGML documentation
> to its own CVS repository, winedoc, which we could host on SourceForge.
> The English version would go in the en subdirectory so we can easily add
I guess the compiled docs hosted on winehq would include the
translations as well?
If they're not part of the source tarball anymore, when will the docs on
winehq will be updated? After each commit to winedoc? At the same time
of Wine releases?
> * Check in the French translation and corresponding infrastructure. The
> translation will go in the fr subdirectory of the winedoc CVS
> repository. At the same time the infrastructure for adding other
> translations should be put in place.
> * Find a way to document the registry
> I had a discussion with Alexandre and lamented that, now that we're
> going to move things out of the configuration, we won't be able to put
> comments describing what each setting does. However we already have the
> problem with all of the Windows settings. Furthermore he noted that it's
> hard to find where a given setting is used in the Wine code (because the
> registry path is encoded as a Unicode string?). And the problem is
> compounded by the lack of proper documentation for registry settings in
> So the idea is to create a way to document each registry setting in
> the source code so it can be extracted with a tool similar to c2man.pl
> (or with a hacked c2man.pl).
How about having a "Explanation" or "Comment" key along with the
effective key? wine.inf could fill those in on the first run... If users
remove the comment, they're in the same boat as with the config.
Of course, that's orthogonal to having proper documentation in comments
in the code using such a key.
Note that a method for correctly grepping Wine's unicode strings would
be invaluable, not only for registry entries.
More information about the wine-devel