Re: [Discussion] Pootle Migration - Git Connection
Hi all, To be honest, I think we don't have the (wo)man power to maintain translations for two branches. It would be better to concentrate on AOO42X and to export translations to the source on a regular base. E.g. we now have a complete Ukrainian UI on Pootle, but I cannot build a test version, because the translation is not in our code. Regards, Matthias Am 13.06.22 um 06:40 schrieb Peter Kovacs: > > Am 11.06.22 um 14:54 schrieb Arrigo Marchiori: > >>> We could then think of a Version Mapping and a back push translation >>> system. >>> This is just a crazy Idea at this moment, to manage the string changes >>> between Versions. >> What do you mean exactly? >> >> I would expect l10n-savy developers to push changes from the Pootle >> development repository into AOO41X or other branches, at appropriate >> times (for example, before a beta release). > > I use 41x and 42x as an example. The amount of Strings used in 41x and > 42x are different. The PO files do not match. > > And we will have that also in future. The way we are developing > currently that we have one productive release and we build one > development release, leads to the point that we might have 2 releases. > > I would like to try to have an auto backport script the creates from > the development branch PO files PO files of the older version. > > That is is the Idea at least > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: [Discussion] Pootle Migration - Git Connection
Am 11.06.22 um 14:54 schrieb Arrigo Marchiori: We could then think of a Version Mapping and a back push translation system. This is just a crazy Idea at this moment, to manage the string changes between Versions. What do you mean exactly? I would expect l10n-savy developers to push changes from the Pootle development repository into AOO41X or other branches, at appropriate times (for example, before a beta release). I use 41x and 42x as an example. The amount of Strings used in 41x and 42x are different. The PO files do not match. And we will have that also in future. The way we are developing currently that we have one productive release and we build one development release, leads to the point that we might have 2 releases. I would like to try to have an auto backport script the creates from the development branch PO files PO files of the older version. That is is the Idea at least - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hello at all, the process which is already implemented is: I wrote a shell script which export every night (2 am CET) the data from the database to have recent po files. Then I copy them into my home folder at the "pootle" server, where I commit it into a git repo. Then I can get the po files to my own system to generate the sdf files. this step was required as log as I had to use ubuntu 18.04. There is no problem to give more persons access to the group of my home folder. Kind regards Mechtilde Am 11.06.22 um 14:54 schrieb Arrigo Marchiori: Hello All, On Sun, May 29, 2022 at 11:41:09PM +0200, Peter Kovacs wrote: Hello all, I am still working myself into Pootle. Pootle stores the translation at default on the filesystem. There is a backend which can utilize git. Pootle commit changes on the translation towards the git repository. It would give us maybe the opportunity to maintain different Iteration of OpenOffice Translation texts. Storing any development effort into a version control system is IMHO a good idea. I think that the best way to do it, would be the easiest, technically speaking. For example: if you want to configure Pootle to use Git, you will have to let it authenticate in some ways. If it's easy, then go ahead! The alternative would be having someone manually pushing changes from the filesystem into the repository. This could be done on a periodic basis; say every two weeks. To summarize: +1 for Git, in whatever way it is easiest to configure and to maintain. For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. I agree that branches would be most useful. We could then think of a Version Mapping and a back push translation system. This is just a crazy Idea at this moment, to manage the string changes between Versions. What do you mean exactly? I would expect l10n-savy developers to push changes from the Pootle development repository into AOO41X or other branches, at appropriate times (for example, before a beta release). What do you think? Is this an Idea to look into? Please write me your opinion. Thanks. I hope this helps. Best regards, -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hello All, On Sun, May 29, 2022 at 11:41:09PM +0200, Peter Kovacs wrote: > Hello all, > > I am still working myself into Pootle. > > Pootle stores the translation at default on the filesystem. There is a > backend which can utilize git. Pootle commit changes on the translation > towards the git repository. > > It would give us maybe the opportunity to maintain different Iteration of > OpenOffice Translation texts. Storing any development effort into a version control system is IMHO a good idea. I think that the best way to do it, would be the easiest, technically speaking. For example: if you want to configure Pootle to use Git, you will have to let it authenticate in some ways. If it's easy, then go ahead! The alternative would be having someone manually pushing changes from the filesystem into the repository. This could be done on a periodic basis; say every two weeks. To summarize: +1 for Git, in whatever way it is easiest to configure and to maintain. > For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could > use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation > files. I agree that branches would be most useful. > We could then think of a Version Mapping and a back push translation system. > This is just a crazy Idea at this moment, to manage the string changes > between Versions. What do you mean exactly? I would expect l10n-savy developers to push changes from the Pootle development repository into AOO41X or other branches, at appropriate times (for example, before a beta release). > What do you think? Is this an Idea to look into? Please write me your > opinion. Thanks. I hope this helps. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hi Mechtilde, Can you please commit the Ukrainian SDF to trunk? I will take care of it then... Regards, Matthias Am 05.06.22 um 08:31 schrieb Mechtilde: > Hello Matthias, > > I exported the strings for uk. > > Can you send me a screenshot of the settings I have to use in filezilla. > > Then I can upload it into my home directory. > > Kind regards > > Mechtilde > > Am 04.06.22 um 13:46 schrieb Matthias Seidel: >> Hi Mechtilde, >> >> Short question: >> >> Are we able to export languages at the moment? >> >> UKR ui is at 95% now and I would like to build a localized Windows >> build. >> >> Regards, >> >> Matthias >> >> Am 04.06.22 um 08:07 schrieb Mechtilde: >>> Hello Bidouille, >>> >>> Am 30.05.22 um 08:44 schrieb Bidouille: Hello Peter, > For example. 4.1.x and 4.2.x Translation sets do not match. Maybe > we could use Git to have a 4.2.x branch,another branch will contain > 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. >>> >>> End-user should use the web frontend. in this thread we discuss how >>> the backend works /should work. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> > smime.p7s Description: S/MIME Cryptographic Signature
Re: [Discussion] Pootle Migration - Git Connection
Hello Matthias, I exported the strings for uk. Can you send me a screenshot of the settings I have to use in filezilla. Then I can upload it into my home directory. Kind regards Mechtilde Am 04.06.22 um 13:46 schrieb Matthias Seidel: Hi Mechtilde, Short question: Are we able to export languages at the moment? UKR ui is at 95% now and I would like to build a localized Windows build. Regards, Matthias Am 04.06.22 um 08:07 schrieb Mechtilde: Hello Bidouille, Am 30.05.22 um 08:44 schrieb Bidouille: Hello Peter, For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. End-user should use the web frontend. in this thread we discuss how the backend works /should work. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hi Mechtilde, Short question: Are we able to export languages at the moment? UKR ui is at 95% now and I would like to build a localized Windows build. Regards, Matthias Am 04.06.22 um 08:07 schrieb Mechtilde: > Hello Bidouille, > > Am 30.05.22 um 08:44 schrieb Bidouille: >> Hello Peter, >> >>> For example. 4.1.x and 4.2.x Translation sets do not match. Maybe >>> we could use Git to have a 4.2.x branch,another branch will contain >>> 4.1.x Translation files. >> >> Git is not a dedicated tool for translation strings >> If I understood, we will have .po files and should use a specific >> software to make this. After work done, pushing PRs to contribute. >> IMO, this is not easy for end-users who help to contribute. > > End-user should use the web frontend. in this thread we discuss how > the backend works /should work. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > smime.p7s Description: S/MIME Cryptographic Signature
Re: [Discussion] Pootle Migration - Git Connection
There would be no change for the Web user experience. The Idea is that Pootle uses git to mark changes Users do, without knowing them. I spoke with Mechtilde some time ago, and currently we do this through scripts that run frequently. Am 30.05.22 um 08:44 schrieb Bidouille: Hello Peter, For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hello Bidouille, Am 30.05.22 um 08:44 schrieb Bidouille: Hello Peter, For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. End-user should use the web frontend. in this thread we discuss how the backend works /should work. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Pootle Migration - Git Connection
Hello Peter, > For example. 4.1.x and 4.2.x Translation sets do not match. Maybe > we could use Git to have a 4.2.x branch,another branch will contain > 4.1.x Translation files. Git is not a dedicated tool for translation strings If I understood, we will have .po files and should use a specific software to make this. After work done, pushing PRs to contribute. IMO, this is not easy for end-users who help to contribute. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Discussion] Pootle Migration - Git Connection
Forgot the Discussion flag. :( Am 29.05.22 um 23:41 schrieb Peter Kovacs: Hello all, I am still working myself into Pootle. Pootle stores the translation at default on the filesystem. There is a backend which can utilize git. Pootle commit changes on the translation towards the git repository. It would give us maybe the opportunity to maintain different Iteration of OpenOffice Translation texts. For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation files. We could then think of a Version Mapping and a back push translation system. This is just a crazy Idea at this moment, to manage the string changes between Versions. What do you think? Is this an Idea to look into? Please write me your opinion. Thanks. All the best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
