Rinse de Vries wrote:
> 
> Hi,
> A Dutch magazine has sent me this newsmessage about a new translation
> tool of Troll Tech:
> 
> http://linuxpr.com/releases/2765.html
> 
> My question: How much different is this new application compared to
> KBabel?
> Is it indeed a milestone in translation tools or does KBabel  work the
> same way?
> 
Well, what's different between the KDE way and the Qt way
of translating, is, that Qt does _always_ uses a scope in form
of the class name. A usual Qt "pot file" would look like this:

#: kmoon.cpp:123
msgid "MoonWidget::About Moon Phase Indicator"
msgstr ""

#: kmoon.cpp:231
msgid "MoonWidget::First Quarter"
msgstr ""

#: kmoon.cpp:242
msgid "MoonWidget::Full Moon"
msgstr ""

As in KDE you would loose the scope in translating, so the
msgstr would look similiar. 

I haven't seen the app so far as I couldn't get it installed,
but judging from the sources it tries hard to give you as
much context as possible.

    "<p> When translating an item, you have the following information
close at"
    " hand:<ul>\n"
    " <li> the source text;\n"
    " <li> the comment for the source text;\n"
    " <li> the context in which the source text appears, possibly with
an"
    " explanation of where to find the context in the Qt application or
other"
    " comment;\n"
    " <li> relevant phrases from phrase books, with translations and"
    " definitions.\n"
    "</ul> Phrase books provide instant information about technical
terms, and"
    " can be edited using <b>Qt Linguist</b>.  There is also a
<i>finished</i>"
    " flag that you may turn on when you are satisfied with a
translation, in"
    " which case the translation is used instead of the source text
when"
    " running the Qt application with the QM file.</p>\n\n"   

But I don't see how is this more than what kbabel does.

Greetings, Stephan

-- 
Frauen und Maenner passen vielleicht nicht zusammen, aber meine 
allerschoensten Schrammen habe ich mir bei diesem Duell geholt.
					       -- Reinhard Mey