forum openoffice
hi i'm trying to register for the forum openoffice but i have a gmail address... i read that i have to send an email in order to register.. my username is GMM1984 password Gretha1984! and ofcourse my email address: gm.mei...@gmail.com kind regards Gretha le Comte-Meijer
Re: Opengrok index upate issue
Hi Matthias, I updated now all git repos on the machine and added some config exclusion. i hope this leads to an indexing of trunk. I check wednesday after work. all the best peter Am 12.08.24 um 22:52 schrieb Matthias Seidel: Hi Peter, Am 12.08.24 um 22:48 schrieb Peter Kovacs: Hi Matthias, Am 12.08.24 um 22:43 schrieb Matthias Seidel: Hi Peter, Am 12.08.24 um 22:35 schrieb Peter Kovacs: Hi all, could not find the thread. so I have updated the index manually. Thanks! can someone check if the status of git is fine and check if the index is now updating regulary? The Index should update some time after something is committed on GitHub. i see. thanks for the hint. I check, but just in case i forget, help me, please. It looks like the Index is up to date, but the Git revision is not. Things I already fixed in trunk are still visible. can you check the AOO2xx branch, i updated that manually. AOO42X seems to be up to date! Maybe the connection to GitHub is the main problem? i guess there is an issue with ownership on the machine. i check tomorrow. Thanks! Regards, Matthias all the best peter http://opengrok.openoffice.org/ - 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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
updating the translation process
Hello all. as you all know the translation process is stuck. Let me sum up the process, issue and my proposed solution. the basics We still use a SDF- definition file for our UI elements. The main benefit is that it is small. The larger po-files are used by pootle. This makes it necessary that we convert the Sdf file into a po-file and vice versa. the pootle team still maintains a converter tool, which can do the job. we have a script that automates the process. the script uses a git repo to counter errors. What issues do we currently have? - the translation tool is needs a newer python version, and the version available in the distribution does not work - the process with git is a local safety measure. - the script uses pootle installed tools, for extraction. - pootle is out of maintenance using a out dated version of django and python 2 As you see we have different issues that block this topic. The po file format is used by other open source translation tools so we can easily switch. This is why i would like to switch the translation tool at the end. first i would like to get the conversion process running. I think it would be best if we build the conversion in github. for this we need another translation repository. the idea would be that 1) nighties exports sdf on build bot 2) nighties pushes the export to github. i think on a sdf branch 3) trigger creates the conversion to po file and pushes the changes into a po branch. (using actions) 4) translation service pulls the po branch and imports it. This differs a bit from the current process, which does not is working locally and involves fetch from nighties and then local build. With the issue of meeting requirements on the server. any ideas, concerns or questions? all the best peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: updating the translation process
> On Aug 13, 2024, at 4:27 PM, Peter Kovacs wrote: > > Hello all. > > as you all know the translation process is stuck. Let me sum up the process, > issue and my proposed solution. > > the basics > > We still use a SDF- definition file for our UI elements. The main benefit is > that it is small. The larger po-files are used by pootle. > > This makes it necessary that we convert the Sdf file into a po-file and vice > versa. > > the pootle team still maintains a converter tool, which can do the job. > > we have a script that automates the process. the script uses a git repo to > counter errors. > > > What issues do we currently have? > > - the translation tool is needs a newer python version, and the version > available in the distribution does not work > > - the process with git is a local safety measure. > > - the script uses pootle installed tools, for extraction. > > - pootle is out of maintenance using a out dated version of django and python > 2 > > > As you see we have different issues that block this topic. > > The po file format is used by other open source translation tools so we can > easily switch. This is why i would like to switch the translation tool at the > end. > > first i would like to get the conversion process running. I think it would be > best if we build the conversion in github. > > for this we need another translation repository. > > the idea would be that > > 1) nighties exports sdf on build bot > > 2) nighties pushes the export to github. i think on a sdf branch > > 3) trigger creates the conversion to po file and pushes the changes into a po > branch. (using actions) > > 4) translation service pulls the po branch and imports it. > > > This differs a bit from the current process, which does not is working > locally and involves fetch from nighties and then local build. With the issue > of meeting requirements on the server. > > any ideas, concerns or questions? This seems like a good plan. I look forward to helping review the GitHub workflows and can help you with review and organization. If we need secrets we will need to get infra’s support. When the process is completed. Builds will import po files from this new repository in the po branch and these will be periodically or manually synched up from the translation service. It would be great if we could copy all the users from pootle to the new service. Best, Dave > > 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
