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
