Am 17.10.24 um 00:08 schrieb Dave Fisher:
On Oct 16, 2024, at 2:27 PM, Peter Kovacs <pe...@apache.org> wrote:
hi all.
mechtilde has set up a translation git repository for the process to save
translations in case something goes wrong with the conversion.
I added now a githup repository and i would like to convert our scripts that
they GitHub create a po file if a sdf file is checked in and vice versa.
why do we need this?
the translation is done in po files while Apache OpenOffice uses the self
invented translation file sdf. sdf files are about 50% smaller then po files.
changes in the code are extracted as the sdf file for us, which is used to
introduce new text into the translation process
Does pootle play a role?
not directly. po files are supported by all the translation tools while sdf is
not directly supported. But ther is an library that can do the conversion.
what i like to do is:
linux build bot -> sdf us -> github -> conversion -> po files -> transation tool -> translator
work -> po languages -> github -> conversion -> sdf file -> language release packaging.
may be we could maintain multiple versions if our sdf file stays backward
compatible. my understanding is there are breaking changes between 4.1 and 4.2.
What is the discussion about?
I would like to know your thoughts about if we should try to keep everything in
one repo and branch or split into a po branch and sdf pranch. or even into 2
repos?
I'm for a single repository. Since an SDF file and its PO file are produced
together it’s probably easier to have them each on the same branch. I
understand that we do need to split stuff up because this is too much for a
single branch.
What if we had a branch for each language? Would that help?
the pootle instance at least would like to import all files at once. we
would then need to check if a folder struckture would do the trick.
Another thought, currently we use one folder to import export, but
pootle and other services can work directly on git.
We need to check what the expect. While we have the blocker of upload
limit of 2GB, I have the thought is we manage everything in one branch
we need to solve the challenge to identify in which direction we want to
merge.
If the branch represents this, we could work with the assumption that on
sdf branch only sdf files are available and on po branch we would
probably want to transform to sdf file format.
We need only the to check on sdf if it is en_US or language files to
avoide a permanent toggle of tranform jobs. I would like to do this
within github actions.
the one repo solution we already hit githubs limit of 2GB per push for the
initial split. so the thought started to try to avoid a big file update on
github. each language takes about 60 mb .
How many languages do we have in Pootle?
Best,
Dave
your thoughts?
cheers.
petko
---------------------------------------------------------------------
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
