I'd like to see it in one repo preferably
If we could (sort of) copy the directory structure from Pootle, I think we are 
halfway there
If space is an issue we might combine UI and HC2 if possible, however that 
might be a big one :-)

All languages have their own PO-files and sdf

On 2024/10/16 21:27:24 Peter Kovacs 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?
> 
> 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 .
> 
> 
> your thoughts?
> 
> cheers.
> 
> petko
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to