--0016364eec7e4501a604a1cd498c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tom, with all the due respect, "improve" should mean the Qt version does the job= , but you have a more specific target to meet, which is alien to Qt. I'm not aware of Qt localization having defined Russian "off target", so I'd say an upstream bug is an upstream bug. That's unless Qt says they have no interes= t for localization... B=C3=A8rto On 26 April 2011 10:12, Tom Albers wrote: > ----- Original Message ----- > > On Monday, April 25, 2011 22:12:55 Alexander Potashev wrote: > > > What do you think about inclusion of KUndo*2 into kdelibs? > > > > we really don't want more duplication of code and effort between Qt > > and > > kdelibs, and we certainly don't want forks of Qt code in kdelibs. > > Forks? It does sound like to me as we take the base class from Qt and > improve it for usage within KDE. We've done that for years and years. Doe= s > this now imply that that's bad practice and kdelibs is closed for such > classes? > > Best, > -- > Tom Albers > KDE Sysadmin > --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D If Pac-Man had affected us as kids, we'd all be running around in a darkene= d room munching pills and listening to repetitive music. --0016364eec7e4501a604a1cd498c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tom,

with all the due respect, "improve" should mean the Q= t version does the job, but you have a more specific target to meet, which = is alien to Qt. I'm not aware of Qt localization having defined Russian= "off target", so I'd say an upstream bug is an upstream bug.= That's unless Qt says they have no interest for localization...

B=C3=A8rto

On 26 April 20= 11 10:12, Tom Albers <= toma@kde.org> wrote:
----- Original Message -----
> On Monday, April 25, 2011 22:12:55 Alexander Potashev wrote:
> > What do you think about inclusion of KUndo*2 into kdelibs?
>
> we really don't want more duplication of code and effort between Q= t
> and
> kdelibs, and we certainly don't want forks of Qt code in kdelibs.<= br>
Forks? It does sound like to me as we take the base class from Qt and= improve it for usage within KDE. We've done that for years and years. = Does this now imply that that's bad practice and kdelibs is closed for = such classes?

Best,
--
Tom Albers
KDE Sysadmin



--
=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
If Pac-Man had affected us as kids, we'd all= be running around in a darkened room munching pills and listening to repet= itive music.
--0016364eec7e4501a604a1cd498c--