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

List:       kde-release-team
Subject:    Re: Report of packaging issues with mega release - Qt5/6 translation conflicts
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2024-01-25 21:18:47
Message-ID: 2414560.bqSAcqniv6 () xps15
[Download RAW message or body]

El dissabte, 20 de gener de 2024, a les 17:39:15 (CET), Fabian Vogt va 
escriure:
> Hi,
> 
> Am Freitag, 8. Dezember 2023, 12:56:09 CET schrieb Jonathan Riddell:
> > On Fri, 8 Dec 2023 at 10:53, Antonio Rojas <arojas@archlinux.org> wrote:
> > > > - phonon: Qt5/6 versions collide (translations)
> > > > 
> > > > For Phonon and similar cases the translations are shared, why not just
> > > 
> > > package the translations with one of them which you know to be
> > > installed?
> 
> Is this actually valid? 

I ran lrelease from Qt5 and Qt6 over the same phonon libphonon_qt.po and they 
generated exactly bit by bit the same file.

Is that not your experience?

> I don't expect that Qt 5 will always be able to read
> QM files produced for Qt 6. The other way around is probably not guaranteed
> either.

Whether there's a promise or not that this will forever be the same, can't 
say.

Cheers,
  Albert

> 
> IMO the translations need to contain the Qt version in their path name,
> either filename or somewhere in the installation path.
> 
> This is also an issue for e.g. kimageannotator:
> https://invent.kde.org/graphics/gwenview/-/merge_requests/245#note_851730
> 
> Cheers,
> Fabian
> 
> > > > Jonathan
> > > 
> > > Because none of them is guaranteed to be installed. Only the one that is
> > > pulled as a dependency of something will
> > 
> > Can you put them in a common package that both libraries depend on?
> > 
> > Having two translations for the same repo with the same strings would
> > likely cause more effort for translators.
> > 
> > Jonathan




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