<div class="gmail_quote">On Fri, Jun 25, 2010 at 11:14, Paul Vriens <span dir="ltr"><<a href="mailto:paul.vriens.wine@gmail.com">paul.vriens.wine@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 06/25/2010 11:04 AM, Dmitry Timoshkov wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
Francois Gouget<<a href="mailto:fgouget@free.fr" target="_blank">fgouget@free.fr</a>> wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
We will still need people to take on the somwhat unsexy control resizing<div class="im"><br>
task and that may be a problem. If it turns out we lack volunteers for<br>
that we may turn to some automatic layout scheme, for instance describe<br>
the resources in a glade-like language and translate+convert them to rc<br>
files at build time.<br>
</div></blockquote><div class="im">
<br>
Sounds not very exciting. If there is a choice of having resources with properly<br>
placed and sized controls but english only, vs. translated but with broken layout<br>
ones, then I'm afraid most users would prefer an english variant.<br>
</div></blockquote>
<br>
Once we start using po files we can probably get rid of the 'transl' website as those stats will come from whatever tool we choose to deal with po files.<br>
<br>
For the actual resources and their size/placements it would be nice to have a tool/website as well that could be used to show how the translated language actually looks in a menu/dialog/whatever with even the possibility to change things. Is that feasible?<br>
</blockquote></div><br>Why reinventing the wheel? Such a tool already exists (ResHacker or similar).<br>What we should do to attract more people is to provide a more "user-friendly" web page/ translator page explaining in greater detail:<br>
- how to find what has to be translated (translation statistics, .rc files, ...)<br>- how to edit a file (#pragma code_page, encoding, menu accelerators, ...)<br>- how to check/adapt actual results with ResHacker, since you have to either adapt the text to fit in, or the dialogs size)<br>
- how to create a patch OR send it to e.g. <a href="mailto:translation@winehq.org">translation@winehq.org</a> for inclusion<br><br>I may help in doing this.<br><br>Furthermore, on the main web page, "Development - Become a Wine developer" can be intimidating for some potential translators (most non-developers potential translators would not consider themselves... well... developers!).<br>
Maybe something like "Contribute - How you can help" (or similar) would be less repulsive.<br><br>Frédéric<br>