-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mikael Relbe wrote: > On Jun 4, 10:24 am, anatoly techtonik <[email protected]> wrote: >> I wonder if it makes sense for proper attribution to separate people >> who provide translations from those who sent patches to Trac code, >> because making such patch requires significantly more efforts in >> learning Trac code and toolchain than translations. It is not like >> somebody will feel discouraged because of that, but this will give >> them more points in their resumes. >> -- >> anatoly t. > > I am not sure about this, but translation is a different task than > writing code, indeed. > > I have spent numerous of hours translating Trac to Swedish, and I even > did not start from scratch then since a lot of work had been done by > others. The hard work was in finding appropriate expressions, and > creating consistency in the language. Have a look at the Swedish terms > page _1 just to get an idea. I have had to study the code quite a lot > to be able to understand the context in finding the appropriate > translation. > > _1: http://trac.edgewall.org/wiki/TracTermsSv > > I think the experience from translating Trac could be very beneficial > when producing code...
I'd tell you the same for my experience from German translation. Never saw parts of the whole code structure I suddenly had to study to understand, what was going on there when pushing a message out. Explaining code to a developer is different from explaining it to a user, but this is what translations are about. BTW: should better read 'transcription' instead of 'translation', because good l10n work doesn't bring the word but the sense to the local user, effectively bringing the translator to another level of understanding as well. You could see it, if you study the latest changesets for Trac, where several findings from translations triggered changes in the code. Sure, the translator of one msgid as well as the coder of one single line of whitespace/typo patch might/will exist, but is dealt with by other means, like cboos outlined before. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwJXYcACgkQ31DJeiZFuHc3TwCgwXPjK4L4+QJHCZJZTpUAFYI8 mQMAn3fbT7Bd1XgEoqTlC3Qzy3C1V9Zj =zXBo -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
