El dissabte, 3 de setembre de 2022, a les 10:44:01 (CEST), Johnny Jazeix va escriure: > Hi, > > this is great. For GCompris, we have some stuff to handle translation that > differs from the usual (for example, the po files are in > po/gcompris_<lang>.po, not po/<lang>/gcompris_qt.po). I'll take a look to > harmonise it with the usual. > For the stable branch, we don't plan to do a release before December so it > would be better to not apply it at Akademy (except if the change on > GCompris side is easily backportable but I have to check).
If you don't plan to do a release before December you have 3 months to make sure it works, i don't understand the problem. Albert > > Cheers, > > Johnny > > Le sam. 3 sept. 2022 à 09:47, Albert Astals Cid <aa...@kde.org> a écrit : > > El dissabte, 3 de setembre de 2022, a les 1:01:47 (CEST), Ömer Fadıl USTA > > va > > > > escriure: > > > Just wanted to learn one thing , isn't this will populate the logs with > > > lots of entries on git log history ? > > > I mean right now I am tracking git changes based on changes in history > > > > but > > > > > this will add a new entry > > > each night or I understand this wrong ? > > > > If you look a the example URL i posted you can see there's not a new entry > > each night. > > > > Cheers, > > > > Albert > > > > > Also wouldn't it be possible to fetch related translation on the fly > > > from > > > the software side after releases ? > > > I mean translation of language X might be getting a little back lets say > > > 5.26 released but team X > > > might be late to complete their translation on time but user should have > > > chance to download it > > > after the release of it (without waiting for the next tagging ). > > > Wouldn't > > > it be possible to download and install the latest > > > language data in applications just like users do with themes? > > > > > > Thank you > > > > > > Ömer Fadıl Usta > > > PGP key : 0xfd11561976b1690b > > > about.me/omerusta > > > > > > > > > Albert Astals Cid <aa...@kde.org>, 3 Eyl 2022 Cmt, 00:25 tarihinde şunu > > > > > > yazdı: > > > > As you may know, translations for apps don't live in the same place as > > > > the > > > > > > code for the apps themselves. > > > > > > > > This greatly benefits translators but is not awesome for the release > > > > management > > > > side of things since it means that for each release we need to not > > > > forget > > > > > > to > > > > copy the appropriate files to the appropriate place, makes tagging > > > > somewhat > > > > harder, etc. > > > > > > > > For a while now we have been running an "experimental" > > > > copy-po-qm-docbook- > > > > > > back-to-repository in a number of "select" repositories and it seems > > > > to > > > > have > > > > worked quite well, you can seem one example in > > > > https://invent.kde.org/plasma-mobile/alligator/-/commits/master/po > > > > > > > > The idea is to enable this for all repositories. > > > > > > > > This is a heads up, as a developer there's nothing you need to do, at > > > > most > > > > > > remove the po/ folder from .gitignore if for some reason it is there. > > > > > > > > If you're a packager you will need to make sure your scripts don't try > > > > to > > > > > > copy > > > > po/qm/docbook files anymore when doing a release once this is > > > > activated. > > > > > > My plan would be to enable this scripts over Akademy so we have the > > > > high > > > > > > bandwidth there to fix things if needed. > > > > > > > > Opinions? Comments? > > > > > > > > Cheers, > > > > > > > > Albert
