On Tue, 7 Apr 2009, Vincent Povirk wrote:
[...]
> I don't think a dependency on po/gettext and the resulting two
> translation systems instead of one is a good idea. I think it is best
> to use the existing rc system to translate all text.
The problem is there is no translation tool that knows how
+1
A box model is really the way to go here. This is how the real
toolkits do it; you don't translate the entire layout, just the text.
The toolkit generates a suitable layout at runtime based on the text
sizes. That makes it much easier to edit dialogs.
We are stuck with the inferior Windows dia
2009/4/6 Warren Dumortier :
> Yeah, why not.
>
> But that was not really hard at all, if you use a calculator to
> calculate x and y coords. I could easily change winecfg for my patch.
> IMO it is not really needed as winecfg doesn't change a lot...
The issue is not so much that winecfg changes a
Hi,
This is something I have been thinking about for a while and is
triggered by a comment by Austin on the "How can we improve WINE"
thread that is floating around.
In short, this is aiming to discuss and seek a resolution to issues
encountered when editing resource files -- in particular dialog
