This is a multi-part message in MIME format.
--------------42lVrCYMRX5Gkz8vB7Rk0lmX
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Yaron Shahrabani skreiv 05.04.2024 22:15:
> Great, that makes a lot of sense, thank you!
> Now I have 2 other problems:
> 1. I don't know how to combine KF5 with KF6 in the same project.
As Łukasz Wojniłowicz mentioned, you can use the branch translation
feature in Lokalize. But a IMHO simpler solution is to instead switch to
using the PO Summit workflow:
https://techbase.kde.org/Localization/Workflows/PO_Summit
Then you will have only a single file to translate (for each
application/library), instead of one file for each branch (currently up
to four branches: trunk6, trunk5, stable6 and stable5). And you don’t
have to worry or care about a PO file being renamed in one branch, but
not the other (which breaks Lokalize’s branch sync feature), a PO file
being split into several PO files (in one branch but not the other), or
multiple PO files being merged into a single PO file (in one branch but
not the other). All this is automatically handled for you by some nice
people. :)
--
Karl Ove Hufthammer
--------------42lVrCYMRX5Gkz8vB7Rk0lmX
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
Yaron Shahrabani skreiv 05.04.2024
22:15:
Great,
that makes a lot of sense, thank you!
Now
I have 2 other problems:
1.
I don't know how to combine KF5 with KF6 in the same project.
As Łukasz Wojniłowicz mentioned, you can use the branch
translation feature in Lokalize. But a IMHO simpler solution is to
instead switch to using the PO Summit workflow:
https://techbase.kde.org/Localization/Workflows/PO_Summit
Then you will have only a single file to translate (for each
application/library), instead of one file for each branch
(currently up to four branches: trunk6, trunk5, stable6 and
stable5). And you don’t have to worry or care about a PO file
being renamed in one branch, but not the other (which breaks
Lokalize’s branch sync feature), a PO file being split into
several PO files (in one branch but not the other), or multiple PO
files being merged into a single PO file (in one branch but not
the other). All this is automatically handled for you by some nice
people. :)
--
Karl Ove Hufthammer
--------------42lVrCYMRX5Gkz8vB7Rk0lmX--