Comments on: Join the openSUSE Proofreading Team

By: Curtis Ekstrom

Curtis Ekstrom — Sat, 23 Aug 2008 17:11:14 +0000

I’d also be willing to join. Just wondered if anyone knows how to get a pot file editor working under kde 4.1. Lokalize won’t install for me because of a dependency error (libqt4-backend-mysql or something like that) I saw that the files can be updated through the terminal with the svn co commands, so maybe an editor on the hardrive isn’t necessary?
Thanks,
frosch62

Also, how difficult would it be to develop a program which displays all possible text locations giving proofreaders the ability to see physically where the messages will appear (and therefore which proofreading/grammar rules apply). Maybe programmers could enter a simple number as a tag, coded to be the equivalent in such a program of the position of the text, resulting in less work for everyone.

By: Jon Robison

Jon Robison — Wed, 20 Aug 2008 12:19:37 +0000

Coitenly! I’ll help. And for those who don’t get the reference, that’s Curly from the Three Stooges.

By: John

John — Tue, 19 Aug 2008 20:43:13 +0000

I would love to help you edit your text into English.

By: Grrósz Dániel

Grrósz Dániel — Sun, 10 Aug 2008 01:32:24 +0000

Yes, unfortunately a completely different translation system would be needed that displays the strings where they belong and this cannot really be solved in the currently used translation systems. On the other hand many mistakes could be spotted by just looking through the menus and other visible texts of the translated application.

By: Mike

Mike — Fri, 08 Aug 2008 03:49:06 +0000

Grósz Dániel: Yes, that would be useful. Some of the pot files already supply a little bit of context in the comments, e.g. in x11.pot:

#. translators: this string is used in the context of fetching a configuration setting from the system
#: src/autoyast/dialog/autoDialog.ycp:108
#, fuzzy
msgid “Fetch from system”
msgstr “”

But it’s not consistently done. I don’t know how much of this depends upon upstream developers either. Perhaps it’s a best-practice suggestion that could be made to projects? I can’t think of a way for openSUSE to address it without detailed analysis of where each string is used.

By: Grósz Dániel

Grósz Dániel — Fri, 08 Aug 2008 01:27:07 +0000

What would also be useful for almost all software projects is not to just give the translators a word list that they translate without knowing the context but somehow translate messages knowing where they appear. Lots of stupid messages could be avoided (especially in languages with significantly different grammar from English).

By: Christian Boltz

Christian Boltz — Thu, 07 Aug 2008 19:45:56 +0000

Maybe, and I have to tell you that you did not find all errors ;-)

-> … before translator_s_ will start _their_ work.

By: Erlend

Erlend — Thu, 07 Aug 2008 16:38:27 +0000

> This team wants to check new software strings before translator will start _there_ work

Is this a qualification test? :-)