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
