[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Common textes (was: Re: tr2i18n issue)
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2006-02-21 5:49:18
Message-ID: 200602210649.20067.nicolasg () snafu ! de
[Download RAW message or body]

On Monday 20 February 2006 15:06, Gregory Mokhin wrote:
> > The hacky way is to use a non-standard accelarator, e.g.: Ope&n
> >
> > (As for KDE4, thi is perhaps again a reason more not to have the "common
> > texts" in KDE anymore.)
>
> Are "common texts" gone already?

No, there are still there in KDE4.

trunk/KDE/kdelibs/common_texts.cpp

> I guess having such common texts
> would be useful, surely not for short and ambiguous words, but for
> very common sentences.

Here it starts to be the limit where it could be discussed if KDE should 
provide that feature or if it is the translating tool (i.e. KBabel) that 
should provide it.

>
> We had a discussion already about numerous versions of "can't open
> file", "error opening file" etc. These sentences are very common and
> are good candidates for inclusion into "common texts", because they
> can be translated "once and forever". This list would become also a
> kind of style guide for developers.

But there will always be variants of those, as sometimes it will be with a 
file name, sometimes without and sometimes with additional info (.e.g. 
KBabel's "No entry found!"

But may be we have a misunderstanding here. Common texts are only about 
translations, not about code itself. So it is not good for a generic 
"Cannot open file %1" that each application will use.

>
> Regards,
> Gregory

Have a nice day!

[prev in list] [next in list] [prev in thread] [next in thread]