A few questions about UI strings

[Andreas Pakulat]

On 12.04.09 22:38:31, Frederik Schwarzer wrote:
> On Sunday 12 April 2009 02:03:52 Andreas Pakulat wrote:
> > On 11.04.09 18:57:05, Frederik Schwarzer wrote:
> > > ====
> > > kdevelop/languages/cpp/veritas/uutcontextaction.cpp
> > > "Generate Unit Under Test"
> > > 
> > > Another candidate for some context
> > 
> > Hmm, why? Though, again I'd say only the first word needs translation.
> > The rest is a standard term within the area of unit-testing :) Should we
> > change such things to
> > i18n("Generate")+" Unit Under Test", or rather use
> 
> No. For German it is common to leave such terms but there are countries
> that are more ... proud of their language or languages with different
> writings (e.g. Japanese uses Hiragana and Katakana signs to transcribe english
> words. And even in German there might be a proper german term in the future, like
> "Entwurfsmuster" for "Design Pattern".
> Every user-visible string has to be translatable, even if it seems reasonable to
> not translate it.

:( Thats one of the reasons I don't use the german translation for
kdevelop since 5 years. Its completely non-understandable for somebody
who knows its way around these things as they try to translate each and
everything. I can however accept (as I have no way to prove something
different) that this is specific to german and in other languages this
is far more common and people working in the specific field actually do
use language-specific terms for these things. 

However, I think some of these texts cannot be reasonably translated by
somebody who has no idea about developing. For example I can't think of
a good context for the above right now as (without repeating the
sentence) it seems really obvious what is meant there.
 
> > > ====
> > > Could "Trolltech" be replaced by "Nokia" or is it ok to be as is?
> > 
> > Are you talking about copyrights? If so, then the answer is: I don't
> > know, please ask a KDE lawyer - or somebody more familiar with
> > copyrights. We did copy some code from Qt, but AFAIK that was all way
> > before Nokia took over and changed the company name. So I'm not sure
> > what the right thing is.
> 
> Yes, I mean in the about dialog info. No idea either, was just curious.

Ah, that should be changed indeed... done.

> > Ok, here's what it does, additionally to "Break blocks" (which inserts
> > newlines between unrelated blocks, for example between two class
> > declarations), "Break Blocks All" adds newlines also around closing
> > headers, i.e. around the "catch" for a try/catch, or the "else" for an
> > if/else.
> > 
> > So yes, "Break all blocks" is better, I think this comes from the
> > original astyle api/manpage which lists "--break-blocks=all".
> 
> I leave that to you, since it is more than a typo. :)

Changed the text. But didn't know how to add context to a .ui file, how
is this done?

> Thank you for all the explanations, also to the other responders. It helped a lot
> in understanding these strings. There will be more questions in the future. :)

Keep em coming :)

-- 
You two ought to be more careful--your love could drag on for years and years.