Addition of En resources to non-En resources

Francois Gouget fgouget at
Thu Jun 24 07:55:31 CDT 2010

On Wed, 23 Jun 2010, Dmitry Timoshkov wrote:

> Francois Gouget <fgouget at> wrote:
> > James never meant that Wine would not use rc files at all. What he meant 
> > is that rc files would lose their status as the autoritative source for 
> > the resource strings and would be mostly generated from po files.
> The .rc files are much more than just strings, in any case the translator
> need to edit/check the .rc files to get an acceptable result.

Which is something that translators have not all been doing because 
verifying that the dialog looks ok is such a pain. Currently translators 
need two have two completely distinct skillsets:
 * An English to the target language translator skill.
 * An rc file editing, testing and resizing skill.

Requiring that translators master both skills severly limits the pool of 
translators we can draw from. Introducing po files lets us treat each 
task independently and leverage all the online po translation tools.

We will still need people to take on the somwhat unsexy control resizing 
task and that may be a problem. If it turns out we lack volunteers for 
that we may turn to some automatic layout scheme, for instance describe 
the resources in a glade-like language and translate+convert them to rc 
files at build time.

> I was replying to a comment saying basically "me too" which the sender 
> tends to reply to almost every message.

The sender is excited by the prospect of rc files being used for 
translating Wine resources and that's pretty understandable. I am too!

Francois Gouget <fgouget at>    
  Good judgment comes from experience, and experience comes from bad judgment
                               -- Barry LePatner

More information about the wine-devel mailing list