Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
BTW: Of course I am available for testing (since 2019 to be exact). I cannot merge my PRs [1][2] until we have solved this problem... Regards,    Matthias [1] https://github.com/apache/openoffice/pull/168 [2] https://github.com/apache/openoffice/pull/180 Am 28.07.24 um 17:54 schrieb Matthias

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
Hi Damjan, Am 28.07.24 um 17:42 schrieb Damjan Jovanovic: On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel wrote: Hi Aivaras, Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis: 2024-07-28 11:17, Matthias Seidel rašė: The last step would be to export the new translations to SDF files and to me

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
Am 28.07.24 um 17:51 schrieb Aivaras Stepukonis: 2024-07-28 18:38, Matthias Seidel rašė: The format is not the problem... 😉 We need to find volunteers who want to work on it. And we need to have the will to release AOO 4.2.0. The lack of volunteering is certainly /another/ problem; however,

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Aivaras Stepukonis
2024-07-28 18:38, Matthias Seidel rašė: The format is not the problem... 😉 We need to find volunteers who want to work on it. And we need to have the will to release AOO 4.2.0. The lack of volunteering is certainly /another/ problem; however, I don’t see how that explains that SDFs are not

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Damjan Jovanovic
On Sun, Jul 28, 2024 at 3:39 PM Matthias Seidel wrote: > Hi Aivaras, > > Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis: > > 2024-07-28 11:17, Matthias Seidel rašė: > >> The last step would be to export the new translations to SDF files > >> and to merge them with our code. > > > > While I’m not

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
Hi Aivaras, Am 28.07.24 um 17:32 schrieb Aivaras Stepukonis: 2024-07-28 11:17, Matthias Seidel rašė: The last step would be to export the new translations to SDF files and to merge them with our code. While I’m not in a position to appreciate the technical reasons for using SDF files, the wo

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Aivaras Stepukonis
2024-07-28 11:17, Matthias Seidel rašė: The last step would be to export the new translations to SDF files and to merge them with our code. While I’m not in a position to appreciate the technical reasons for using SDF files, the working format for localizers is PO files. From the standpoint

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
Dick, Am 28.07.24 um 11:55 schrieb Dick Groskamp: Matthias On 2024/07/28 08:17:48 Matthias Seidel wrote: Hi Dick, Am 27.07.24 um 15:37 schrieb Dick Groskamp: OK, looked into it a bit. >From the en-us.sdf new templates have to be created, which are then uploaded to Pootle. (This will add ne

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Dick Groskamp
Matthias On 2024/07/28 08:17:48 Matthias Seidel wrote: > Hi Dick, > > Am 27.07.24 um 15:37 schrieb Dick Groskamp: > > OK, looked into it a bit. > > > > >From the en-us.sdf new templates have to be created, which are then > > >uploaded to Pootle. > > (This will add new strings and mark deprecated

Re: Not yet translated functions UNICODE and UNICHAR

2024-07-28 Thread Matthias Seidel
Hi Dick, Am 27.07.24 um 15:37 schrieb Dick Groskamp: OK, looked into it a bit. >From the en-us.sdf new templates have to be created, which are then uploaded to Pootle. (This will add new strings and mark deprecated ones) After that, all existing translations have to be downloaded to disk The