Re: The way to 4.2.0

On Mon, Dec 30, 2024 at 1:07 AM Damjan Jovanovic wrote: > - Another "regression" (Bugzilla seems to be down?) which is Windows-only, > and has a known but ugly workaround - we leak the library handle like we > did before (and still do on 4.1.x), instead of releasing it properly. > > This is that

Re: The way to 4.2.0

> On Dec 29, 2024, at 5:17 PM, Aivaras Stepukonis wrote: > >> - Another "regression" (Bugzilla seems to be down?) which is Windows-only, >> and has a known but ugly workaround - we leak the library handle like we >> did before (and still do on 4.1.x), instead of releasing it properly. > This o

Re: The way to 4.2.0

- Another "regression" (Bugzilla seems to be down?) which is Windows-only, and has a known but ugly workaround - we leak the library handle like we did before (and still do on 4.1.x), instead of releasing it properly. This one, if I read it correctly, I can confirm. It is rather bad. As soon as f

Re: The way to 4.2.0

On Sun, Dec 29, 2024 at 9:12 PM Arrigo Marchiori wrote: > Hello all, > > On Sun, Dec 29, 2024 at 10:01:56AM +, Peter kovacs wrote: > > > Hi all. > > > > So let's discuss blockers of 4.2.0. > > > > I am only aware of translations 4.2.0 as a real blocker. > > There is a nasty, repeatable crash

Re: Regarding OpenOffice the Moribund.

Not exactly the reverse, but, yes, support OpenOffice in an inclusive manner. Exactly the reverse. One cannot support Open Office in an /exclusive/ manner because of the Apache license. And one can not support a derivative such as Libre Office in an /inclusive/ manner because of its license.

Re: Regarding OpenOffice the Moribund.

> On Dec 29, 2024, at 12:54 PM, Aivaras Stepukonis > wrote: > >> If you wish to have Apache OpenOffice continue to exist […] help support any >> and all OpenOffice derivatives. > I think it is the reverse, Dave. If you wish any and all Open Office > derivatives to continue to exist, help su

Re: The way to 4.2.0

Hello all, On Sun, Dec 29, 2024 at 10:01:56AM +, Peter kovacs wrote: > Hi all. > > So let's discuss blockers of 4.2.0. > > I am only aware of translations 4.2.0 as a real blocker. There is a nasty, repeatable crash of Impress under Windows. I tried to look into it some time ago but I fail

Re: Regarding OpenOffice the Moribund.

If you wish to have Apache OpenOffice continue to exist […] help support any and all OpenOffice derivatives. I think it is the reverse, Dave. If you wish any and all Open Office derivatives to continue to exist, help support Open Office. -- Pagarbiai / Sincerely, 📧 Aivaras Stepukonis

Re: Regarding OpenOffice the Moribund.

> On Dec 28, 2024, at 3:32 PM, Aivaras Stepukonis wrote: > > “Guerrilla marketing,” such as badmouthing Open Office and replacing > references to it with references to Libre Office in Wikipedia and elsewhere, > has been the norm for a long time now. A number of LO partizans use even > https

Re: The way to 4.2.0

> On Dec 29, 2024, at 2:49 AM, Matthias Seidel > wrote: > > Hi Peter, > > Am 29.12.24 um 11:01 schrieb Peter kovacs: >> Hi all. >> >> So let's discuss blockers of 4.2.0. >> >> I am only aware of translations 4.2.0 as a real blocker. > We still have other blocker to fix, but yes, translatio

Re: [PR] Fix grammar and spelling [openoffice-project]

sebbASF commented on PR #18: URL: https://github.com/apache/openoffice-project/pull/18#issuecomment-2564766430 Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To u

Re: [PR] Fix grammar and spelling [openoffice-project]

sebbASF merged PR #18: URL: https://github.com/apache/openoffice-project/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoff

[PR] Fix grammar and spelling [openoffice-project]

jbampton opened a new pull request, #18: URL: https://github.com/apache/openoffice-project/pull/18 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscri

[PR] Fix spelling [openoffice]

jbampton opened a new pull request, #235: URL: https://github.com/apache/openoffice/pull/235 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-

Re: Regarding OpenOffice the Moribund.

Hi Peter, Am 29.12.24 um 10:50 schrieb Peter kovacs: It was a hard fight to replace 'dead' with 'dormant' on Wikipedia. The German page is even more negative. But German Wikipedia is in general worse in that respect. Yes, personally I like Wikipedia but regarding OpenOffice there is so much ha

Re: The way to 4.2.0

Hi Peter, Am 29.12.24 um 11:01 schrieb Peter kovacs: Hi all. So let's discuss blockers of 4.2.0. I am only aware of translations 4.2.0 as a real blocker. We still have other blocker to fix, but yes, translation is the *real* blocker. Afaik it is unclear if our translations are still complet

The way to 4.2.0

Hi all. So let's discuss blockers of 4.2.0. I am only aware of translations 4.2.0 as a real blocker. Afaik it is unclear if our translations are still complete. So we need one time to convert the us sdf from the nightly build server (hope it builds) to PO format and then convert the translated

Re: Regarding OpenOffice the Moribund.

It was a hard fight to replace 'dead' with 'dormant' on Wikipedia. The German page is even more negative. But German Wikipedia is in general worse in that respect. It is funny that the guy said abandon ware since that is what tdf demands. That we abandon the AOO code line and recommend the LO c