On 06/25/2010 11:44 AM, Dmitry Timoshkov wrote:
Paul Vrienspaul.vriens.wine@gmail.com wrote:
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?
What's wrong with running a test application with those menus/dialogs under Wine? What's the reason to complicate things by separating tasks of translating and verifying the result of the translation?
Well, nothing is wrong with that I guess. It's however geared to people who are coders, not?
Of course not, that's proven by the amount of new translations we see these days from new people, who apparently are not coders.
Yes, but that also sometimes requires volunteers to do the actual work (editing the resource files and creating patches) for them. I mean, I did a lot of work for Danish and Michael is doing the same for Romanian. It would be much nicer if that can be automated in some way.
What we see is that there are several people who want to help us with the translation part but have no idea how to code (or are actually willing to code). We could use them, especially for the more exotic (or let's call it less mainstream) languages.
Since when the editing of .rc files started to require coding skills?
Fine, let's call it editing an up to date file and creating a patch out of that.