Fwd: Fwd: Open office for apple M2?

[Matthias Seidel]

For English speaking users, the link is of course:

https://adoptium.net/temurin/releases/?os=mac&arch=x64&package=jre&version=11



 Weitergeleitete Nachricht 
Betreff:    Re: Fwd: Open office for apple M2?
Datum:  Mon, 8 Jul 2024 16:29:10 +0200
Von:Matthias Seidel 
Antwort an: dev@openoffice.apache.org
An: dev@openoffice.apache.org



Larry,

I am not a Mac user.

But for an Intel version of AOO you will need an *Intel* version of JAVA.

So please try to install it (the recommended versions are still 8 and 
11, both LTS):


https://adoptium.net/de/temurin/releases/?os=mac&arch=x64&package=jre&version=11

Be sure to activate it in AOO after install.

Regards,

   Matthias

Am 08.07.24 um 11:59 schrieb Larry Gusaas:

On 2024-07-07 3:08 a.m., Matthias Seidel wrote:

Hi All,

Am 06.07.24 um 14:09 schrieb Rony G. Flatscher:

Any news on this?

As more and more Apple computers with M1, M2 processors become part 
of the market a missing arm64 version of AOO for macOS causes people 
to turn to LibreOffice (and quietly so).


To be clear, this is not about an Arm version of AOO, but to inform 
our users that the existing Intel version runs perfectly (via Rosetta 
2) on an M1, M2,... CPU.



Wrong. Database does not work. Keep getting messages "JRE is 
defective" and "No Java installation could be found". I just upgraded 
to  JRE 22.0.1 (jdk-22_macos-aarch64_ 
<https://download.oracle.com/java/22/latest/jdk-22_macos-aarch64_bin.dmg>). 
on MacBook Air M1. Earlier versions of java did not work either. Have 
not been able to use Database since I got new MacBook in 2021





But nobody seems to be interested in giving our users this information.

That said: I am not going to do that either. There are enough people 
that could start contributing NOW!


Matthias





smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Fwd: Open office for apple M2?

[Matthias Seidel]

Larry,

I am not a Mac user.

But for an Intel version of AOO you will need an *Intel* version of JAVA.

So please try to install it (the recommended versions are still 8 and 
11, both LTS):


https://adoptium.net/de/temurin/releases/?os=mac&arch=x64&package=jre&version=11

Be sure to activate it in AOO after install.

Regards,

   Matthias

Am 08.07.24 um 11:59 schrieb Larry Gusaas:

On 2024-07-07 3:08 a.m., Matthias Seidel wrote:

Hi All,

Am 06.07.24 um 14:09 schrieb Rony G. Flatscher:

Any news on this?

As more and more Apple computers with M1, M2 processors become part 
of the market a missing arm64 version of AOO for macOS causes people 
to turn to LibreOffice (and quietly so).


To be clear, this is not about an Arm version of AOO, but to inform 
our users that the existing Intel version runs perfectly (via Rosetta 
2) on an M1, M2,... CPU.



Wrong. Database does not work. Keep getting messages "JRE is 
defective" and "No Java installation could be found". I just upgraded 
to  JRE 22.0.1 (jdk-22_macos-aarch64_ 
). 
on MacBook Air M1. Earlier versions of java did not work either. Have 
not been able to use Database since I got new MacBook in 2021





But nobody seems to be interested in giving our users this information.

That said: I am not going to do that either. There are enough people 
that could start contributing NOW!


Matthias





smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Fwd: Open office for apple M2?

[Larry Gusaas]

On 2024-07-07 3:08 a.m., Matthias Seidel wrote:

Hi All,

Am 06.07.24 um 14:09 schrieb Rony G. Flatscher:

Any news on this?

As more and more Apple computers with M1, M2 processors become part of the market a missing 
arm64 version of AOO for macOS causes people to turn to LibreOffice (and quietly so).


To be clear, this is not about an Arm version of AOO, but to inform our users that the 
existing Intel version runs perfectly (via Rosetta 2) on an M1, M2,... CPU.



Wrong. Database does not work. Keep getting messages "JRE is defective" and "No Java 
installation could be found". I just upgraded to  JRE 22.0.1 (jdk-22_macos-aarch64_ 
). on MacBook Air M1. 
Earlier versions of java did not work either. Have not been able to use Database since I got 
new MacBook in 2021





But nobody seems to be interested in giving our users this information.

That said: I am not going to do that either. There are enough people that could start 
contributing NOW!


Matthias



--
_

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website:http://larry-gusaas.com

"An artist is never ahead of his time but most people are far behind theirs." - 
Edgard Varese

Re: Fwd: Open office for apple M2?

[Matthias Seidel]

Hi All,

Am 06.07.24 um 14:09 schrieb Rony G. Flatscher:

Any news on this?

As more and more Apple computers with M1, M2 processors become part of 
the market a missing arm64 version of AOO for macOS causes people to 
turn to LibreOffice (and quietly so).


To be clear, this is not about an Arm version of AOO, but to inform our 
users that the existing Intel version runs perfectly (via Rosetta 2) on 
an M1, M2,... CPU.


But nobody seems to be interested in giving our users this information.

That said: I am not going to do that either. There are enough people 
that could start contributing NOW!


Matthias



---rony



On 16.04.2024 19:30, Matthias Seidel wrote:

Hi All,

Am 16.04.24 um 10:28 schrieb serena castaldi:

Hello,
I have been trying to install Open Office on my most recent MacBook 
Air M2 and then found that there is not an updated version that can 
work on this computer. Or at least I could not find it to download.

DO you have any information on this topic?
Thank you
Serena Castaldi


The "Platform Hints" section for macOS needs to be updated for a 
along time. (Coming soon...)


Any volunteer?

Matthias

[1] https://www.openoffice.org/download/platform_hints.html 


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Fwd: Open office for apple M2?

[Rony G. Flatscher]

Any news on this?

As more and more Apple computers with M1, M2 processors become part of the market a missing arm64 
version of AOO for macOS causes people to turn to LibreOffice (and quietly so).


---rony



On 16.04.2024 19:30, Matthias Seidel wrote:

Hi All,

Am 16.04.24 um 10:28 schrieb serena castaldi:

Hello,
I have been trying to install Open Office on my most recent MacBook Air M2 and then found that 
there is not an updated version that can work on this computer. Or at least I could not find it 
to download.

DO you have any information on this topic?
Thank you
Serena Castaldi


The "Platform Hints" section for macOS needs to be updated for a along time. 
(Coming soon...)

Any volunteer?

Matthias

[1] https://www.openoffice.org/download/platform_hints.html 


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

Fwd: Your proposal: Apache OpenOffice and Free Software for business tasks

[Dr. Michael Stehmann]

Hello,

we will have a booth on T-DOSE.

https://t-dose.org/2024/

Regards
Michael

 Weitergeleitete Nachricht 
Betreff: Your proposal: Apache OpenOffice and Free Software for business 
tasks

Datum: Mon, 29 Apr 2024 21:06:40 -
Von: T-DOSE 2024 
Antwort an: T-DOSE 2024 
An: mich...@canzeley.de

Hi!

We are happy to tell you that we accept your proposal "Apache OpenOffice 
and Free Software for business tasks"

to T-DOSE 2024. Please click this link to confirm your attendance:

https://pretalx.t-dose.org/2024/me/submissions/XBFKAR/confirm

We look forward to seeing you at T-DOSE 2024 - Please contact us if you 
have any

questions! We will reach out again before the conference to tell you details
about your slot in the schedule and technical details concerning the room
and presentation tech.

See you there!
The T-DOSE 2024 organisers


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Fwd: Open office for apple M2?

[Matthias Seidel]

Hi All,

Am 16.04.24 um 10:28 schrieb serena castaldi:

Hello,
I have been trying to install Open Office on my most recent MacBook Air M2 and 
then found that there is not an updated version that can work on this computer. 
Or at least I could not find it to download.
DO you have any information on this topic?
Thank you
Serena Castaldi


The "Platform Hints" section for macOS needs to be updated for a along 
time. (Coming soon...)


Any volunteer?

Matthias

[1] https://www.openoffice.org/download/platform_hints.html



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Fwd: Open office for apple M2?

[serena castaldi]

> Hello, 
> I have been trying to install Open Office on my most recent MacBook Air M2 
> and then found that there is not an updated version that can work on this 
> computer. Or at least I could not find it to download.
> DO you have any information on this topic?
> Thank you 
> Serena Castaldi


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

Re: Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[Arrigo Marchiori]

Hello All,

On Thu, Mar 28, 2024 at 11:48:03AM +1030, David wrote:

> I believe self service registration to Bugzilla has been disabled for
> several years - see for example
> https://www.mail-archive.com/dev@openoffice.apache.org/msg39684.html

Yes, and I agree that registration should be advertised in a clear way
on the homepage.

The current BZ entry page [1] is full of information (including the
wrong email address reported by John Silver).

> Dave Fisher wrote:
[...]
> > I think that at a minimum we should:
> > 
> > 1. Change the footer text on our bugzilla [...]
> > To
> > 
> > “For additional information about this Bugzilla instance including 
> > requesting an account please see [about Bug 
> > Tracking](https://openoffice.apache.org/bug-tracking.html 
> > }’

+1

I suggest this link should also be added below the search box,
before the "Apache OpenOffice (AOO) Bugzilla User's Guide" link.

> > 2. We can then add improvements to the bug-tracking page at any time.

+1

Best regards,
-- 
Arrigo

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

Re: Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[Dave Fisher]

> On Mar 27, 2024, at 5:34 PM, Marcus  wrote:
> 
> Am 27.03.24 um 23:21 schrieb Dave Fisher:
>> It seems that it has become difficult to create a bugzilla account and we 
>> need to update our guidance/
>> I think that at a minimum we should:
>> 1. Change the footer text on our bugzilla that reads
>> "In case of problems with the functioning of Apache OpenOffice (AOO) 
>> Bugzilla, please contact aoo-bugzilla-ad...@apache.org. Please Note:this 
>> e-mail address is only for reporting problems with Apache OpenOffice (AOO) 
>> Bugzilla. Mail about any other subject will be silently ignored.”
>> To
>> “For additional information about this Bugzilla instance including 
>> requesting an account please see [about Bug 
>> Tracking](https://openoffice.apache.org/bug-tracking.html 
>> }’
>> 2. We can then add improvements to the bug-tracking page at any time.
> 
> first we should clarify if we want to use the existing description Wiki page 
> [1] or to add much text to the projects page [2].
> 
>> Anything else?
> 
> I don't see any setting in the admin sections of Bugzilla. So, I think we 
> need the Infra team to change the text.

Exactly. That’s why I want consensus before the request.

> 
> [1] https://wiki.openoffice.org/wiki/QA/HowToFileIssue
> [2] https://openoffice.apache.org/bug-tracking.html

[2] Should point to [1]. [1] should be edited to remove discussion of “create” 
an account.

[2] is about filing a bug while [1] is about the bug tracker ...

Best,
Dave

> 
> Marcus
> 
> 
> 
>>> Begin forwarded message:
>>> 
>>> From: David 
>>> Subject: Re: New Open Office account?
>>> Date: March 27, 2024 at 2:43:00 PM PDT
>>> To: us...@openoffice.apache.org
>>> Reply-To: us...@openoffice.apache.org
>>> 
>>> The account creation page  with that information seems to have been 
>>> disabled; however that email address aoo-bugzilla-ad...@apache.org is also 
>>> referenced in the footer on every page on Bugzilla.
>>> 
>>> Dave Fisher wrote:
 Try sysad...@openoffice.apache.org 
 
 If you could also identify the url where you see that notice and send that 
 as well.
 
 Best,
 Dave
 
> On Mar 27, 2024, at 4:57 AM, john silver  
> wrote:
> 
> How would one go about getting a New Open Office account to submit bugs 
> or suggestions? previously when I went to get a new account it said "User 
> account creation has been disabled." and that I need to send an email to 
> aoo-bugzilla-ad...@apache.org but when I sent the email it came back with 
> a failure notice.
> 
> 
> -
> 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

Re: Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[David]

I believe self service registration to Bugzilla has been disabled for 
several years - see for example 
https://www.mail-archive.com/dev@openoffice.apache.org/msg39684.html


Dave Fisher wrote:

HI -

It seems that it has become difficult to create a bugzilla account and we need 
to update our guidance/

I think that at a minimum we should:

1. Change the footer text on our bugzilla that reads

"In case of problems with the functioning of Apache OpenOffice (AOO) Bugzilla, 
please contact aoo-bugzilla-ad...@apache.org. Please Note:this e-mail address is 
only for reporting problems with Apache OpenOffice (AOO) Bugzilla. Mail about any 
other subject will be silently ignored.”

To

“For additional information about this Bugzilla instance including requesting an 
account please see [about Bug 
Tracking](https://openoffice.apache.org/bug-tracking.html 
}’

2. We can then add improvements to the bug-tracking page at any time.

Anything else?

Best,
Dave



Begin forwarded message:

From: David 
Subject: Re: New Open Office account?
Date: March 27, 2024 at 2:43:00 PM PDT
To: us...@openoffice.apache.org
Reply-To: us...@openoffice.apache.org

The account creation page  with that information seems to have been disabled; 
however that email address aoo-bugzilla-ad...@apache.org is also referenced in 
the footer on every page on Bugzilla.

Dave Fisher wrote:

Try sysad...@openoffice.apache.org 

If you could also identify the url where you see that notice and send that as 
well.

Best,
Dave


On Mar 27, 2024, at 4:57 AM, john silver  wrote:

How would one go about getting a New Open Office account to submit bugs or suggestions? 
previously when I went to get a new account it said "User account creation has been 
disabled." and that I need to send an email to aoo-bugzilla-ad...@apache.org but 
when I sent the email it came back with a failure notice.

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



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






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

Re: Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[Marcus]

Am 27.03.24 um 23:21 schrieb Dave Fisher:

It seems that it has become difficult to create a bugzilla account and we need 
to update our guidance/

I think that at a minimum we should:

1. Change the footer text on our bugzilla that reads

"In case of problems with the functioning of Apache OpenOffice (AOO) Bugzilla, 
please contact aoo-bugzilla-ad...@apache.org. Please Note:this e-mail address is 
only for reporting problems with Apache OpenOffice (AOO) Bugzilla. Mail about any 
other subject will be silently ignored.”

To

“For additional information about this Bugzilla instance including requesting an 
account please see [about Bug 
Tracking](https://openoffice.apache.org/bug-tracking.html 
}’

2. We can then add improvements to the bug-tracking page at any time.


first we should clarify if we want to use the existing description Wiki 
page [1] or to add much text to the projects page [2].



Anything else?


I don't see any setting in the admin sections of Bugzilla. So, I think 
we need the Infra team to change the text.


[1] https://wiki.openoffice.org/wiki/QA/HowToFileIssue
[2] https://openoffice.apache.org/bug-tracking.html

Marcus




Begin forwarded message:

From: David 
Subject: Re: New Open Office account?
Date: March 27, 2024 at 2:43:00 PM PDT
To: us...@openoffice.apache.org
Reply-To: us...@openoffice.apache.org

The account creation page  with that information seems to have been disabled; 
however that email address aoo-bugzilla-ad...@apache.org is also referenced in 
the footer on every page on Bugzilla.

Dave Fisher wrote:

Try sysad...@openoffice.apache.org 

If you could also identify the url where you see that notice and send that as 
well.

Best,
Dave


On Mar 27, 2024, at 4:57 AM, john silver  wrote:

How would one go about getting a New Open Office account to submit bugs or suggestions? 
previously when I went to get a new account it said "User account creation has been 
disabled." and that I need to send an email to aoo-bugzilla-ad...@apache.org but 
when I sent the email it came back with a failure notice.



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

Bugzilla Improvement to fix confusion Fwd: New Open Office account?

[Dave Fisher]

HI -

It seems that it has become difficult to create a bugzilla account and we need 
to update our guidance/

I think that at a minimum we should:

1. Change the footer text on our bugzilla that reads 

"In case of problems with the functioning of Apache OpenOffice (AOO) Bugzilla, 
please contact aoo-bugzilla-ad...@apache.org. Please Note:this e-mail address 
is only for reporting problems with Apache OpenOffice (AOO) Bugzilla. Mail 
about any other subject will be silently ignored.”

To

“For additional information about this Bugzilla instance including requesting 
an account please see [about Bug 
Tracking](https://openoffice.apache.org/bug-tracking.html 
}’

2. We can then add improvements to the bug-tracking page at any time.

Anything else?

Best,
Dave


> Begin forwarded message:
> 
> From: David 
> Subject: Re: New Open Office account?
> Date: March 27, 2024 at 2:43:00 PM PDT
> To: us...@openoffice.apache.org
> Reply-To: us...@openoffice.apache.org
> 
> The account creation page  with that information seems to have been disabled; 
> however that email address aoo-bugzilla-ad...@apache.org is also referenced 
> in the footer on every page on Bugzilla.
> 
> Dave Fisher wrote:
>> Try sysad...@openoffice.apache.org 
>> 
>> If you could also identify the url where you see that notice and send that 
>> as well.
>> 
>> Best,
>> Dave
>> 
>>> On Mar 27, 2024, at 4:57 AM, john silver  wrote:
>>> 
>>> How would one go about getting a New Open Office account to submit bugs or 
>>> suggestions? previously when I went to get a new account it said "User 
>>> account creation has been disabled." and that I need to send an email to 
>>> aoo-bugzilla-ad...@apache.org but when I sent the email it came back with a 
>>> failure notice.
>>> 
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: users-h...@openoffice.apache.org
>>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: users-h...@openoffice.apache.org
> 

Fwd: Input Needed: Software for the Public Good Stories

[Matthias Seidel]

Hi All,

FYI

Matthias



 Weitergeleitete Nachricht 
Betreff:Re: Input Needed: Software for the Public Good Stories
Datum:  Tue, 28 Nov 2023 10:57:35 -0800
Von:Whitney True 
Antwort an: d...@community.apache.org
An: d...@community.apache.org
Kopie (CC): mark...@apache.org



Hello ASF Community,

The ASF M&P team is hoping to showcase how the ASF Community has helped
provide software for the public good in celebration of the ASF's 25th
anniversary. We hope you will be willing to share a story for the ASF blog
and social media channels. Please fill out this short form.


Here is a reminder of the types of stories we are looking for:

- Case studies that showcase how your project’s technology is being used;
- Details surrounding an important forthcoming project milestone; or
- Any other ways your project embodies the ASF mission and way? Please
use this form anytime you have an exciting milestone to share.


*And please note you can submit more than once!*
Many thanks for your time and input,
Whitney
On Behalf of the ASF M&P team

On Tue, Nov 7, 2023 at 9:30 AM Whitney True  wrote:


Hello ASF Community,

As the ASF nears its 25th anniversary, we want to showcase how the ASF
community has helped realize the Foundation's mission of providing software
for the public good.

The ASF Marketing & Publicity (M&P) team will be showcasing major
milestones and public good stories across the ASF’s blog and social media
channels. We hope you'll be willing to share a story by filling out this
short form.

What are we looking for?

- Case studies that showcase how your project’s technology is being
used;
- Details surrounding an important forthcoming project milestone; or
- Any other ways your project embodies the ASF mission and way? Please
use this form anytime you have an exciting milestone to share.

***Please note you can submit more than once!** *

Many thanks for your time and input,
Whitney
On Behalf of the ASF M&P team








smime.p7s
Description: Kryptografische S/MIME-Signatur

Fwd: New Pootle Account

[Matthias Seidel]

 Weitergeleitete Nachricht 
Betreff:New Pootle Account
Datum:  Wed, 1 Nov 2023 09:25:50 +0200
Von:Валентин Андриюк 
Antwort an: l...@openoffice.apache.org
An: l...@openoffice.apache.org



Hello my name is Valentine and I'm from Ukraine
Please create a Pootle account for me. I state that my contributions are
under
the Apache 2 license and I will work on ukrainian language.
My preferred username is Andriyuk.


smime.p7s
Description: Kryptografische S/MIME-Signatur

Fwd: [madler/zlib] Release v1.3 - zlib 1.3

[Matthias Seidel]

FYI:



 Weitergeleitete Nachricht 
Betreff:[madler/zlib] Release v1.3 - zlib 1.3
Datum:  Fri, 18 Aug 2023 03:00:18 -0700
Von:Mark Adler 
Antwort an: madler/zlib 
An: madler/zlib 
Kopie (CC): Subscribed 



 zlib 1.3 

Repository: madler/zlib  · Tag: v1.3 
 · Commit: 09155ea 
 
· Released by: madler 



 zlib 1.3 Release Notes

/August 18, 2023/

Version 1.3 has these key changes:

 * Building using K&R (pre-ANSI) function definitions is no longer
   supported.
 * Fixed a bug in deflateBound() for level 0 and memLevel 9.
 * Fixed a bug when gzungetc() is used immediately after gzopen().
 * Fixed a bug when using gzflush() with a very small buffer.
 * Fixed a crash when gzsetparams() is attempted for a transparent write.
 * Fixed test/example.c to work with FORCE_STORED.
 * Fixed minizip to allow it to open an empty zip file.
 * Fixed reading disk number start on zip64 files in minizip.
 * Fixed a logic error in minizip argument processing.

—

This release has 8 assets:

 * zlib-1.3.tar.gz
 * zlib-1.3.tar.gz.asc
 * zlib-1.3.tar.xz
 * zlib-1.3.tar.xz.asc
 * zlib13.zip
 * zlib13.zip.asc
 * Source code (zip)
 * Source code (tar.gz)

Visit the release page 
 to download them.


—
You are receiving this because you are watching this repository.
View it on GitHub  or 
unsubscribe 
 
from all notifications for this repository.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Install AOO via winget on Windows 10/11

[Matthias Seidel]

Hi,

Am 04.06.23 um 11:04 schrieb Peter Kovacs:
> Maybe this would be good in a installation guide?

Yes, I plan to update:

https://wiki.openoffice.org/wiki/Documentation/FAQ/Installation/How_do_I_install_Apache_OpenOffice_on_Windows%3F

as I already did for the Microsoft Store.

Regards,

   Matthias

> Am 04.06.23 um 10:58 schrieb Matthias Seidel:
>>
>> Re-send
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: Install AOO via winget on Windows 10/11
>> Datum: Sat, 3 Jun 2023 20:32:10 +0200
>> Von: Matthias Seidel 
>> An: dev@openoffice.apache.org 
>>
>>
>>
>> Hi,
>>
>> FYI, I recently learned about using "winget".
>>
>> This is Microsofts commandline package manager for Windows 10/11.
>>
>> While the OpenOffice package information is still showing 4.1.13 [1] one
>> can always install the latest version from msstore:
>>
>> winget install XP89J5462CMGJD
>>
>> If you want to install AOO in a different language simply add the
>> locale, e.g.:
>>
>> winget install XP89J5462CMGJD --locale en-US
>>
>> BTW: We have 38 of our 41 locales available in msstore (missing are:
>> ast, ca-XV, ca-XR).
>>
>> For detailed info about AOO use:
>>
>> winget show XP89J5462CMGJD
>>
>> Regards,
>>
>>    Matthias
>>
>> [1]
>> https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/Apache/OpenOffice
>>
>>
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Install AOO via winget on Windows 10/11

[Peter Kovacs]

Maybe this would be good in a installation guide?

Am 04.06.23 um 10:58 schrieb Matthias Seidel:


Re-send



 Weitergeleitete Nachricht 
Betreff:Install AOO via winget on Windows 10/11
Datum:  Sat, 3 Jun 2023 20:32:10 +0200
Von:Matthias Seidel 
An: dev@openoffice.apache.org 



Hi,

FYI, I recently learned about using "winget".

This is Microsofts commandline package manager for Windows 10/11.

While the OpenOffice package information is still showing 4.1.13 [1] one
can always install the latest version from msstore:

winget install XP89J5462CMGJD

If you want to install AOO in a different language simply add the
locale, e.g.:

winget install XP89J5462CMGJD --locale en-US

BTW: We have 38 of our 41 locales available in msstore (missing are:
ast, ca-XV, ca-XR).

For detailed info about AOO use:

winget show XP89J5462CMGJD

Regards,

   Matthias

[1]
https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/Apache/OpenOffice

Fwd: Install AOO via winget on Windows 10/11

[Matthias Seidel]

Re-send



 Weitergeleitete Nachricht 
Betreff:Install AOO via winget on Windows 10/11
Datum:  Sat, 3 Jun 2023 20:32:10 +0200
Von:Matthias Seidel 
An: dev@openoffice.apache.org 



Hi,

FYI, I recently learned about using "winget".

This is Microsofts commandline package manager for Windows 10/11.

While the OpenOffice package information is still showing 4.1.13 [1] one
can always install the latest version from msstore:

winget install XP89J5462CMGJD

If you want to install AOO in a different language simply add the
locale, e.g.:

winget install XP89J5462CMGJD --locale en-US

BTW: We have 38 of our 41 locales available in msstore (missing are:
ast, ca-XV, ca-XR).

For detailed info about AOO use:

winget show XP89J5462CMGJD

Regards,

   Matthias

[1]
https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/Apache/OpenOffice




smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: Re: User Installation Process Feedback

[Pedro Lino]

Resending my email from yesterday :)
 
-- Original Message --
From: Pedro Lino 
To: dev@openoffice.apache.org
Date: 05/08/2023 6:32 PM WEST
Subject: Re: User Installation Process Feedback
 
 
Hi Andrea

> On 05/08/2023 5:37 PM BST Andrea Pescetti  mailto:pesce...@apache.org> wrote:
>  
>  
> On 07/05/23 Dave Fisher wrote:
> 
> > For those just now looking into this here is a link: 
> > https://docs.appimage.org/
> > If we switch to this packaging it appears that we can significantly reduce 
> > the many Linux packages we create when we release.
> > 
> I've done a recent build to produce an AppImage a few weeks (ahem..)
> ago, but I missed the final packaging and did not have time for it.
>  
> I can complete it and put it somewehere on home.apache.org next weekend
> if anyone wishes to play with it.
> 
 
Yes, please!
Is it 4.1.14?
 
Thanks!
Pedro

>  
> It's basically the same as
> https://archive.fosdem.org/2022/schedule/event/openoffice_linux_packaging/
>  
> Regards,
> Andrea.
>  
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> mailto:dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> mailto:dev-h...@openoffice.apache.org
> 

Fwd: [Remix-Design/RemixIcon] Release v3.0.0 - v3.0.0

[Matthias Seidel]

FYI

Again, I think this would be a wonderful source for a "Dark Mode" icon
theme...

Volunteers?

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:[Remix-Design/RemixIcon] Release v3.0.0 - v3.0.0
Datum:  Sat, 01 Apr 2023 02:38:01 -0700
Von:Wendy Gao 
Antwort an: Remix-Design/RemixIcon 
An: Remix-Design/RemixIcon 
Kopie (CC): Subscribed 



  v3.0.0 

Repository: Remix-Design/RemixIcon
 · Tag: v3.0.0
 · Commit:
6aeb080

· Released by: wendygaoyuan 


  🎉 ADD

New arrow category, related icons have also been moved to this category.

Added 156 icons, including AI related icons: |arrow-down-double|
|arrow-left-double| |arrow-right-double| |arrow-turn-back|
|arrow-turn-forward| |arrow-up-double| |bard| |bootstrap| |box-1|
|box-2| |box-3| |brain| |candle| |cash| |contract-left|
|contract-left-right| |contract-right| |contract-up-down| |copilot|
|corner-down-left| |corner-down-right| |corner-left-down|
|corner-left-up| |corner-right-down| |corner-right-up|
|corner-up-left-double| |corner-up-left| |corner-up-right-double|
|corner-up-right| |cross| |edge-new| |equal| |expand-left|
|expand-left-right| |expand-right| |expand-up-down| |flickr|
|forward-10| |forward-15| |forward-30| |forward-5| |graduation-cap|
|home-office| |hourglass-2| |hourglass| |javascript| |loop-left|
|loop-right| |memories| |meta| |microsoft-loop| |nft| |notion| |openai|
|overline| |p2p| |presentation| |replay-10| |replay-15| |replay-30|
|replay-5| |school| |shining-2| |shining| |sketching| |skip-down|
|skip-left| |skip-right| |skip-up| |slow-down| |sparkling-2| |sparkling|
|speak| |speed-up| |tiktok| |token-swap| |unpin| |wechat-channels|
|wordpress| ;


  🌟 UPDATE

According to the latest logo style, redesigned |discord| and |gitlab| icons;


  💊 FIX

Changed the baseline of iconfont, now icons should be vertically aligned
with the text.

—

This release has 4 assets:

  * RemixIcon_Fonts_v3.0.0.zip
  * RemixIcon_Svg_v3.0.0.zip
  * Source code (zip)
  * Source code (tar.gz)

Visit the release page
 to
download them.

—
You are receiving this because you are watching this repository.
View it on GitHub
 or
unsubscribe

from all notifications for this repository.



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: TAC supporting Berlin Buzzwords

[Marcus]

For your information.



 Weitergeleitete Nachricht 
Subject: TAC supporting Berlin Buzzwords
Date:Fri, 24 Mar 2023 10:56:36 +0100
From:Gavin McDonald 



Hi All,

The ASF Travel Assistance Committee is supporting taking up to six (6) 
people to attend Berlin Buzzwords In June this year.


This includes Conference passes, and travel & accommodation as needed.

Please see our website at https://tac.apache.org 
 for more information and how to apply.


Applications close on 15th April.

Good luck to those that apply.

Gavin McDonald (VP TAC)


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

Re: Fwd: E-mail address for publishing extensions is wrong

[Matthias Seidel]

Needless to say that the extension is uploaded for LO without problems...
You can imagine what will happen in the future?

Really, I am concerned about the lack of response here!

Am 14.03.23 um 23:50 schrieb Matthias Seidel:
>
> Nobody interested?
>
> If we are not able to get the site functional again we should think
> about shutting it down...
>
> Regards,
>
>    Matthias
>
> Am 13.03.23 um 18:04 schrieb Matthias Seidel:
>>
>> FYI:
>>
>> This message was created automatically by mail delivery software.
>>
>> A message that you sent could not be delivered to one or more of its
>> recipients. This is a permanent error. The following address(es) failed:
>>
>>   nore...@extensions.openoffice.org
>> retry timeout exceeded
>> Am 11.03.23 um 19:07 schrieb Matthias Seidel:
>>>
>>> Hi All,
>>>
>>> The extension site gets more and more broken...
>>>
>>> I don't have the time to spend hours on every new extension that
>>> someone wants to publish.
>>>
>>> Maybe we should get the problems fixed?
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>> Am 09.03.23 um 17:46 schrieb Matthias Seidel:

 Hello All,

 FYI:

 While I can publish the extension page, the downloadable files are
 (again) not to be found in the SourceForge database.

 Apart from that, we need a working mail address for users to
 contact us.

 Regards,

    Matthias


  Weitergeleitete Nachricht 
 Betreff:   E-mail address for publishing extensions is wrong
 Datum: Thu, 9 Mar 2023 17:24:20 +0100
 Von:   Bogdan 
 Antwort an:us...@openoffice.apache.org
 An:us...@openoffice.apache.org



 Hello.

 After I created my extension, I wanted to publish it, but instead I
 saw the message:

 "
 This extension is currently not published. Please contact the
 system administrator at nore...@extensions.openoffice.org to have
 it published, including a link to this page.
 "

 What would be the actual address to write to? Because it isn't
 "noreply", right?

 The extension is:
 https://extensions.openoffice.org/en/project/keyparastocx

 Thank you!

 -- 
 Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
 X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
 Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
 www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: E-mail address for publishing extensions is wrong

[Matthias Seidel]

Nobody interested?

If we are not able to get the site functional again we should think
about shutting it down...

Regards,

   Matthias

Am 13.03.23 um 18:04 schrieb Matthias Seidel:
>
> FYI:
>
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   nore...@extensions.openoffice.org
> retry timeout exceeded
> Am 11.03.23 um 19:07 schrieb Matthias Seidel:
>>
>> Hi All,
>>
>> The extension site gets more and more broken...
>>
>> I don't have the time to spend hours on every new extension that
>> someone wants to publish.
>>
>> Maybe we should get the problems fixed?
>>
>> Regards,
>>
>>    Matthias
>>
>> Am 09.03.23 um 17:46 schrieb Matthias Seidel:
>>>
>>> Hello All,
>>>
>>> FYI:
>>>
>>> While I can publish the extension page, the downloadable files are
>>> (again) not to be found in the SourceForge database.
>>>
>>> Apart from that, we need a working mail address for users to contact us.
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>>
>>>  Weitergeleitete Nachricht 
>>> Betreff:E-mail address for publishing extensions is wrong
>>> Datum:  Thu, 9 Mar 2023 17:24:20 +0100
>>> Von:Bogdan 
>>> Antwort an: us...@openoffice.apache.org
>>> An: us...@openoffice.apache.org
>>>
>>>
>>>
>>> Hello.
>>>
>>> After I created my extension, I wanted to publish it, but instead I
>>> saw the message:
>>>
>>> "
>>> This extension is currently not published. Please contact the system
>>> administrator at nore...@extensions.openoffice.org to have it
>>> published, including a link to this page.
>>> "
>>>
>>> What would be the actual address to write to? Because it isn't
>>> "noreply", right?
>>>
>>> The extension is:
>>> https://extensions.openoffice.org/en/project/keyparastocx
>>>
>>> Thank you!
>>>
>>> -- 
>>> Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
>>> X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
>>> Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
>>> www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: users-h...@openoffice.apache.org
>>>


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: E-mail address for publishing extensions is wrong

[Matthias Seidel]

FYI:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  nore...@extensions.openoffice.org
retry timeout exceeded

Am 11.03.23 um 19:07 schrieb Matthias Seidel:
>
> Hi All,
>
> The extension site gets more and more broken...
>
> I don't have the time to spend hours on every new extension that
> someone wants to publish.
>
> Maybe we should get the problems fixed?
>
> Regards,
>
>    Matthias
>
> Am 09.03.23 um 17:46 schrieb Matthias Seidel:
>>
>> Hello All,
>>
>> FYI:
>>
>> While I can publish the extension page, the downloadable files are
>> (again) not to be found in the SourceForge database.
>>
>> Apart from that, we need a working mail address for users to contact us.
>>
>> Regards,
>>
>>    Matthias
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: E-mail address for publishing extensions is wrong
>> Datum:   Thu, 9 Mar 2023 17:24:20 +0100
>> Von: Bogdan 
>> Antwort an:  us...@openoffice.apache.org
>> An:  us...@openoffice.apache.org
>>
>>
>>
>> Hello.
>>
>> After I created my extension, I wanted to publish it, but instead I
>> saw the message:
>>
>> "
>> This extension is currently not published. Please contact the system
>> administrator at nore...@extensions.openoffice.org to have it
>> published, including a link to this page.
>> "
>>
>> What would be the actual address to write to? Because it isn't
>> "noreply", right?
>>
>> The extension is:
>> https://extensions.openoffice.org/en/project/keyparastocx
>>
>> Thank you!
>>
>> -- 
>> Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
>> X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
>> Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
>> www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: users-h...@openoffice.apache.org
>>


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: E-mail address for publishing extensions is wrong

[Matthias Seidel]

Hi All,

The extension site gets more and more broken...

I don't have the time to spend hours on every new extension that someone
wants to publish.

Maybe we should get the problems fixed?

Regards,

   Matthias

Am 09.03.23 um 17:46 schrieb Matthias Seidel:
>
> Hello All,
>
> FYI:
>
> While I can publish the extension page, the downloadable files are
> (again) not to be found in the SourceForge database.
>
> Apart from that, we need a working mail address for users to contact us.
>
> Regards,
>
>    Matthias
>
>
>  Weitergeleitete Nachricht 
> Betreff:  E-mail address for publishing extensions is wrong
> Datum:Thu, 9 Mar 2023 17:24:20 +0100
> Von:  Bogdan 
> Antwort an:   us...@openoffice.apache.org
> An:   us...@openoffice.apache.org
>
>
>
> Hello.
>
> After I created my extension, I wanted to publish it, but instead I
> saw the message:
>
> "
> This extension is currently not published. Please contact the system
> administrator at nore...@extensions.openoffice.org to have it
> published, including a link to this page.
> "
>
> What would be the actual address to write to? Because it isn't
> "noreply", right?
>
> The extension is:
> https://extensions.openoffice.org/en/project/keyparastocx
>
> Thank you!
>
> -- 
> Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
> X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
> Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
> www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org
>
> -
> To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: users-h...@openoffice.apache.org
>


smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: E-mail address for publishing extensions is wrong

[Matthias Seidel]

Hello All,

FYI:

While I can publish the extension page, the downloadable files are
(again) not to be found in the SourceForge database.

Apart from that, we need a working mail address for users to contact us.

Regards,

   Matthias


 Weitergeleitete Nachricht 
Betreff:E-mail address for publishing extensions is wrong
Datum:  Thu, 9 Mar 2023 17:24:20 +0100
Von:Bogdan 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Hello.

After I created my extension, I wanted to publish it, but instead I saw
the message:

"
This extension is currently not published. Please contact the system
administrator at nore...@extensions.openoffice.org to have it published,
including a link to this page.
"

What would be the actual address to write to? Because it isn't
"noreply", right?

The extension is: https://extensions.openoffice.org/en/project/keyparastocx

Thank you!

-- 
Regards - Bogdan ('bogdro') D. (GNU/Linux & FreeDOS)
X86 assembly (DOS, GNU/Linux):http://bogdro.evai.pl/index-en.php
Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org

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



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: Upgraded: grep 3.9

[Matthias Seidel]

FYI


 Weitergeleitete Nachricht 
Betreff:Upgraded: grep 3.9
Datum:  Mon, 06 Mar 2023 14:32:55 -0700
Von:Cygwin grep Co-Maintainer via Cygwin-announce

Antwort an: Cygwin 
An: Cygwin Announcements 
Kopie (CC): Cygwin grep Co-Maintainer 



The following package has been upgraded in the Cygwin distribution:

* grep 3.9

GNU grep searches one or more input files for lines containing a match
to a specified pattern. By default, grep outputs the matching lines. The
GNU implementation includes several useful extensions over POSIX.

The previous release stated that egrep and fgrep are deprecated
obsolescent commands, will be dropped in future, and from this release
until then, every use will show a stderr warning message, reminding you
how to change your commands and scripts:

$ egrep ...
egrep: warning: egrep is obsolescent; using grep -E
...
$ fgrep ...
fgrep: warning: fgrep is obsolescent; using grep -F
...

Cygwin releases will suppress the egrep and fgrep warning messages, but
developers and maintainers should rigorously remove all such usages from
their practices and scripts, as those commands could be dropped, or any
warning messages could be treated as fatal errors, in future.

Other invalid usages documented previously also now generate stderr
warning or error messages e.g.

grep: warning: * at start of expression
grep: warning: ? at start of expression
grep: warning: + at start of expression
grep: warning: {...} at start of expression
grep: warning: stray \ before 
grep: warning: stray \ before unprintable character
grep: warning: stray \ before white space

For more information see the project home pages:

https://www.gnu.org/software/grep/
https://sv.gnu.org/projects/grep/

For changes since the previous Cygwin release please see below or read
/usr/share/doc/grep/NEWS after installation; for complete details see:

/usr/share/doc/grep/ChangeLog
https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.9


Noteworthy changes in release 3.9 (2023-03-05) [stable]

* Bug fixes

With -P, some non-ASCII UTF8 characters were not recognized as
word-constituent due to our omission of the PCRE2_UCP flag. E.g.,
given f(){ echo Perú|LC_ALL=en_US.UTF-8 grep -Po "$1"; } and
this command, echo $(f 'r\w'):$(f '.\b'), before it would print ":r".
After the fix, it prints the correct results: "rú:ú".

When given multiple patterns the last of which has a back-reference,
grep no longer sometimes mistakenly matches lines in some cases.
[Bug#36148#13 introduced in grep 3.4]



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Updated: make-4.4.1-1 & -2

[Arrigo Marchiori]

Hello Matthias,

On Thu, Mar 02, 2023 at 05:43:22PM +0100, Matthias Seidel wrote:

> Hi All,
> 
> Can anyone test if we can build with the updated make on Windows?
> 
> I don't want to risk it! If not there is no way back... ;-)

We seem to have the same problems with GNU Make 4.4.1 as with GNU Make
4.4.

I'll discuss my proposed fix in the other thread.

Best regards,
-- 
Arrigo

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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.14 released

[Matthias Seidel]

Hi Pedro,

Am 02.03.23 um 23:26 schrieb Pedro Lino:
> Hi Matthias
>
>> On 03/01/2023 7:12 PM WET Matthias Seidel  wrote:
>> First AOO4115 Test Builds for Windows can be found here:
>>
>> https://home.apache.org/~mseidel/AOO-builds/AOO-4115-Test/
> Anything in particular to test compared to 4.1.14?

You can see the changes here:

https://github.com/apache/openoffice/compare/AOO4114-GA...AOO41X

Standard commits and some cherry-picks.

But it is open for everyone! ;-)

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.14 released

[Pedro Lino]

Hi Matthias

> On 03/01/2023 7:12 PM WET Matthias Seidel  wrote:

> First AOO4115 Test Builds for Windows can be found here:
> 
> https://home.apache.org/~mseidel/AOO-builds/AOO-4115-Test/

Anything in particular to test compared to 4.1.14?

Best,
Pedro

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

Fwd: Updated: make-4.4.1-1 & -2

[Matthias Seidel]

Hi All,

Can anyone test if we can build with the updated make on Windows?

I don't want to risk it! If not there is no way back... ;-)

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:Updated: make-4.4.1-1 & -2
Datum:  Thu, 2 Mar 2023 07:40:07 +0100
Von:Marco Atzeri via Cygwin-announce 
Antwort an: Marco Atzeri 
An: cygwin-annou...@cygwin.com



Versions 4.4.1-1 (default) and 4.4.1-2 (test) of

make

are available in the Cygwin distribution

CYGWIN_CHANGES
The default version is built with jobserver using FIFO and
the test version using pipe.
In same complex corner case the previous 4.4-1 was reported to
fail and it is unclear if the pipe version is the solution
or just a side coincidence.
Please report any problem on any version.

DESCRIPTION
A GNU tool for controlling the generation of executables and other
non-source files of a program from the program's source files. Make
allows users to build and install packages without any significant
knowledge about the details of the build process. The details about
how the program should be built are provided for make in the program's
makefile.

CHANGES
Updated to the last upstream main release.
Full details on:
https://lists.gnu.org/archive/html/bug-make/2023-02/msg00127.html

HOMEPAGE
http://www.gnu.org/software/make/

Regards
Marco Atzeri

If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.14 released

[Matthias Seidel]

Hi All,

Thanks to everyone involved in this release!

Time to work on the next release. AOO41X and AOO42X are open for
commits, whatever comes first! ;-)

First AOO4115 Test Builds for Windows can be found here:

https://home.apache.org/~mseidel/AOO-builds/AOO-4115-Test/

Regards,

   Matthias

Am 27.02.23 um 21:38 schrieb Carl Marcum:
> Hello OpenOffice community.
>
> We want to thank everyone who helped make this release happen.
>
> Best regards,
> Carl
> (on behalf of the OpenOffice PMC)
>
> 
>
> 27 February 2023 - The Apache OpenOffice project is pleased to
> announce the release of Apache OpenOffice 4.1.14.
>
> Apache OpenOffice is a popular Open Source office document
> productivity suite available in 41 languages on Windows, macOS and Linux.
>
> Apache OpenOffice 4.1.14 is a maintenance release incorporating bug
> fixes and other enhancements.
>
> This release also includes the latest dictionaries.  All users of
> Apache OpenOffice 4.1.13 or earlier are advised to upgrade.
>
> For the complete overview see the list in Bugzilla:
> https://s.apache.org/AOO-4114changes
>
> Full version of this announcement:
> https://s.apache.org/AOO-4114announcement
>
> Apache OpenOffice 4.1.14 Release Notes:
> https://s.apache.org/AOO-4114releasenotes
>
> Download the source:
> https://openoffice.apache.org/downloads.html
>
> Download Apache OpenOffice 4.1.14 from the original source only:
> https://www.openoffice.org/download/
>
> Follow Apache OpenOffice:
> Twitter   https://twitter.com/apacheoo
> Facebook  https://www.facebook.com/ApacheOO
> YouTube   https://www.youtube.com/openoffice
> Mail  https://openoffice.apache.org/mailing-lists.html
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.14 released

[Carl Marcum]

Hello OpenOffice community.

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the OpenOffice PMC)



27 February 2023 - The Apache OpenOffice project is pleased to announce 
the release of Apache OpenOffice 4.1.14.


Apache OpenOffice is a popular Open Source office document productivity 
suite available in 41 languages on Windows, macOS and Linux.


Apache OpenOffice 4.1.14 is a maintenance release incorporating bug 
fixes and other enhancements.


This release also includes the latest dictionaries.  All users of Apache 
OpenOffice 4.1.13 or earlier are advised to upgrade.


For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4114changes

Full version of this announcement:
https://s.apache.org/AOO-4114announcement

Apache OpenOffice 4.1.14 Release Notes:
https://s.apache.org/AOO-4114releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.14 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html



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

Re: Fwd: Logo proposal

[Pedro Lino]

Hi Manjiro5
 
Thank you for your interest and contribution to the OpenOffice project.
 
Unfortunately this mailing list does not support embedded or attached images.
Can you please host these images or an archive and send the link?
 
Thank you in advance!
 
All the best,
Pedro
 

> On 01/15/2023 5:39 PM WET Xavier Verbrèghe  
> wrote:
>  
>  
>  
> 
> -- Forwarded message -
> De : CORENTIN VERBREGHE  mailto:corentin.verbreg...@gmail.com>
> Date: dim. 15 janv. 2023 à 18:35
> Subject: Logo proposal
> To: dev@openoffice.apache.org mailto:dev@openoffice.apache.org 
> mailto:dev@openoffice.apache.org>
> 
> 
> 
>  
> 
> Hello, I wish change the logos of Apache OpenOffice softwares because I think 
> that they are is no longer up to date. I wish OpenOffice looked as modern as 
> LibreOffice. Could you look at my proposals? Hoping that you like them and 
> that they are updated. If you have any comments tell me, I really would like 
> AOO to have its old glow.
> 
>  
> 
> Cordially.
> 
> Manjiro5
> 

Fwd: Logo proposal

[Xavier Verbrèghe]

-- Forwarded message -
De : CORENTIN VERBREGHE 
Date: dim. 15 janv. 2023 à 18:35
Subject: Logo proposal
To: dev@openoffice.apache.org 




Hello, I wish change the logos of Apache OpenOffice softwares because I
think that they are is no longer up to date. I wish OpenOffice looked as
modern as LibreOffice. Could you look at my proposals? Hoping that you like
them and that they are updated. If you have any comments tell me, I really
would like AOO to have its old glow.



Cordially.

Manjiro5

Re: Fwd: Bug in Calc - Search and Substitute.

[Peter Kovacs]

hello Mauro,

Am 04.01.23 um 16:11 schrieb Mauro (GMail):

Hallo Peter,
I'm sorry you didn't see my problem... it's very unpleasant!

makes it more difficult to hunt the issue.

And I've seen it from a lot of version.
😊

Sorry, I forgot the AOO version, so I add the graphic card too.
- PC: HP Working Station ZBook with Intel HD Graphics 530 and his 
monitor 1600x900.

- OS: Win10.
- Monitor 2: Extension Philips 272B connected to NVidia Quadro M1000M.
- AOO 4.1.13, but my problem is present from a lot of version, I don't 
know from when.

What about Java?


Thank you and best regards,


you are welcome

peter


Mauro.


Peter Kovacs ha scritto il 02/01/2023 alle 22:37:


Hi all,

I tested the report today.

My system differs slightly.

I tested with

- AOO 4.1.12

- win 11

- 2x ASUS screens with AMD GPU

- OpenJDK is installed


I have no issues.

@mauro

What Version of AOO do you use?

Do you have Java 32bit installed?


All the best

Peter

Am 28.12.22 um 14:30 schrieb Matthias Seidel:


Hi all,

FYI

Can anyone confirm/test?

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff: Bug in Calc - Search and Substitute.
Datum: Wed, 28 Dec 2022 11:50:18 +0100
Von: Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
   - Monitor 1: HP Working Station ZBook
   - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
 The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.
😉

Hope to help you, best regards,
Mauro Francioni.

Bologna - Italia.




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

Re: Fwd: Bug in Calc - Search and Substitute.

[Mauro (GMail)]

Hallo Peter,
I'm sorry you didn't see my problem... it's very unpleasant!
And I've seen it from a lot of version.
😊

Sorry, I forgot the AOO version, so I add the graphic card too.
- PC: HP Working Station ZBook with Intel HD Graphics 530 and his 
monitor 1600x900.

- OS: Win10.
- Monitor 2: Extension Philips 272B connected to NVidia Quadro M1000M.
- AOO 4.1.13, but my problem is present from a lot of version, I don't 
know from when.


Thank you and best regards,
Mauro.


Peter Kovacs ha scritto il 02/01/2023 alle 22:37:


Hi all,

I tested the report today.

My system differs slightly.

I tested with

- AOO 4.1.12

- win 11

- 2x ASUS screens with AMD GPU

- OpenJDK is installed


I have no issues.

@mauro

What Version of AOO do you use?

Do you have Java 32bit installed?


All the best

Peter

Am 28.12.22 um 14:30 schrieb Matthias Seidel:


Hi all,

FYI

Can anyone confirm/test?

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:Bug in Calc - Search and Substitute.
Datum:  Wed, 28 Dec 2022 11:50:18 +0100
Von:Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
   - Monitor 1: HP Working Station ZBook
   - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
 The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.
😉

Hope to help you, best regards,
Mauro Francioni.

Bologna - Italia.

Re: Fwd: Bug in Calc - Search and Substitute.

[Peter Kovacs]

Hi all,

I tested the report today.

My system differs slightly.

I tested with

- AOO 4.1.12

- win 11

- 2x ASUS screens with AMD GPU

- OpenJDK is installed


I have no issues.

@mauro

What Version of AOO do you use?

Do you have Java 32bit installed?


All the best

Peter

Am 28.12.22 um 14:30 schrieb Matthias Seidel:


Hi all,

FYI

Can anyone confirm/test?

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:Bug in Calc - Search and Substitute.
Datum:  Wed, 28 Dec 2022 11:50:18 +0100
Von:Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
   - Monitor 1: HP Working Station ZBook
   - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
 The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.
😉

Hope to help you, best regards,
Mauro Francioni.

Bologna - Italia.

Re: Fwd: Bug in Calc - Search and Substitute.

[Marcus]

Am 30.12.22 um 19:10 schrieb Peter Kovacs:

Am 30.12.22 um 19:00 schrieb Marcus:

Am 28.12.22 um 14:30 schrieb Matthias Seidel:

FYI
Can anyone confirm/test?


maybe a Linux-only issue. On my Linux system with 2 monitors no dialog 
boxes or document windows will disappear.


Do you mean Windows?

I can test Windows in the next days. I have 2 Monitors. I just was not 
at home the past days.


yes, the original reporter is working on Windows 10.

Marcus




 Weitergeleitete Nachricht 
Betreff: Bug in Calc - Search and Substitute.
Datum: Wed, 28 Dec 2022 11:50:18 +0100
Von: Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
    - Monitor 1: HP Working Station ZBook
    - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
  The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.



-
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



--

Ciao

Marcus


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

Re: Fwd: Bug in Calc - Search and Substitute.

[Peter Kovacs]

Am 30.12.22 um 19:00 schrieb Marcus:

Am 28.12.22 um 14:30 schrieb Matthias Seidel:

FYI
Can anyone confirm/test?


maybe a Linux-only issue. On my Linux system with 2 monitors no dialog 
boxes or document windows will disappear.


Do you mean Windows?

I can test Windows in the next days. I have 2 Monitors. I just was not 
at home the past days.




Marcus




 Weitergeleitete Nachricht 
Betreff: Bug in Calc - Search and Substitute.
Datum: Wed, 28 Dec 2022 11:50:18 +0100
Von: Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
    - Monitor 1: HP Working Station ZBook
    - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
  The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.



-
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

Re: Fwd: Bug in Calc - Search and Substitute.

[Marcus]

Am 28.12.22 um 14:30 schrieb Matthias Seidel:

FYI
Can anyone confirm/test?


maybe a Linux-only issue. On my Linux system with 2 monitors no dialog 
boxes or document windows will disappear.


Marcus




 Weitergeleitete Nachricht 
Betreff:Bug in Calc - Search and Substitute.
Datum:  Wed, 28 Dec 2022 11:50:18 +0100
Von:Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
    - Monitor 1: HP Working Station ZBook
    - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
  The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.



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

Fwd: Bug in Calc - Search and Substitute.

[Matthias Seidel]

Hi all,

FYI

Can anyone confirm/test?

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:Bug in Calc - Search and Substitute.
Datum:  Wed, 28 Dec 2022 11:50:18 +0100
Von:Mauro (GMail) 
Antwort an: us...@openoffice.apache.org
An: us...@openoffice.apache.org



Good morning,
I'd like to evidence a bug in Calc.

The base system information are:
- PC: HP Working Station ZBook
- OS: Win10.
- Monitor:
   - Monitor 1: HP Working Station ZBook
   - Monitor 2: Extension Philips 272B

The conditions are:
1) _Use Calc in monitor 2_.
2) Press Ctrl-F to open the Search and Substitute Box.
_Leave the Search and Substitute Box on Monitor 1._
3) Click on More Option Button.
 The Search and Substitute Box disappear, it's no more visible.

The only system to view again the Search and Substitute Box is:
- disconnect the Monitor 2
- open the Search and Substitute Box again.

This bug is present for a long time now and very old version.
😉

Hope to help you, best regards,
Mauro Francioni.

Bologna - Italia.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Cygwin x86 end-of-life

[Matthias Seidel]

I will continue to build AOO41X with my installed Cygwin32. If it ever
breaks on my VM, I will *not* repair it.

Damjan posted the needed patches to build AOO41X with Cygwin64, if
anyone wants to commit them...

Regards,

   Matthias

Am 11.11.22 um 18:39 schrieb Matthias Seidel:
> Hi Pedro,
>
> Am 11.11.22 um 18:15 schrieb Pedro Lino:
>> Hi Matthias
>>  
>> If I understand correctly this will still allow to build x86 binaries for 
>> the Windows OS, right?
> For AOO41X we are somehow stuck with Cygwin32. So it will allow us to
> build but it will not get updates anymore.
>
>> It would only be a problem if our builds had to be compiled in a x86 OS?
> Basically this isn't a problem since beginning with AOO42X we build our
> x86 binaries with Cygwin64.
>
> But we should *really* try to get AOO 4.2.0 out. Not only for this
> reason. ;-)
>
> Regards,
>
>    Matthias
>
>>  
>> Regards,
>> Pedro
>>
>>> On 11/11/2022 4:26 PM WET Matthias Seidel  
>>> wrote:
>>>  
>>>  
>>>
>>> Hi all,
>>>
>>> FYI, long announced.
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>>>
>>>  Weitergeleitete Nachricht 
>>> Betreff:Cygwin x86 end-of-life
>>> Datum:  Fri, 11 Nov 2022 15:50:33 +
>>> Von:Jon Turney  
>>> mailto:jon.tur...@dronecode.org.uk
>>> An: cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
>>>
>>>
>>>
>>> As has previously been announced, Cygwin is dropping support for x86 
>>> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit) Windows, 
>>> and the forthcoming Cygwin 3.4 will be released for x86_64 only.
>>>
>>> Concurrent with that, updates to x86 packages will be stopped, and the 
>>> Cygwin x86 package repository will be archived.
>>>
>>> (Instructions on the special steps needed to install from that archive will 
>>> be forthcoming, once we've worked out what they are.)
>>>
>>> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please 
>>> strongly consider moving to an x86_64 Cygwin installation.
>>>
>>> (If you have ARM hardware, we believe that x86_64 Cygwin works correctly 
>>> using the x86_64 emulation in Windows 11)
>>>
>>> If you're one of the tiny percentage of Cygwin users using x86 Cygwin on a 
>>> real x86 Windows OS, don't panic! The current installation will continue to 
>>> run on your system. You just won't get any more updates.
>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: Cygwin x86 end-of-life

[Matthias Seidel]

FYI



 Weitergeleitete Nachricht 
Betreff:Re: Cygwin x86 end-of-life
Datum:  Fri, 25 Nov 2022 18:45:16 +
Von:Jon Turney 
An: cygwin-annou...@cygwin.com



On 11/11/2022 15:50, Jon Turney wrote:
>
> As has previously been announced, Cygwin is dropping support for x86
> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit)
> Windows, and the forthcoming Cygwin 3.4 will be released for x86_64 only.
>
> Concurrent with that, updates to x86 packages will be stopped, and the
> Cygwin x86 package repository will be archived.
>
> (Instructions on the special steps needed to install from that archive
> will be forthcoming, once we've worked out what they are.)

To install the last cygwin version for x86, run setup using the options
'--allow-unsupported-windows option --site circa_URL', where circa_URL
can be one of:

* The URL for any sourceware mirror[1], followed by cygwin-archive/20221123

*
http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/2022/11/23/063457

Thanks to the Cygwin Time Machine for providing this archive.

These instructions have also been added at [2]

[1] Note that not all cygwin mirrors [3] also carry a full mirror of
sourceware (but the list at [4] is believed to be sadly incomplete)
[2] https://cygwin.com/install.html#unsupported
[3] https://cygwin.com/mirrors.html
[4] https://sourceware.org/mirrors.html

> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please
> strongly consider moving to an x86_64 Cygwin installation.
>
> (If you have ARM hardware, we believe that x86_64 Cygwin works
> correctly using the x86_64 emulation in Windows 11)
>
> If you're one of the tiny percentage of Cygwin users using x86 Cygwin
> on a real x86 Windows OS, don't panic! The current installation will
> continue to run on your system. You just won't get any more updates.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Cygwin x86 end-of-life

[Matthias Seidel]

Hi Pedro,

Am 11.11.22 um 18:15 schrieb Pedro Lino:
> Hi Matthias
>  
> If I understand correctly this will still allow to build x86 binaries for the 
> Windows OS, right?

For AOO41X we are somehow stuck with Cygwin32. So it will allow us to
build but it will not get updates anymore.

> It would only be a problem if our builds had to be compiled in a x86 OS?

Basically this isn't a problem since beginning with AOO42X we build our
x86 binaries with Cygwin64.

But we should *really* try to get AOO 4.2.0 out. Not only for this
reason. ;-)

Regards,

   Matthias

>  
> Regards,
> Pedro
>
>> On 11/11/2022 4:26 PM WET Matthias Seidel  wrote:
>>  
>>  
>>
>> Hi all,
>>
>> FYI, long announced.
>>
>> Regards,
>>
>>Matthias
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: Cygwin x86 end-of-life
>> Datum:   Fri, 11 Nov 2022 15:50:33 +
>> Von: Jon Turney  
>> mailto:jon.tur...@dronecode.org.uk
>> An:  cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
>>
>>
>>
>> As has previously been announced, Cygwin is dropping support for x86 
>> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit) Windows, 
>> and the forthcoming Cygwin 3.4 will be released for x86_64 only.
>>
>> Concurrent with that, updates to x86 packages will be stopped, and the 
>> Cygwin x86 package repository will be archived.
>>
>> (Instructions on the special steps needed to install from that archive will 
>> be forthcoming, once we've worked out what they are.)
>>
>> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please 
>> strongly consider moving to an x86_64 Cygwin installation.
>>
>> (If you have ARM hardware, we believe that x86_64 Cygwin works correctly 
>> using the x86_64 emulation in Windows 11)
>>
>> If you're one of the tiny percentage of Cygwin users using x86 Cygwin on a 
>> real x86 Windows OS, don't panic! The current installation will continue to 
>> run on your system. You just won't get any more updates.
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Cygwin x86 end-of-life

[Pedro Lino]

Hi Matthias
 
If I understand correctly this will still allow to build x86 binaries for the 
Windows OS, right?
It would only be a problem if our builds had to be compiled in a x86 OS?
 
Regards,
Pedro

> On 11/11/2022 4:26 PM WET Matthias Seidel  wrote:
>  
>  
> 
> Hi all,
> 
> FYI, long announced.
> 
> Regards,
> 
>Matthias
> 
> 
>  Weitergeleitete Nachricht 
> Betreff:  Cygwin x86 end-of-life
> Datum:Fri, 11 Nov 2022 15:50:33 +
> Von:  Jon Turney  
> mailto:jon.tur...@dronecode.org.uk
> An:   cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
> 
> 
> 
> As has previously been announced, Cygwin is dropping support for x86 Windows. 
> Cygwin 3.3.6 is the final version supporting x86 (32-bit) Windows, and the 
> forthcoming Cygwin 3.4 will be released for x86_64 only.
> 
> Concurrent with that, updates to x86 packages will be stopped, and the Cygwin 
> x86 package repository will be archived.
> 
> (Instructions on the special steps needed to install from that archive will 
> be forthcoming, once we've worked out what they are.)
> 
> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please 
> strongly consider moving to an x86_64 Cygwin installation.
> 
> (If you have ARM hardware, we believe that x86_64 Cygwin works correctly 
> using the x86_64 emulation in Windows 11)
> 
> If you're one of the tiny percentage of Cygwin users using x86 Cygwin on a 
> real x86 Windows OS, don't panic! The current installation will continue to 
> run on your system. You just won't get any more updates.
> 

Fwd: Cygwin x86 end-of-life

[Matthias Seidel]

Hi all,

FYI, long announced.

Regards,

   Matthias


 Weitergeleitete Nachricht 
Betreff:Cygwin x86 end-of-life
Datum:  Fri, 11 Nov 2022 15:50:33 +
Von:Jon Turney 
An: cygwin-annou...@cygwin.com




As has previously been announced, Cygwin is dropping support for x86
Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit)
Windows, and the forthcoming Cygwin 3.4 will be released for x86_64 only.

Concurrent with that, updates to x86 packages will be stopped, and the
Cygwin x86 package repository will be archived.

(Instructions on the special steps needed to install from that archive
will be forthcoming, once we've worked out what they are.)

If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please
strongly consider moving to an x86_64 Cygwin installation.

(If you have ARM hardware, we believe that x86_64 Cygwin works correctly
using the x86_64 emulation in Windows 11)

If you're one of the tiny percentage of Cygwin users using x86 Cygwin on
a real x86 Windows OS, don't panic! The current installation will
continue to run on your system. You just won't get any more updates.


smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: Native speaker/developer

[Peter Kovacs]

sorry forgot to fix email address



 Weitergeleitete Nachricht 
Betreff:Re: Native speaker/developer
Datum:  Thu, 3 Nov 2022 06:49:27 +0100
Von:Peter Kovacs 
Antwort an: dev@openoffice.apache.org
Organisation:   Apache Foundation
An: 	dev@openoffice.apache.org, Robi Brutoczki 





Szia Robi,

As Biduille said, everyone who helps is welcome.

The state of Hungarian translation you can check at [1]

For contributing you need an account. Request it on 
l...@openoffice.apache.org


Just mention your your preferred nickname and email.

Our web pages are static webpages. For changing them all you need is a 
GitHub account. You can send PR for the web/documentation repos. see [2] 
and [3]


Maybe check with documentation team on d...@openoffice.apache.org

On web we have following developer needs:

# we need to fix stuff on Mwiki (PHP)

# we need to migrate translation tool

# Forum maintenance? (Dave can say something, this is only a guess on my 
part)


# updating opengrok

# migrating our services to docker

If you are interested in those top just confirm. I guide you. Here we 
don't have a workflow yet.


[1] https://translate.apache.org/hu/aoo40/

[2] https://github.com/apache/openoffice-org

[3] https://github.com/apache/openoffice-docs


Am 31.10.22 um 11:15 schrieb Robi Brutoczki:

Hello
This is Rob , I'm a native Hungarian speaker and a Junior
full-stack developer.
Please let me know if you need me to help with Hungarian or if you could
use a Junior.
Thank you



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

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.13 released

[Carl Marcum]

Hello OpenOffice community.

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the OpenOffice PMC)



22 July 2022 - The Apache OpenOffice project is pleased to announce the 
release of Apache OpenOffice 4.1.13.


Apache OpenOffice is a popular Open Source office document productivity 
suite available in 41 languages on Windows, macOS and Linux.


Apache OpenOffice 4.1.13 is a Security release incorporating bug fixes 
and other enhancements.


This release also includes the latest dictionaries.  All users of Apache 
OpenOffice 4.1.12 or earlier are advised to upgrade.


For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4113changes

Full version of this announcement:
https://s.apache.org/AOO-4113announcement

Apache OpenOffice 4.1.13 Release Notes:
https://s.apache.org/AOO-4113releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.13 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html



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

Fwd: [Issue 114497] Mail Merge E-Mail: "Find outgoing mail server Fail" with particular mail servers

[Bidouille]

Some Mac users can test the mailmerge.py and try to connect on SMTP.
I tried to do it with the VM McStadium but unsuccessful. 

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

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.12 released

[Carl Marcum]

Hello OpenOffice community.

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the OpenOffice PMC)


 Forwarded Message 
Subject:[ANNOUNCE] Apache OpenOffice 4.1.12 released
Date:   Wed, 4 May 2022 18:24:00 -0400
From:   Carl Marcum 
Organization:   Apache Software Foundation
To: annou...@openoffice.apache.org



04 May 2022 - The Apache OpenOffice project is pleased to announce the 
release of Apache OpenOffice 4.1.12.


This release is dedicated to Jörg Schmidt, who was a valued contributor 
to the project and suddenly passed away at the end of last year.


Apache OpenOffice is a popular Open Source office document productivity 
suite available in 41 languages on Windows, macOS and Linux.


Apache OpenOffice 4.1.12 is a maintenance release incorporating bug 
fixes and other enhancements.


This release also includes the latest dictionaries.  All users of Apache 
OpenOffice 4.1.11 or earlier are advised to upgrade.


For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4112changes

Full version of this announcement:
https://s.apache.org/AOO-4112announcement

Apache OpenOffice 4.1.12 Release Notes:
https://s.apache.org/AOO-4112releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.12 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html


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

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi Arrigo,

Am 30.10.21 um 15:22 schrieb Arrigo Marchiori:
> Hello Matthias, All,
>
>
> On Fri, Oct 29, 2021 at 09:05:52PM +0200, Matthias Seidel wrote:
>
>> Hi Arrigo,
>>
>> Am 28.10.21 um 22:11 schrieb Arrigo Marchiori:
>>> Hello Matthias, All,
>>>
>>> On Thu, Oct 28, 2021 at 09:13:05PM +0200, Matthias Seidel wrote:
>>>
 Hi all,

 one positive effect of Cygwin 3.3.0 seems to be that I can build with
 threads again!
>>> That would be _very_ good!
>> Indeed!
> And I confirm that I can build AOO41X with as many threads as I want! :-)

Great!

Then my next AOO41X Test Build will be with the latest Cygwin.

AOO42X is already there:

https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/

>
 That saves me a lot of hours. I am building AOO42X right now...

 @Arrigo: Can you try AOO41X?
>>> Only tomorrow evening... sorry.
>> No hurry, we are already at Cygwin 3.3.1. ;-)
> Well, I updated the whole Cygwin distribution in fact; I am using
> 3.3.1-1. As I wrote above, it is working well.
>
> Only caveat: as gawk gets updated, I had to reinstall /usr/bin/awk as
> a copy instead of a symlink. AOO's configure script promptly pointed
> out the problem.

Yes, I did that just yesterday. Once in a while gawk gets updated... ;-)

Regards,

   Matthias

>
> Best regards,



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Arrigo Marchiori]

Hello Matthias, All,


On Fri, Oct 29, 2021 at 09:05:52PM +0200, Matthias Seidel wrote:

> Hi Arrigo,
> 
> Am 28.10.21 um 22:11 schrieb Arrigo Marchiori:
> > Hello Matthias, All,
> >
> > On Thu, Oct 28, 2021 at 09:13:05PM +0200, Matthias Seidel wrote:
> >
> >> Hi all,
> >>
> >> one positive effect of Cygwin 3.3.0 seems to be that I can build with
> >> threads again!
> > That would be _very_ good!
> Indeed!

And I confirm that I can build AOO41X with as many threads as I want! :-)

> >> That saves me a lot of hours. I am building AOO42X right now...
> >>
> >> @Arrigo: Can you try AOO41X?
> > Only tomorrow evening... sorry.
> 
> No hurry, we are already at Cygwin 3.3.1. ;-)

Well, I updated the whole Cygwin distribution in fact; I am using
3.3.1-1. As I wrote above, it is working well.

Only caveat: as gawk gets updated, I had to reinstall /usr/bin/awk as
a copy instead of a symlink. AOO's configure script promptly pointed
out the problem.

Best regards,
-- 
Arrigo

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

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi Arrigo,

Am 28.10.21 um 22:11 schrieb Arrigo Marchiori:
> Hello Matthias, All,
>
> On Thu, Oct 28, 2021 at 09:13:05PM +0200, Matthias Seidel wrote:
>
>> Hi all,
>>
>> one positive effect of Cygwin 3.3.0 seems to be that I can build with
>> threads again!
> That would be _very_ good!
Indeed!
>
>> That saves me a lot of hours. I am building AOO42X right now...
>>
>> @Arrigo: Can you try AOO41X?
> Only tomorrow evening... sorry.

No hurry, we are already at Cygwin 3.3.1. ;-)

Regards,

   Matthias

>
> Best regards,



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Arrigo Marchiori]

Hello Matthias, All,

On Thu, Oct 28, 2021 at 09:13:05PM +0200, Matthias Seidel wrote:

> Hi all,
> 
> one positive effect of Cygwin 3.3.0 seems to be that I can build with
> threads again!

That would be _very_ good!

> That saves me a lot of hours. I am building AOO42X right now...
> 
> @Arrigo: Can you try AOO41X?

Only tomorrow evening... sorry.

Best regards,
-- 
Arrigo

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

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi all,

one positive effect of Cygwin 3.3.0 seems to be that I can build with
threads again!

That saves me a lot of hours. I am building AOO42X right now...

@Arrigo: Can you try AOO41X?

Regards,

   Matthias

Am 28.10.21 um 15:24 schrieb Matthias Seidel:
> Hi Pedro,
>
> Am 28.10.21 um 15:06 schrieb Pedro Lino:
>> Hi Matthias
>>
>> Not wanting to disregard Damjan's effort, wouldn't it be better if people 
>> who can fix issues would focus on 4.2.x?
> Of course that would be better, but then we should start to fix the
> years old release blocker.
>
> I am +1 for releasing 4.2.0 when it is ready.
>
>> I assume Cygwin 3.3.0 will be supported for some time, so we should use that 
>> time to focus on 4.2.x?
> It will be the last version supported for 32-bit. Of course we can build
> as along as it breaks... ;-)
>
> Regards,
>
>    Matthias
>
>> Regards,
>> Pedro
>>
>>> On 10/28/2021 1:57 PM Matthias Seidel  wrote:
>>>
>>>  
>>> Hi all,
>>>
>>> Cygwin 3.3.0 will be available soon and it will be the last 32-bit
>>> version we can build AOO41X with.
>>>
>>> I remember, that Damjan longer ago posted a list of commits to make
>>> AOO41X buildable with Cygwin64.
>>>
>>> Can we have a look at it?
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>> Am 27.10.21 um 18:25 schrieb Matthias Seidel:
 Hi Pedro,

 This is not about a 64-bit version of AOO but about building AOO with
 Cygwin 64-bit.

 AOO41x needs Cygwin32 at the moment, trunk/AOO42X are already built with
 Cygwin64.

 Regards,

    Matthias

 Am 27.10.21 um 18:16 schrieb Pedro Lino:
> Hi Matthias
>
> I agree. Providing 64-bit Windows binaries must be the #1 priority for 
> this Project (not because they are needed or better than the 32-bit 
> builds but because they will not be supported by the compilers or the OS)
> This will also solve the problem of having to suggest the installation of 
> a 32-bit Java (which is also becoming unsupported)
>
> Regards,
> Pedro
>
>
>> On 10/27/2021 4:25 PM Matthias Seidel  
>> wrote:
>>
>>
>>
>> Hi all,
>>
>> Looks like we need to get building AOO41X for Windows on Cygwin64 or 
>> get out AOO42X.
>>
>> Whatever comes first... ;-)
>>
>> Regards,
>>
>>Matthias
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: [HEADSUP] Phasing out old Windows versions and 32 bit 
>> support
>> Datum:   Wed, 27 Oct 2021 10:57:45 +0200
>> Von: Corinna Vinschen via Cygwin-announce 
>>  mailto:cygwin-annou...@cygwin.com
>> Antwort an:  cyg...@cygwin.com mailto:cyg...@cygwin.com
>> An:  cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
>> Kopie (CC):  Corinna Vinschen  
>> mailto:corinna-cyg...@cygwin.com
>>
>>
>> [I sent this announcement to the Cygwin mailing list accidentally.
>> Now sending it to cygwin-announce, too, to reach more people. Please
>> reply on the cygwin mailing list if you have any concerns or 
>> comments]
>>
>>
>> Hi folks,
>>
>>
>> The upcoming version 3.3.0 is the last version officially supporting
>> Windows Vista and Windows Server 2008.
>>
>> The next major release 3.4.0 will be released in 2022 and will be the
>> last one officially supporting Windows 7, Windows 8, Windows Server 
>> 2008
>> R2, and Windows Server 2012.
>>
>> We're also planning to drop Support for the 32 bit release of Cygwin 
>> in
>> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
>> maintainers won't have to update 32 bit packages anymore. If you're
>> still running Cygwin under WOW64, consider to move to 64 bit in the 
>> next
>> couple of months.
>>
>>
>> Corinna
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi Pedro,

Am 28.10.21 um 15:06 schrieb Pedro Lino:
> Hi Matthias
>
> Not wanting to disregard Damjan's effort, wouldn't it be better if people who 
> can fix issues would focus on 4.2.x?

Of course that would be better, but then we should start to fix the
years old release blocker.

I am +1 for releasing 4.2.0 when it is ready.

>
> I assume Cygwin 3.3.0 will be supported for some time, so we should use that 
> time to focus on 4.2.x?

It will be the last version supported for 32-bit. Of course we can build
as along as it breaks... ;-)

Regards,

   Matthias

>
> Regards,
> Pedro
>
>> On 10/28/2021 1:57 PM Matthias Seidel  wrote:
>>
>>  
>> Hi all,
>>
>> Cygwin 3.3.0 will be available soon and it will be the last 32-bit
>> version we can build AOO41X with.
>>
>> I remember, that Damjan longer ago posted a list of commits to make
>> AOO41X buildable with Cygwin64.
>>
>> Can we have a look at it?
>>
>> Regards,
>>
>>    Matthias
>>
>> Am 27.10.21 um 18:25 schrieb Matthias Seidel:
>>> Hi Pedro,
>>>
>>> This is not about a 64-bit version of AOO but about building AOO with
>>> Cygwin 64-bit.
>>>
>>> AOO41x needs Cygwin32 at the moment, trunk/AOO42X are already built with
>>> Cygwin64.
>>>
>>> Regards,
>>>
>>>    Matthias
>>>
>>> Am 27.10.21 um 18:16 schrieb Pedro Lino:
 Hi Matthias

 I agree. Providing 64-bit Windows binaries must be the #1 priority for 
 this Project (not because they are needed or better than the 32-bit builds 
 but because they will not be supported by the compilers or the OS)
 This will also solve the problem of having to suggest the installation of 
 a 32-bit Java (which is also becoming unsupported)

 Regards,
 Pedro


> On 10/27/2021 4:25 PM Matthias Seidel  
> wrote:
>
>
>
> Hi all,
>
> Looks like we need to get building AOO41X for Windows on Cygwin64 or 
> get out AOO42X.
>
> Whatever comes first... ;-)
>
> Regards,
>
>Matthias
>
>
>
>  Weitergeleitete Nachricht 
> Betreff:  [HEADSUP] Phasing out old Windows versions and 32 bit 
> support
> Datum:Wed, 27 Oct 2021 10:57:45 +0200
> Von:  Corinna Vinschen via Cygwin-announce 
>  mailto:cygwin-annou...@cygwin.com
> Antwort an:   cyg...@cygwin.com mailto:cyg...@cygwin.com
> An:   cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
> Kopie (CC):   Corinna Vinschen  
> mailto:corinna-cyg...@cygwin.com
>
>
> [I sent this announcement to the Cygwin mailing list accidentally.
> Now sending it to cygwin-announce, too, to reach more people. Please
> reply on the cygwin mailing list if you have any concerns or comments]
>
>
> Hi folks,
>
>
> The upcoming version 3.3.0 is the last version officially supporting
> Windows Vista and Windows Server 2008.
>
> The next major release 3.4.0 will be released in 2022 and will be the
> last one officially supporting Windows 7, Windows 8, Windows Server 
> 2008
> R2, and Windows Server 2012.
>
> We're also planning to drop Support for the 32 bit release of Cygwin 
> in
> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
> maintainers won't have to update 32 bit packages anymore. If you're
> still running Cygwin under WOW64, consider to move to 64 bit in the 
> next
> couple of months.
>
>
> Corinna
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Pedro Lino]

Hi Matthias

Not wanting to disregard Damjan's effort, wouldn't it be better if people who 
can fix issues would focus on 4.2.x?

I assume Cygwin 3.3.0 will be supported for some time, so we should use that 
time to focus on 4.2.x?

Regards,
Pedro

> On 10/28/2021 1:57 PM Matthias Seidel  wrote:
> 
>  
> Hi all,
> 
> Cygwin 3.3.0 will be available soon and it will be the last 32-bit
> version we can build AOO41X with.
> 
> I remember, that Damjan longer ago posted a list of commits to make
> AOO41X buildable with Cygwin64.
> 
> Can we have a look at it?
> 
> Regards,
> 
>    Matthias
> 
> Am 27.10.21 um 18:25 schrieb Matthias Seidel:
> > Hi Pedro,
> >
> > This is not about a 64-bit version of AOO but about building AOO with
> > Cygwin 64-bit.
> >
> > AOO41x needs Cygwin32 at the moment, trunk/AOO42X are already built with
> > Cygwin64.
> >
> > Regards,
> >
> >    Matthias
> >
> > Am 27.10.21 um 18:16 schrieb Pedro Lino:
> >> Hi Matthias
> >>
> >> I agree. Providing 64-bit Windows binaries must be the #1 priority for 
> >> this Project (not because they are needed or better than the 32-bit builds 
> >> but because they will not be supported by the compilers or the OS)
> >> This will also solve the problem of having to suggest the installation of 
> >> a 32-bit Java (which is also becoming unsupported)
> >>
> >> Regards,
> >> Pedro
> >>
> >>
> >>> On 10/27/2021 4:25 PM Matthias Seidel  
> >>> wrote:
> >>>
> >>>
> >>>
> >>> Hi all,
> >>>
> >>> Looks like we need to get building AOO41X for Windows on Cygwin64 or 
> >>> get out AOO42X.
> >>>
> >>> Whatever comes first... ;-)
> >>>
> >>> Regards,
> >>>
> >>>Matthias
> >>>
> >>>
> >>>
> >>>  Weitergeleitete Nachricht 
> >>> Betreff:  [HEADSUP] Phasing out old Windows versions and 32 bit 
> >>> support
> >>> Datum:Wed, 27 Oct 2021 10:57:45 +0200
> >>> Von:  Corinna Vinschen via Cygwin-announce 
> >>>  mailto:cygwin-annou...@cygwin.com
> >>> Antwort an:   cyg...@cygwin.com mailto:cyg...@cygwin.com
> >>> An:   cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
> >>> Kopie (CC):   Corinna Vinschen  
> >>> mailto:corinna-cyg...@cygwin.com
> >>>
> >>>
> >>> [I sent this announcement to the Cygwin mailing list accidentally.
> >>> Now sending it to cygwin-announce, too, to reach more people. Please
> >>> reply on the cygwin mailing list if you have any concerns or comments]
> >>>
> >>>
> >>> Hi folks,
> >>>
> >>>
> >>> The upcoming version 3.3.0 is the last version officially supporting
> >>> Windows Vista and Windows Server 2008.
> >>>
> >>> The next major release 3.4.0 will be released in 2022 and will be the
> >>> last one officially supporting Windows 7, Windows 8, Windows Server 
> >>> 2008
> >>> R2, and Windows Server 2012.
> >>>
> >>> We're also planning to drop Support for the 32 bit release of Cygwin 
> >>> in
> >>> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
> >>> maintainers won't have to update 32 bit packages anymore. If you're
> >>> still running Cygwin under WOW64, consider to move to 64 bit in the 
> >>> next
> >>> couple of months.
> >>>
> >>>
> >>> Corinna
> >>>

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

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi all,

Cygwin 3.3.0 will be available soon and it will be the last 32-bit
version we can build AOO41X with.

I remember, that Damjan longer ago posted a list of commits to make
AOO41X buildable with Cygwin64.

Can we have a look at it?

Regards,

   Matthias

Am 27.10.21 um 18:25 schrieb Matthias Seidel:
> Hi Pedro,
>
> This is not about a 64-bit version of AOO but about building AOO with
> Cygwin 64-bit.
>
> AOO41x needs Cygwin32 at the moment, trunk/AOO42X are already built with
> Cygwin64.
>
> Regards,
>
>    Matthias
>
> Am 27.10.21 um 18:16 schrieb Pedro Lino:
>> Hi Matthias
>>
>> I agree. Providing 64-bit Windows binaries must be the #1 priority for this 
>> Project (not because they are needed or better than the 32-bit builds but 
>> because they will not be supported by the compilers or the OS)
>> This will also solve the problem of having to suggest the installation of a 
>> 32-bit Java (which is also becoming unsupported)
>>
>> Regards,
>> Pedro
>>
>>
>>> On 10/27/2021 4:25 PM Matthias Seidel  
>>> wrote:
>>>
>>>
>>>
>>> Hi all,
>>>
>>> Looks like we need to get building AOO41X for Windows on Cygwin64 or 
>>> get out AOO42X.
>>>
>>> Whatever comes first... ;-)
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>>>
>>>
>>>  Weitergeleitete Nachricht 
>>> Betreff:[HEADSUP] Phasing out old Windows versions and 32 bit 
>>> support
>>> Datum:  Wed, 27 Oct 2021 10:57:45 +0200
>>> Von:Corinna Vinschen via Cygwin-announce 
>>>  mailto:cygwin-annou...@cygwin.com
>>> Antwort an: cyg...@cygwin.com mailto:cyg...@cygwin.com
>>> An: cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
>>> Kopie (CC): Corinna Vinschen  
>>> mailto:corinna-cyg...@cygwin.com
>>>
>>>
>>> [I sent this announcement to the Cygwin mailing list accidentally.
>>> Now sending it to cygwin-announce, too, to reach more people. Please
>>> reply on the cygwin mailing list if you have any concerns or comments]
>>>
>>>
>>> Hi folks,
>>>
>>>
>>> The upcoming version 3.3.0 is the last version officially supporting
>>> Windows Vista and Windows Server 2008.
>>>
>>> The next major release 3.4.0 will be released in 2022 and will be the
>>> last one officially supporting Windows 7, Windows 8, Windows Server 2008
>>> R2, and Windows Server 2012.
>>>
>>> We're also planning to drop Support for the 32 bit release of Cygwin in
>>> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
>>> maintainers won't have to update 32 bit packages anymore. If you're
>>> still running Cygwin under WOW64, consider to move to 64 bit in the next
>>> couple of months.
>>>
>>>
>>> Corinna
>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi Pedro,

This is not about a 64-bit version of AOO but about building AOO with
Cygwin 64-bit.

AOO41x needs Cygwin32 at the moment, trunk/AOO42X are already built with
Cygwin64.

Regards,

   Matthias

Am 27.10.21 um 18:16 schrieb Pedro Lino:
> Hi Matthias
>
> I agree. Providing 64-bit Windows binaries must be the #1 priority for this 
> Project (not because they are needed or better than the 32-bit builds but 
> because they will not be supported by the compilers or the OS)
> This will also solve the problem of having to suggest the installation of a 
> 32-bit Java (which is also becoming unsupported)
>
> Regards,
> Pedro
>
>
>> On 10/27/2021 4:25 PM Matthias Seidel  wrote:
>>
>>
>>
>> Hi all,
>>
>> Looks like we need to get building AOO41X for Windows on Cygwin64 or get 
>> out AOO42X.
>>
>> Whatever comes first... ;-)
>>
>> Regards,
>>
>>Matthias
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: [HEADSUP] Phasing out old Windows versions and 32 bit 
>> support
>> Datum:   Wed, 27 Oct 2021 10:57:45 +0200
>> Von: Corinna Vinschen via Cygwin-announce 
>>  mailto:cygwin-annou...@cygwin.com
>> Antwort an:  cyg...@cygwin.com mailto:cyg...@cygwin.com
>> An:  cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
>> Kopie (CC):  Corinna Vinschen  
>> mailto:corinna-cyg...@cygwin.com
>>
>>
>> [I sent this announcement to the Cygwin mailing list accidentally.
>> Now sending it to cygwin-announce, too, to reach more people. Please
>> reply on the cygwin mailing list if you have any concerns or comments]
>>
>>
>> Hi folks,
>>
>>
>> The upcoming version 3.3.0 is the last version officially supporting
>> Windows Vista and Windows Server 2008.
>>
>> The next major release 3.4.0 will be released in 2022 and will be the
>> last one officially supporting Windows 7, Windows 8, Windows Server 2008
>> R2, and Windows Server 2012.
>>
>> We're also planning to drop Support for the 32 bit release of Cygwin in
>> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
>> maintainers won't have to update 32 bit packages anymore. If you're
>> still running Cygwin under WOW64, consider to move to 64 bit in the next
>> couple of months.
>>
>>
>> Corinna
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Pedro Lino]

Hi Matthias

I agree. Providing 64-bit Windows binaries must be the #1 priority for this 
Project (not because they are needed or better than the 32-bit builds but 
because they will not be supported by the compilers or the OS)
This will also solve the problem of having to suggest the installation of a 
32-bit Java (which is also becoming unsupported)

Regards,
Pedro


> On 10/27/2021 4:25 PM Matthias Seidel  wrote:
> 
> 
> 
> Hi all,
> 
> Looks like we need to get building AOO41X for Windows on Cygwin64 or get 
> out AOO42X.
> 
> Whatever comes first... ;-)
> 
> Regards,
> 
>Matthias
> 
> 
> 
>  Weitergeleitete Nachricht 
> Betreff:  [HEADSUP] Phasing out old Windows versions and 32 bit support
> Datum:Wed, 27 Oct 2021 10:57:45 +0200
> Von:  Corinna Vinschen via Cygwin-announce 
>  mailto:cygwin-annou...@cygwin.com
> Antwort an:   cyg...@cygwin.com mailto:cyg...@cygwin.com
> An:   cygwin-annou...@cygwin.com mailto:cygwin-annou...@cygwin.com
> Kopie (CC):   Corinna Vinschen  
> mailto:corinna-cyg...@cygwin.com
> 
> 
> [I sent this announcement to the Cygwin mailing list accidentally.
> Now sending it to cygwin-announce, too, to reach more people. Please
> reply on the cygwin mailing list if you have any concerns or comments]
> 
> 
> Hi folks,
> 
> 
> The upcoming version 3.3.0 is the last version officially supporting
> Windows Vista and Windows Server 2008.
> 
> The next major release 3.4.0 will be released in 2022 and will be the
> last one officially supporting Windows 7, Windows 8, Windows Server 2008
> R2, and Windows Server 2012.
> 
> We're also planning to drop Support for the 32 bit release of Cygwin in
> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
> maintainers won't have to update 32 bit packages anymore. If you're
> still running Cygwin under WOW64, consider to move to 64 bit in the next
> couple of months.
> 
> 
> Corinna
> 

Fwd: [HEADSUP] Phasing out old Windows versions and 32 bit support

[Matthias Seidel]

Hi all,

Looks like we need to get building AOO41X for Windows on Cygwin64 or get
out AOO42X.

Whatever comes first... ;-)

Regards,

   Matthias



 Weitergeleitete Nachricht 
Betreff:[HEADSUP] Phasing out old Windows versions and 32 bit support
Datum:  Wed, 27 Oct 2021 10:57:45 +0200
Von:Corinna Vinschen via Cygwin-announce 
Antwort an: cyg...@cygwin.com
An: cygwin-annou...@cygwin.com
Kopie (CC): Corinna Vinschen 



[I sent this announcement to the Cygwin mailing list accidentally.
Now sending it to cygwin-announce, too, to reach more people. Please
reply on the cygwin mailing list if you have any concerns or comments]


Hi folks,


The upcoming version 3.3.0 is the last version officially supporting
Windows Vista and Windows Server 2008.

The next major release 3.4.0 will be released in 2022 and will be the
last one officially supporting Windows 7, Windows 8, Windows Server 2008
R2, and Windows Server 2012.

We're also planning to drop Support for the 32 bit release of Cygwin in
2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
maintainers won't have to update 32 bit packages anymore. If you're
still running Cygwin under WOW64, consider to move to 64 bit in the next
couple of months.


Corinna


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.11 released

[Matthias Seidel]

Hi all,

And thanks to everyone who was involved in this release!

Time to move on...

Can anyone create a tag/branch for AOO41X?
Note that Jim already merged new code, so it is not HEAD of.

We should also update the documentation here, some parts are still for SVN:

https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release#HowtoCookaRelease-Tasksafterthereleaseispublic

Regards,

   Matthias

Am 06.10.21 um 22:20 schrieb Carl Marcum:
> Hello OpenOffice community,
>
> We want to thank everyone who helped make this release happen.
>
> Best regards,
> Carl
> (on behalf of the Apache OpenOffice PMC)
>
>
>  Forwarded Message 
> Subject: [ANNOUNCE] Apache OpenOffice 4.1.11 released
> Date: Wed, 6 Oct 2021 14:19:06 -0400
> From: Carl Marcum 
> Organization: Apache Software Foundation
> To: annou...@openoffice.apache.org
>
>
>
> 06 October 2021 - The Apache OpenOffice project is pleased to announce
> the release of Apache OpenOffice 4.1.11.
>
> This release is dedicated to Patricia Shanahan who was a valued
> contributor to the project.
> https://s.apache.org/patricia.shanahan
>
> Apache OpenOffice is a popular Open Source office document productivity
> suite available in 41 languages on Windows, macOS and Linux.
>
> Apache OpenOffice 4.1.11 is a security release aimed at correcting the
> following issues:
>
> CVE-2021-33035 Buffer overflow from a crafted DBF file
> CVE-2021-40439 Billion Laughs
> CVE-2021-28129 DEB packaging for Apache OpenOffice 4.1.8 installed
> with a non-root userid and groupid
>
> This release also includes the latest dictionaries.
> All users of Apache OpenOffice 4.1.10 or earlier are advised to upgrade.
>
> For the complete overview see the list in Bugzilla:
> https://s.apache.org/AOO-4111changes
>
> Full version of this announcement:
> https://s.apache.org/AOO-4111announcement
>
> Apache OpenOffice 4.1.11 Release Notes:
> https://s.apache.org/AOO-4111releasenotes
>
> Download the source:
> https://openoffice.apache.org/downloads.html
>
> Download Apache OpenOffice 4.1.11 from the original source only:
> https://www.openoffice.org/download/
>
> Follow Apache OpenOffice:
> Twitter   https://twitter.com/apacheoo
> Facebook  https://www.facebook.com/ApacheOO
> YouTube   https://www.youtube.com/openoffice
> Mail  https://openoffice.apache.org/mailing-lists.html
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.11 released

[Carl Marcum]

Hello OpenOffice community,

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the Apache OpenOffice PMC)


 Forwarded Message 
Subject:[ANNOUNCE] Apache OpenOffice 4.1.11 released
Date:   Wed, 6 Oct 2021 14:19:06 -0400
From:   Carl Marcum 
Organization:   Apache Software Foundation
To: annou...@openoffice.apache.org



06 October 2021 - The Apache OpenOffice project is pleased to announce
the release of Apache OpenOffice 4.1.11.

This release is dedicated to Patricia Shanahan who was a valued
contributor to the project.
https://s.apache.org/patricia.shanahan

Apache OpenOffice is a popular Open Source office document productivity
suite available in 41 languages on Windows, macOS and Linux.

Apache OpenOffice 4.1.11 is a security release aimed at correcting the
following issues:

CVE-2021-33035 Buffer overflow from a crafted DBF file
CVE-2021-40439 Billion Laughs
CVE-2021-28129 DEB packaging for Apache OpenOffice 4.1.8 installed with 
a non-root userid and groupid


This release also includes the latest dictionaries.
All users of Apache OpenOffice 4.1.10 or earlier are advised to upgrade.

For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4111changes

Full version of this announcement:
https://s.apache.org/AOO-4111announcement

Apache OpenOffice 4.1.11 Release Notes:
https://s.apache.org/AOO-4111releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.11 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html


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

Re: Fwd: FrOSCon 2021: Event Details

[Matthias Seidel]

Hi Michael,

Am 02.08.21 um 10:50 schrieb Dr. Michael Stehmann:
> Hello,
>
> I have asked for a "booth" for Apache OpenOffice.

Thank you for the ongoing work! I hope we get a"presence" at FrOSCon.

Regards,

   Matthias

>
> Ich habe dort einen "Stand" angemeldet.
>
> Kind regards
> Freundliche Grüße
> Michael
>
>
>  Weitergeleitete Nachricht 
> Betreff: FrOSCon 2021: Event Details
> Datum: Sun, 1 Aug 2021 21:41:19 +0200
> Von: proje...@lists.froscon.de
> Antwort an: proje...@froscon.de
> An: proje...@lists.froscon.de
>
> [Deutsche Version unten / German version below]
>
> As FrOSCon approaches, we wanted to inform you of some of the details
> regarding the event. Just to remind you, we'll have the 16th edition
> of FrOSCon as an online event on August, 21st to 22nd 2021.
>
> While we had considered about having a more interactive presence like
> you may have seen on other events, we decided against it due the massive
> workload that would've been required. Therefore, we can "only" offer you
> BigBlueButton conference rooms for your booths/devrooms.
>
> This software offers text, audio and video communication as well as
> several presentation tools. Based on your submissions we're confident
> that this should be suitable for everyone. However, you may still
> write us about your project's specific needs.
>
> You'll receive an email with the exact location and access instruction
> before the event starts. Additionally, your room will be linked on our
> main conference page, so that interested visitors may find you there.
>
> If you have any questions, you can reach us via proje...@froscon.org.
>
> We hope to see you at FrOSCon!
>
> -
>
> Da sich das Wochenende der FrOSCon nähert, möchten wir euch noch über
> die Details zur Veranstaltung informieren. Nur zur Erinnerung: die 16.
> Ausgabe der FrOSCon findet online am 21. und 22. August 2021 statt.
>
> Nachdem wir erst über eine interaktivere Präsenz nachgedacht hatten, die
> ihr vielleicht auf anderen Events gesehen habt, haben wir uns
> schließlich aufgrund des großen Aufwandes dagegen entschieden. Daher
> können wir "euch" nur BigBlueButton-Konferenzräume für eure
> Stände/Devrooms anbieten.
>
> Die Software erlaubt Text-, Audio- und Video-Kommunikation und bietet
> außerdem einige Tools für Präsentationen. Anhand eurer Einreichungen
> gehen wir davon aus, dass das für alle Projekte passt. Natürlich könnt
> ihr uns nach wie vor zu Sonderwünschen schreiben.
>
> Ihr bekommt vor dem Start des Events noch eine Mail mit dem genauen Ort
> und wie ihr darauf zugreifen könnt. Außerdem werden wir euren Raum auf
> der Hauptseite der Konferenz verlinken, damit euch interessierte
> Besucher finden können.
>
> Falls ihr Fragen habt, könnt ihr uns unter proje...@froscon.org
> erreichen.
>
> Wir freuen uns euch bei der FrOSCon zu sehen!
> ___
> Projects mailing list
> proje...@lists.froscon.de
> https://management.froscon.de/mailman/listinfo/projects
>
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: FrOSCon 2021: Event Details

[Dr. Michael Stehmann]

Hello,

I have asked for a "booth" for Apache OpenOffice.

Ich habe dort einen "Stand" angemeldet.

Kind regards
Freundliche Grüße
Michael


 Weitergeleitete Nachricht 
Betreff: FrOSCon 2021: Event Details
Datum: Sun, 1 Aug 2021 21:41:19 +0200
Von: proje...@lists.froscon.de
Antwort an: proje...@froscon.de
An: proje...@lists.froscon.de

[Deutsche Version unten / German version below]

As FrOSCon approaches, we wanted to inform you of some of the details
regarding the event. Just to remind you, we'll have the 16th edition
of FrOSCon as an online event on August, 21st to 22nd 2021.

While we had considered about having a more interactive presence like
you may have seen on other events, we decided against it due the massive
workload that would've been required. Therefore, we can "only" offer you
BigBlueButton conference rooms for your booths/devrooms.

This software offers text, audio and video communication as well as
several presentation tools. Based on your submissions we're confident
that this should be suitable for everyone. However, you may still
write us about your project's specific needs.

You'll receive an email with the exact location and access instruction
before the event starts. Additionally, your room will be linked on our
main conference page, so that interested visitors may find you there.

If you have any questions, you can reach us via proje...@froscon.org.

We hope to see you at FrOSCon!

-

Da sich das Wochenende der FrOSCon nähert, möchten wir euch noch über
die Details zur Veranstaltung informieren. Nur zur Erinnerung: die 16.
Ausgabe der FrOSCon findet online am 21. und 22. August 2021 statt.

Nachdem wir erst über eine interaktivere Präsenz nachgedacht hatten, die
ihr vielleicht auf anderen Events gesehen habt, haben wir uns
schließlich aufgrund des großen Aufwandes dagegen entschieden. Daher
können wir "euch" nur BigBlueButton-Konferenzräume für eure
Stände/Devrooms anbieten.

Die Software erlaubt Text-, Audio- und Video-Kommunikation und bietet
außerdem einige Tools für Präsentationen. Anhand eurer Einreichungen
gehen wir davon aus, dass das für alle Projekte passt. Natürlich könnt
ihr uns nach wie vor zu Sonderwünschen schreiben.

Ihr bekommt vor dem Start des Events noch eine Mail mit dem genauen Ort
und wie ihr darauf zugreifen könnt. Außerdem werden wir euren Raum auf
der Hauptseite der Konferenz verlinken, damit euch interessierte
Besucher finden können.

Falls ihr Fragen habt, könnt ihr uns unter proje...@froscon.org erreichen.

Wir freuen uns euch bei der FrOSCon zu sehen!
___
Projects mailing list
proje...@lists.froscon.de
https://management.froscon.de/mailman/listinfo/projects





OpenPGP_signature
Description: OpenPGP digital signature

Fwd: [libexpat/libexpat] Release R_2_4_0 - 2.4.0

[Matthias Seidel]

FYI:

 Weitergeleitete Nachricht 
Betreff:[libexpat/libexpat] Release R_2_4_0 - 2.4.0
Datum:  Sat, 22 May 2021 16:03:09 -0700
Von:Sebastian Pipping 
Antwort an: libexpat/libexpat 
An: libexpat/libexpat 
Kopie (CC): Subscribed 



  2.4.0 

Repository: libexpat/libexpat  ·
Tag: R_2_4_0  ·
Commit: ac2b235

· Released by: hartwork 

Original change log


—

This release has 2 assets:

  * Source code (zip)
  * Source code (tar.gz)

Visit the release page
 to download
them.

—
You are receiving this because you are watching this repository.
View it on GitHub
 or
unsubscribe

from all notifications for this repository.



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.10 released

[Carl Marcum]

Hello OpenOffice community,

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the Apache OpenOffice PMC)


 Forwarded Message 
Subject:[ANNOUNCE] Apache OpenOffice 4.1.10 released
Date:   Tue, 4 May 2021 09:59:21 -0400
From:   Carl Marcum 
Organization:   Apache Software Foundation
To: annou...@openoffice.apache.org



04 May 2021 - The Apache OpenOffice project is pleased to announce the
release of Apache OpenOffice 4.1.10.

Apache OpenOffice is a popular Open Source office document productivity 
suite

available in 41 languages on Windows, macOS and Linux.

Apache OpenOffice 4.1.10 is a security release aimed at correcting an issue
with opening non-HTTP(S) links in a document.
This release also includes the latest dictionaries.
All users of Apache OpenOffice 4.1.9 or earlier are advised to upgrade.

For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4110changes

Full version of this announcement:
https://s.apache.org/AOO-4110announcement

Apache OpenOffice 4.1.10 Release Notes:
https://s.apache.org/AOO-4110releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.10 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html


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

Re: Fwd: [libexpat/libexpat] Release R_2_3_0 - 2.3.0

[Don Lewis]

On 25 Mar, Matthias Seidel wrote:
> Hi all,
> 
>> #422 #426 #447 Windows: Drop support for Visual Studio <=14.0/2015
> 
> Seems, we are out of look here due to the ancient compiler we still use
> on Windows...

Same with nss.  I suspect lack of C99 support is the issue.


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

Re: Fwd: [libexpat/libexpat] Release R_2_3_0 - 2.3.0

[Matthias Seidel]

Hi all,

> #422 #426 #447 Windows: Drop support for Visual Studio <=14.0/2015

Seems, we are out of look here due to the ancient compiler we still use
on Windows...

Matthias

Am 25.03.21 um 02:14 schrieb Matthias Seidel:
>
> FYI
>
>
>  Weitergeleitete Nachricht 
> Betreff:  [libexpat/libexpat] Release R_2_3_0 - 2.3.0
> Datum:Wed, 24 Mar 2021 17:51:35 -0700
> Von:  Sebastian Pipping 
> Antwort an:   libexpat/libexpat 
> An:   libexpat/libexpat 
> Kopie (CC):   Subscribed 
>
>
>
>   2.3.0 
>
> Repository: libexpat/libexpat  ·
> Tag: R_2_3_0  ·
> Commit: 2d58706
> 
> · Released by: hartwork 
>
> Original changelog
> 
>
> —
>
> This release has 11 assets:
>
>   * expat-2.3.0.tar.bz2
>   * expat-2.3.0.tar.bz2.asc
>   * expat-2.3.0.tar.gz
>   * expat-2.3.0.tar.gz.asc
>   * expat-2.3.0.tar.lz
>   * expat-2.3.0.tar.lz.asc
>   * expat-2.3.0.tar.xz
>   * expat-2.3.0.tar.xz.asc
>   * expat-win32bin-2.3.0.exe
>   * Source code (zip)
>   * Source code (tar.gz)
>
> Visit the release page
>  to
> download them.
>
> —
> You are receiving this because you are watching this repository.
> View it on GitHub
>  or
> unsubscribe
> 
> from all notifications for this repository.
>


smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [libexpat/libexpat] Release R_2_3_0 - 2.3.0

[Matthias Seidel]

FYI


 Weitergeleitete Nachricht 
Betreff:[libexpat/libexpat] Release R_2_3_0 - 2.3.0
Datum:  Wed, 24 Mar 2021 17:51:35 -0700
Von:Sebastian Pipping 
Antwort an: libexpat/libexpat 
An: libexpat/libexpat 
Kopie (CC): Subscribed 



  2.3.0 

Repository: libexpat/libexpat  ·
Tag: R_2_3_0  ·
Commit: 2d58706

· Released by: hartwork 

Original changelog


—

This release has 11 assets:

  * expat-2.3.0.tar.bz2
  * expat-2.3.0.tar.bz2.asc
  * expat-2.3.0.tar.gz
  * expat-2.3.0.tar.gz.asc
  * expat-2.3.0.tar.lz
  * expat-2.3.0.tar.lz.asc
  * expat-2.3.0.tar.xz
  * expat-2.3.0.tar.xz.asc
  * expat-win32bin-2.3.0.exe
  * Source code (zip)
  * Source code (tar.gz)

Visit the release page
 to download
them.

—
You are receiving this because you are watching this repository.
View it on GitHub
 or
unsubscribe

from all notifications for this repository.



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Matthias Seidel]

Hi Pedro,

Am 03.03.21 um 00:24 schrieb Pedro Lino:
> Hi Matthias
>
>> On 03/02/2021 11:05 PM Matthias Seidel  wrote:
>> Am 14.02.21 um 17:35 schrieb Pedro Lino:
>>> Hi Marcus
>>>
 On 02/14/2021 3:36 PM Marcus  wrote:
> One question: does someone have the permissions to update the Sourceforge 
> page?
 I don't know how to edit this. I don't find any hint for it - even as 
 admin. Must be a thing of SF.net.
>>> Can we ask them? I volunteer to do that on behalf of AOO if you don't have 
>>> the time.
>> Do you have a SourceForge account?
> I have an old one but not associated to OpenOffice
No problem, I only thought about giving you administrative rights.
> In any case I wrote to support and they answered that they are investigating 
> the issue. It has been a week since they answered. I will give them a few 
> more days before asking for progress.

Thanks, I did not find any possibility to change it.

It seems to be a generated RSS feed that stopped working years ago...

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Pedro Lino]

Hi Matthias

> On 03/02/2021 11:05 PM Matthias Seidel  wrote:

> Am 14.02.21 um 17:35 schrieb Pedro Lino:
> > Hi Marcus
> >
> >> On 02/14/2021 3:36 PM Marcus  wrote:
> >>> One question: does someone have the permissions to update the Sourceforge 
> >>> page?
> >> I don't know how to edit this. I don't find any hint for it - even as 
> >> admin. Must be a thing of SF.net.
> > Can we ask them? I volunteer to do that on behalf of AOO if you don't have 
> > the time.
> 
> Do you have a SourceForge account?

I have an old one but not associated to OpenOffice
In any case I wrote to support and they answered that they are investigating 
the issue. It has been a week since they answered. I will give them a few more 
days before asking for progress.

Regards,
Pedro

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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Matthias Seidel]

Hi Pedro,

Am 14.02.21 um 17:35 schrieb Pedro Lino:
> Hi Marcus
>
>> On 02/14/2021 3:36 PM Marcus  wrote:
>>> One question: does someone have the permissions to update the Sourceforge 
>>> page?
>> I don't know how to edit this. I don't find any hint for it - even as 
>> admin. Must be a thing of SF.net.
> Can we ask them? I volunteer to do that on behalf of AOO if you don't have 
> the time.

Do you have a SourceForge account?

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Peter Kovacs]

FYI: I posted a (late) note on Facebook.

I added some info additional Infos on test distributions.

Maybe people continue to sign up.


On 14.02.21 18:35, Marcus wrote:

Am 14.02.21 um 17:35 schrieb Pedro Lino:

On 02/14/2021 3:36 PM Marcus  wrote:


just go ahead.

Marcus



One question: does someone have the permissions to update the 
Sourceforge page?



I don't know how to edit this. I don't find any hint for it - even as
admin. Must be a thing of SF.net.


Can we ask them? I volunteer to do that on behalf of AOO if you don't 
have the time.



-
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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Marcus]

Am 14.02.21 um 17:35 schrieb Pedro Lino:

On 02/14/2021 3:36 PM Marcus  wrote:


just go ahead.

Marcus




One question: does someone have the permissions to update the Sourceforge page?



I don't know how to edit this. I don't find any hint for it - even as
admin. Must be a thing of SF.net.


Can we ask them? I volunteer to do that on behalf of AOO if you don't have the 
time.



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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Pedro Lino]

Hi Marcus

> On 02/14/2021 3:36 PM Marcus  wrote:

> > One question: does someone have the permissions to update the Sourceforge 
> > page?

> I don't know how to edit this. I don't find any hint for it - even as 
> admin. Must be a thing of SF.net.

Can we ask them? I volunteer to do that on behalf of AOO if you don't have the 
time.

Regards,
Pedro

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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Marcus]

Am 13.02.21 um 20:10 schrieb Pedro Lino:

Hi all

I am happy to announce that I was notified today about the availability of a 
new AOO version!

Congratulations to all for the previous effort to fix notifications in 4.1.8!

One question: does someone have the permissions to update the Sourceforge page?

It is a little absurd that on the main page for OpenOffice
https://sourceforge.net/projects/openofficeorg.mirror/
it reports Project Activity
3 years ago
when the latest files have been uploaded on 2021-02-02


I don't know how to edit this. I don't find any hint for it - even as 
admin. Must be a thing of SF.net.


Marcus


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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Pedro Lino]

Hi all

I am happy to announce that I was notified today about the availability of a 
new AOO version!

Congratulations to all for the previous effort to fix notifications in 4.1.8!

One question: does someone have the permissions to update the Sourceforge page? 

It is a little absurd that on the main page for OpenOffice
https://sourceforge.net/projects/openofficeorg.mirror/
it reports Project Activity 
3 years ago
when the latest files have been uploaded on 2021-02-02

Regards,
Pedro

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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Marcus]

Am 08.02.21 um 11:43 schrieb Arrigo Marchiori:

first of all I want to thank you and all the people involved with
preparing this release!

At the moment, the link on top of www.openoffice.org takes to a HTTP
404 page -- apparently a missing blog entry. But the site
blogs.apache.org seems to be working and so our blog:
https://blogs.apache.org/ooo/


the reason was an outage of parts of the Blog system. The announcement 
was ready but couldn't be published and therefore not displayed for the 
public.


Too bad it was while the go-live was runnning.

In the meantime I was able to publish the announcement.


Maybe it's worth removing the link until the blog entry will be ready?


I don't think it can be removed but only pointing to other target.


Just my two cents, as in Europe we are deep into our business hours
and this small problem may be quite well noticed.


I know the other side would be to delay the release. But I've decided 
not to wait any longer just because one task is not possible.


Marcus




On Mon, Feb 08, 2021 at 12:45:50AM +0100, Marcus wrote:


Hello OpenOffice community,

today we want to share with you the announcement from below.

Thank You

to all who have helped to make this new release happen. Especially the Mac
community will be happy again as they can use DOCX, XLSX; and PPTX document
again.

PS:
The Apache Blog server is having an outage at the moment. So, please be
patient as the usual announcement is not yet there.

Marcus
(on behalf of the Apache OpenOffice PMC)



 Weitergeleitete Nachricht 
Betreff: [ANNOUNCE] Apache OpenOffice 4.1.9 released
Datum: Mon, 8 Feb 2021 00:33:33 +0100
Von: Marcus 
Antwort an: annou...@openoffice.apache.org
An: annou...@openoffice.apache.org

07 February 2021 - Apache OpenOffice, the leading Open Source office
document productivity suite, announced today Apache OpenOffice 4.1.9, now
available in 41 languages on Windows, macOS and Linux.

Apache OpenOffice 4.1.9 is a maintenance release aimed at correcting some
regressions and delivering the latest English dictionary. All users of
Apache OpenOffice 4.1.8 or earlier are advised to upgrade.

For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-419changes

Full version of this announcement:
https://s.apache.org/AOO-419announcement

Apache OpenOffice 4.1.8 Release Notes:
https://s.apache.org/AOO-419releasenotes

Download Apache OpenOffice 4.1.9 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html



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

Re: Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Arrigo Marchiori]

Hello Marcus,

first of all I want to thank you and all the people involved with
preparing this release!

At the moment, the link on top of www.openoffice.org takes to a HTTP
404 page -- apparently a missing blog entry. But the site
blogs.apache.org seems to be working and so our blog:
https://blogs.apache.org/ooo/

Maybe it's worth removing the link until the blog entry will be ready?

Just my two cents, as in Europe we are deep into our business hours
and this small problem may be quite well noticed.

Thank you again and best regards.

On Mon, Feb 08, 2021 at 12:45:50AM +0100, Marcus wrote:

> Hello OpenOffice community,
> 
> today we want to share with you the announcement from below.
> 
> Thank You
> 
> to all who have helped to make this new release happen. Especially the Mac
> community will be happy again as they can use DOCX, XLSX; and PPTX document
> again.
> 
> PS:
> The Apache Blog server is having an outage at the moment. So, please be
> patient as the usual announcement is not yet there.
> 
> Marcus
> (on behalf of the Apache OpenOffice PMC)
> 
> 
> 
>  Weitergeleitete Nachricht 
> Betreff: [ANNOUNCE] Apache OpenOffice 4.1.9 released
> Datum: Mon, 8 Feb 2021 00:33:33 +0100
> Von: Marcus 
> Antwort an: annou...@openoffice.apache.org
> An: annou...@openoffice.apache.org
> 
> 07 February 2021 - Apache OpenOffice, the leading Open Source office
> document productivity suite, announced today Apache OpenOffice 4.1.9, now
> available in 41 languages on Windows, macOS and Linux.
> 
> Apache OpenOffice 4.1.9 is a maintenance release aimed at correcting some
> regressions and delivering the latest English dictionary. All users of
> Apache OpenOffice 4.1.8 or earlier are advised to upgrade.
> 
> For the complete overview see the list in Bugzilla:
> https://s.apache.org/AOO-419changes
> 
> Full version of this announcement:
> https://s.apache.org/AOO-419announcement
> 
> Apache OpenOffice 4.1.8 Release Notes:
> https://s.apache.org/AOO-419releasenotes
> 
> Download Apache OpenOffice 4.1.9 from the original source only:
> https://www.openoffice.org/download/
> 
> Follow Apache OpenOffice:
> Twitter   https://twitter.com/apacheoo
> Facebook  https://www.facebook.com/ApacheOO
> YouTube   https://www.youtube.com/openoffice
> Mail  https://openoffice.apache.org/mailing-lists.html
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Arrigo

http://rigo.altervista.org

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

Fwd: [ANNOUNCE] Apache OpenOffice 4.1.9 released

[Marcus]

Hello OpenOffice community,

today we want to share with you the announcement from below.

Thank You

to all who have helped to make this new release happen. Especially the 
Mac community will be happy again as they can use DOCX, XLSX; and PPTX 
document again.


PS:
The Apache Blog server is having an outage at the moment. So, please be 
patient as the usual announcement is not yet there.


Marcus
(on behalf of the Apache OpenOffice PMC)



 Weitergeleitete Nachricht 
Betreff: [ANNOUNCE] Apache OpenOffice 4.1.9 released
Datum: Mon, 8 Feb 2021 00:33:33 +0100
Von: Marcus 
Antwort an: annou...@openoffice.apache.org
An: annou...@openoffice.apache.org

07 February 2021 - Apache OpenOffice, the leading Open Source office 
document productivity suite, announced today Apache OpenOffice 4.1.9, 
now available in 41 languages on Windows, macOS and Linux.


Apache OpenOffice 4.1.9 is a maintenance release aimed at correcting 
some regressions and delivering the latest English dictionary. All users 
of Apache OpenOffice 4.1.8 or earlier are advised to upgrade.


For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-419changes

Full version of this announcement:
https://s.apache.org/AOO-419announcement

Apache OpenOffice 4.1.8 Release Notes:
https://s.apache.org/AOO-419releasenotes

Download Apache OpenOffice 4.1.9 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html


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

Fwd: CLT2021/B132: Ausstellerzusage "Apache OpenOffice"

[Dr. Michael Stehmann]

Hello,

only a little abstract for your information:

"In 2021 the Chemnitz Linux Days have found a place on a weekend in
March again, although this year in a different form, namely virtual.
Pick up your schedule and make a big mark on 13th and 14th of March
2021. You won't regret it." [0]

Apache OpenOffice will participate with a virtual booth. (Like we did
with a 'real' booth all the years before.)

Kind regards
Michael

[0] https://chemnitzer.linux-tage.de/2021/en/

 Weitergeleitete Nachricht 
Betreff: CLT2021/B132: Ausstellerzusage "Apache OpenOffice"
Datum: Fri, 22 Jan 2021 18:48:58 +0100 (CET)
Von: l...@linux-tage.de
An: anw...@rechtsanwalt-stehmann.de

Hallo Frau Mechtilde Stehmann,
Hallo Herr Dr. Michael Stehmann,


in den vergangenen Wochen habt ihr euch als Aussteller mit dem Titel
"Apache OpenOffice" bei den Chemnitzer Linux-Tagen 2021 angemeldet. Wir
möchten euch gern in unser Programm aufnehmen.

Wie ihr euch sicher denken könnt, ist dieses Jahr alles etwas anders. In
Anbetracht der Corona-Situation können wir uns im März nicht an der TU
Chemnitz treffen. Die Chemnitzer Linux-Tage 2021 werden daher rein
virtuell stattfinden. Mit dieser Mail möchte wir euch über die
wesentlichen Randbedingungen informieren.

* Bitte gebt bis spätestens 7. Februar explizit per Antwort und diese
Mail Bescheid, dass ihr euch an den CLT 2021 beteiligen wollt.

* Zusätzliche Standbetreuer könnt ihr bis zum 21. Februar unter
folgender URL anmelden:
https://chemnitzer.linux-tage.de/2021/de/programm/beitrag/...

* Wir stellen euch einen virtuellen Videokonferenz-Raum in unserem
Open-Source-Videokonferenzsystem BigBlueButton. Vor der Veranstaltung
werdet ihr von uns entsprechende Zugangsdaten erhalten.Unsere Besucher
können diesen Videokonferenzraum während der Veranstaltung betreten und
mit euch interagieren. Für BigBlueButton werden wir Demo-Termine
anbieten. Bis es soweit ist könnt ihr unter folgender URL testen:
https://demo.bigbluebutton.org/gl/

* Über die Gestaltung eures Standprogramms seid ihr frei. Ihr könnt
entweder die gesamte Zeit für Gespräche und Diskussionen bereit stehen
oder selbst ein kleines Standprogramm veröffentlichen (z.B.
Mini-Diskussionsrunden, Quizze, was auch immer euch einfällt). WICHTIG:
Teilt uns euer Standprogramm (Zeitpunkt, Titel, Kurzbeschreibung) bitte
bis zum 21. Februar per E-Mail mit.

* Solltet ihr kein eigenes Programm erstellen, so stellt bitte sicher,
dass während der gesamten Veranstaltung immer mind. eine Person von euch
im Videokonferenzraum erreichbar ist, damit der Stand nicht verlassen wirkt.

* CONFIDENTIAL: Weiterhin arbeiten wir noch an einer CLT-Version des
legendären Workadventures (siehe https://workadventu.re/). Dort werden
wir euch einen Stand bereitstellen und unsere Besucher können dann mit
einem digitalen Avatar durch das Hörsaal- und Seminargebäude laufen und
euch am Stand besuchen. Ob wir das bis März wirklich schaffen, können
wir nicht garantieren. Bitte behaltet dieses Information vorerst für
euch. Wir halten euch auf dem Laufenden.


Viele Grüße,
Euer Linux-Live-Team

Chemnitzer Linux-Tage 2021



OpenPGP_signature
Description: OpenPGP digital signature

Fwd: [openoffice] annotated tag AOO419-RC1 created (now a53baa6)

[Jim Jagielski]

> Begin forwarded message:
> 
> From: j...@apache.org
> Subject: [openoffice] annotated tag AOO419-RC1 created (now a53baa6)
> Date: January 8, 2021 at 2:24:06 PM EST
> To: "comm...@openoffice.apache.org" 
> Reply-To: dev@openoffice.apache.org
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> jim pushed a change to annotated tag AOO419-RC1
> in repository https://gitbox.apache.org/repos/asf/openoffice.git.
> 
> 
>  at a53baa6  (tag)
> tagging 561082130aec836ff9c7626c642cf3c44fbec11f (commit)
> replaces AOO418-GA
>  by Jim Jagielski
>  on Fri Jan 8 14:19:15 2021 -0500
> 
> - Log -
> Tag HEAD (561082130aec836ff9c7626c642cf3c44fbec11f) of AOO419 as AOO419-RC1
> ---
> 
> No new revisions were added by this update.
> 

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Keith N. McKenna]

On 12/11/2020 10:01 AM, Matthias Seidel wrote:
> Hi Peter,
> 
> I am not sure what you are talking about here...
> 
> The discussion is about a non working extension for our Wiki server.
> 
> The repository is for our Media Wiki extension?
> 
> 2 totally different things...
> 
> Matthias

Matthias;

The repository Peter created is for custom MediaWiki extensions that
were created specifically for our mwiki. The one in particular is the
one raising havoc with many pages in the development section of the
mwiki were multiple pages will not open because some instructions were
deprecated.

Regards
Keith

> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
>> I have created the Repository for MWiki extensions with my Proposed name:
>>
>> openoffice-mwiki-ext.git
>> 
>>
>> It is ready to add our MWiki extensions.
>>
>>
>> On 10.12.20 20:35, Keith N. McKenna wrote:
>>> On 12/9/2020 5:38 PM, Marcus wrote:
 Am 09.12.20 um 18:35 schrieb Peter Kovacs:
> How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
>
> We could do the same for the forums customizations.
>
> So we have more control over our support code.
 +1
 This increases the chance that also others can have a look and give
 some
 hints when problems arise.

 Marcus

>>> +1
>>>
>>> Keith

> On 09.12.20 18:24, Dick Groskamp wrote:
>> On 2020/12/09 11:34:03, Carl Marcum  wrote:
>>> Hi Dick,
>>>
>>> I have copied it out and it's contents are below.
>>>
>>> It should be in github or svn but I haven't had time to do anything
>>> with it.
>>>
>>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
 On 2020/12/08 18:56:25, Carl Marcum  wrote:
> There are still hundreds of broken pages in the dev guide.
> Yes it seems to be idls and ildm tags.
>
> There is a new upgraded VM setup for the wiki waiting to get
> changed to
> but I had hoped to look into before it get switched over.
> But I have had limited time and I haven't been able to do any
> testing
> with it since the URL is being redirected.
> I don't know anything about MediaWiki extensions, yet anyway :)
>
> The Infra ticket for our VM is [1].
>
> The only place I know where the code is in the current wiki under:
> extensions/OOoIDLtags/OOoIDLtags.php
>
>
> [1] https://issues.apache.org/jira/browse/INFRA-20339
>
> Best regards,
> Carl
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
 Carl, thanks i will check into it.

 Is it possible to export/copy the IDLTags extension from the MWiki
 to a more accessible place ?
 That way it might be accessible for editing or reversed
 engineering. I think for now it is not reachable.


>>> The filename is OOoIDLtags.php
>>> 
>>> >> /**
>>>     * IDL Tag extension
>>>     * The IDLTagExtension was written to manage the IDL links in the
>>> OpenOffice.org Developer's Guide.
>>>     * The extension converts Java paths to links back to the
>>> online IDL
>>> documentation.
>>>     * @version 1.0.2
>>>     * @link
>>> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
>>>     */
>>>
>>> if ( !defined( 'MEDIAWIKI' ) ) {
>>>        die( 'This file is a MediaWiki extension, it is not a
>>> valid entry
>>> point' );
>>> }
>>>
>>> // Extension credits that will show up on Special:Version
>>> $wgExtensionCredits['parserhook'][] = array(
>>>        'name' => 'IDL Tags',
>>>        'version' => '1.0.2',
>>>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>>>        'description' => 'Manage the IDL links in the OOo Dev
>>> Guide ',
>>>        'url' =>
>>> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
>>> );
>>>
>>> global $wgExtIDLtags;
>>> $wgExtIDLtags   = new RenderIDLtags;
>>> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
>>>
>>> class RenderIDLtags {
>>>
>>>        function oooIDLTags() {
>>>            global $wgParser;
>>>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
>>> ) );
>>>            $wgParser->setHook( 'idlm', array( &$this,
>>> 'renderIDLM' ) );
>>>            $wgParser->setHook( 'idls', array( &$this,
>>> 'renderIDLS' ) );
>>>            $wgParser->setHook( 'idlmodule', array( &$this,
>>> 'renderIDLMODULE' ) );
>>>            $wgParser->setHook( 'idltopic', array( &$this,
>

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Matthias Seidel]

Hi Dick,

Am 11.12.20 um 20:45 schrieb Dick Groskamp:
>
> On 2020/12/11 19:34:47, Matthias Seidel  wrote: 
>> Hi Dick,
>>
>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>>> On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
 Hi Dick,

 Am 11.12.20 um 17:14 schrieb Dick Groskamp:

 The extension is not broken, it is outdated. It cannot be updated
 because that would need a newer version of Wiki.
 However, our AOO skin for the Wiki must be adapted to the newer Wiki
 version...

 At least that is what I understood from Andrea's posts regarding the
 Wiki server in 2019 [1]

>>> Well, if it is outdated and it doesn't do its job, I think it is broken.
>>> What I meant to say is that it doesn't work the way it was designed anymore.
 See above, the extension is not ours. It is from mediaWiki.org (?)

>>> Well, I think it is ours. It was especially created by former developers 
>>> for this purpose and it is probably nowhere else available/usable and just 
>>> works on our wiki.
>> Who would that developer be?! Do you know a name?
> It was somewhere up in this thread:
> // Extension credits that will show up on Special:Version
> $wgExtensionCredits['parserhook'][] = array(
>  'name' => 'IDL Tags',
>  'version' => '1.0.2',
>  'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>  'description' => 'Manage the IDL links in the OOo Dev Guide ',
>  'url' => 
> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> );
>> Isn't it more likely that it is a mediawiki extension like:
>>
>> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
>>
> That is probably where the confusion comes from. You can develop your own 
> extensions if you want, just like our own .oxt's. The whole IDLTags extension 
> is the PHP-page Carl copied from the configuration. That's all

Yes, it seems that this was done "back then".

But I don't think we should try to fix such an old extension if there is
probably a better one included in the Wiki installation.

>>> I haven't read Andrea's post yet, I focused more on getting this defective 
>>> extension IDLTags repaired.
>> Well, that would be a workaround for the moment, but we should "simply"
>> fix the source of the problem...
>>
> With "source of the problem" I assume you mean upgrading the wiki version and 
> updating the skin
> etc as mentioned in Andrea's post
Yes, if I remember it right, Andrea had to use an older PHP version to
get the Wiki running "as is".
>
> As far as I know has Carl a new updated VM  available to go along with that, 
> but he has a tiny
> problem getting access. I think that will be the next step.

Infra wants to update the VM. This probably means we get an even newer
Wiki installation.

Carl has opened a ticket, since we can't test the new VM because of a
redirection.

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/11 19:34:47, Matthias Seidel  wrote: 
> Hi Dick,
> 
> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
> >
> > On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
> >> Hi Dick,
> >>
> >> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> >>
> >> The extension is not broken, it is outdated. It cannot be updated
> >> because that would need a newer version of Wiki.
> >> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> >> version...
> >>
> >> At least that is what I understood from Andrea's posts regarding the
> >> Wiki server in 2019 [1]
> >>
> > Well, if it is outdated and it doesn't do its job, I think it is broken.
> > What I meant to say is that it doesn't work the way it was designed anymore.
> >> See above, the extension is not ours. It is from mediaWiki.org (?)
> >>
> > Well, I think it is ours. It was especially created by former developers 
> > for this purpose and it is probably nowhere else available/usable and just 
> > works on our wiki.
> 
> Who would that developer be?! Do you know a name?

It was somewhere up in this thread:
// Extension credits that will show up on Special:Version
$wgExtensionCredits['parserhook'][] = array(
 'name' => 'IDL Tags',
 'version' => '1.0.2',
 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
 'description' => 'Manage the IDL links in the OOo Dev Guide ',
 'url' => 
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);
> 
> Isn't it more likely that it is a mediawiki extension like:
> 
> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
> 
That is probably where the confusion comes from. You can develop your own 
extensions if you want, just like our own .oxt's. The whole IDLTags extension 
is the PHP-page Carl copied from the configuration. That's all
> >
> > I haven't read Andrea's post yet, I focused more on getting this defective 
> > extension IDLTags repaired.
> 
> Well, that would be a workaround for the moment, but we should "simply"
> fix the source of the problem...
> 
With "source of the problem" I assume you mean upgrading the wiki version and 
updating the skin
etc as mentioned in Andrea's post

As far as I know has Carl a new updated VM  available to go along with that, 
but he has a tiny
problem getting access. I think that will be the next step.

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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Matthias Seidel]

Hi Dick,

Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>
> On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
>> Hi Dick,
>>
>> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
>>
>> The extension is not broken, it is outdated. It cannot be updated
>> because that would need a newer version of Wiki.
>> However, our AOO skin for the Wiki must be adapted to the newer Wiki
>> version...
>>
>> At least that is what I understood from Andrea's posts regarding the
>> Wiki server in 2019 [1]
>>
> Well, if it is outdated and it doesn't do its job, I think it is broken.
> What I meant to say is that it doesn't work the way it was designed anymore.
>> See above, the extension is not ours. It is from mediaWiki.org (?)
>>
> Well, I think it is ours. It was especially created by former developers for 
> this purpose and it is probably nowhere else available/usable and just works 
> on our wiki.

Who would that developer be?! Do you know a name?

Isn't it more likely that it is a mediawiki extension like:

https://www.mediawiki.org/wiki/Extension:SyntaxHighlight

>
> I haven't read Andrea's post yet, I focused more on getting this defective 
> extension IDLTags repaired.

Well, that would be a workaround for the moment, but we should "simply"
fix the source of the problem...

Regards,

   Matthias

>
> Problem is the deprecation of the ereg_replace function from PHP 7.0.*
> That was the function that was used in this IDLTags extension and made it 
> work as it did. This is the reason that several pages in the DevGuide show 
> blank.
>
> If we can replace the used ereg_replace function by a still usable 
> preg_replace function it should
> work again and all should be well :-)
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
> Hi Dick,
> 
> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> 
> The extension is not broken, it is outdated. It cannot be updated
> because that would need a newer version of Wiki.
> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> version...
> 
> At least that is what I understood from Andrea's posts regarding the
> Wiki server in 2019 [1]
> 
Well, if it is outdated and it doesn't do its job, I think it is broken.
What I meant to say is that it doesn't work the way it was designed anymore.
> 
> See above, the extension is not ours. It is from mediaWiki.org (?)
> 
Well, I think it is ours. It was especially created by former developers for 
this purpose and it is probably nowhere else available/usable and just works on 
our wiki.

I haven't read Andrea's post yet, I focused more on getting this defective 
extension IDLTags repaired.

Problem is the deprecation of the ereg_replace function from PHP 7.0.*
That was the function that was used in this IDLTags extension and made it work 
as it did. This is the reason that several pages in the DevGuide show blank.

If we can replace the used ereg_replace function by a still usable preg_replace 
function it should
work again and all should be well :-)





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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Matthias Seidel]

Hi Dick,

Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> I think there is some confusion. I will try to explain:
I know, that's why I asked. ;-)
>
> There is an extension for AOo, the extension MediaWiki that you repaired for 
> 4.1.8, which is intended to convert text from Writer to Mediawiki content. We 
> are not referring to that one.

Exactly!

But I didn't repair it, it just started to work after we updated several
core component...

>
> There is also an extension for the Mediawiki itself. That extension is called 
> IDLTags en converts tags on the Mediawiki to valid URL's for references to 
> IDL in the DevGuide.
> This is where we are talking about. This last extension has been broken and 
> we couldn't find it anywhere but in the configuration of Mediawiki itself. It 
> was removed from the wiki and it seems the developers left us.

The extension is not broken, it is outdated. It cannot be updated
because that would need a newer version of Wiki.
However, our AOO skin for the Wiki must be adapted to the newer Wiki
version...

At least that is what I understood from Andrea's posts regarding the
Wiki server in 2019 [1]

>
> Carl managed to extract IDLTags from the configuration and now we were 
> looking for a place to store it, so everyone can have a look at it and that 
> it is accessible to everyone.  See it as a safe haven for somehow lost 
> orphans.
>
> Therefore Peter has made this last repo openoffice-mwiki-ext.git
> 

See above, the extension is not ours. It is from mediaWiki.org (?)

Regards,

   Matthias

[1] https://www.mail-archive.com/dev@openoffice.apache.org/msg35741.html

>
> I think you can see it as a vault for precious gems that, not yet, have a 
> place on/in other repo's
>
> Greetings
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/11 15:01:35, Matthias Seidel  wrote: 
> Hi Peter,
> 
> I am not sure what you are talking about here...
> 
> The discussion is about a non working extension for our Wiki server.
> 
> The repository is for our Media Wiki extension?
> 
> 2 totally different things...
> 
> Matthias
> 
> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> > I have created the Repository for MWiki extensions with my Proposed name:
> >
> > openoffice-mwiki-ext.git
> > 
> >
> > It is ready to add our MWiki extensions.
> >
> >
> > On 10.12.20 20:35, Keith N. McKenna wrote:
> >> On 12/9/2020 5:38 PM, Marcus wrote:
> >>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>  How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
> 
>  We could do the same for the forums customizations.
> 
>  So we have more control over our support code.
> >>> +1
> >>> This increases the chance that also others can have a look and give
> >>> some
> >>> hints when problems arise.
> >>>
> >>> Marcus
> >>>
> >> +1
> >>
> >> Keith
> >>>
>  On 09.12.20 18:24, Dick Groskamp wrote:
> > On 2020/12/09 11:34:03, Carl Marcum  wrote:
> >> Hi Dick,
> >>
> >> I have copied it out and it's contents are below.
> >>
> >> It should be in github or svn but I haven't had time to do anything
> >> with it.
> >>
> >> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >>> On 2020/12/08 18:56:25, Carl Marcum  wrote:
>  There are still hundreds of broken pages in the dev guide.
>  Yes it seems to be idls and ildm tags.
> 
>  There is a new upgraded VM setup for the wiki waiting to get
>  changed to
>  but I had hoped to look into before it get switched over.
>  But I have had limited time and I haven't been able to do any
>  testing
>  with it since the URL is being redirected.
>  I don't know anything about MediaWiki extensions, yet anyway :)
> 
>  The Infra ticket for our VM is [1].
> 
>  The only place I know where the code is in the current wiki under:
>  extensions/OOoIDLtags/OOoIDLtags.php
> 
> 
>  [1] https://issues.apache.org/jira/browse/INFRA-20339
> 
>  Best regards,
>  Carl
> 
> 
>  -
> 
>  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>  For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
> >>> Carl, thanks i will check into it.
> >>>
> >>> Is it possible to export/copy the IDLTags extension from the MWiki
> >>> to a more accessible place ?
> >>> That way it might be accessible for editing or reversed
> >>> engineering. I think for now it is not reachable.
> >>>
> >>>
> >> The filename is OOoIDLtags.php
> >> 
> >>  >> /**
> >>     * IDL Tag extension
> >>     * The IDLTagExtension was written to manage the IDL links in the
> >> OpenOffice.org Developer's Guide.
> >>     * The extension converts Java paths to links back to the
> >> online IDL
> >> documentation.
> >>     * @version 1.0.2
> >>     * @link
> >> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
> >>     */
> >>
> >> if ( !defined( 'MEDIAWIKI' ) ) {
> >>        die( 'This file is a MediaWiki extension, it is not a
> >> valid entry
> >> point' );
> >> }
> >>
> >> // Extension credits that will show up on Special:Version
> >> $wgExtensionCredits['parserhook'][] = array(
> >>        'name' => 'IDL Tags',
> >>        'version' => '1.0.2',
> >>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> >>        'description' => 'Manage the IDL links in the OOo Dev
> >> Guide ',
> >>        'url' =>
> >> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> >> );
> >>
> >> global $wgExtIDLtags;
> >> $wgExtIDLtags   = new RenderIDLtags;
> >> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
> >>
> >> class RenderIDLtags {
> >>
> >>        function oooIDLTags() {
> >>            global $wgParser;
> >>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
> >> ) );
> >>            $wgParser->setHook( 'idlm', array( &$this,
> >> 'renderIDLM' ) );
> >>            $wgParser->setHook( 'idls', array( &$this,
> >> 'renderIDLS' ) );
> >>            $wgParser->setHook( 'idlmodule', array( &$this,
> >> 'renderIDLMODULE' ) );
> >>            $wgParser->setHook( 'idltopic', array( &$this,
> >> 'renderIDLTOPIC'
> >> ) );
> >>        }
> >>
> >>        function renderIDL( $input, $args, $parser ) {
> >>            $parser->disableCache();
> >>        

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Matthias Seidel]

Hi Peter,

I am not sure what you are talking about here...

The discussion is about a non working extension for our Wiki server.

The repository is for our Media Wiki extension?

2 totally different things...

Matthias

Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> I have created the Repository for MWiki extensions with my Proposed name:
>
> openoffice-mwiki-ext.git
> 
>
> It is ready to add our MWiki extensions.
>
>
> On 10.12.20 20:35, Keith N. McKenna wrote:
>> On 12/9/2020 5:38 PM, Marcus wrote:
>>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
 How about we create a OpenOffice-Mwiki-ext Repo in gitbox?

 We could do the same for the forums customizations.

 So we have more control over our support code.
>>> +1
>>> This increases the chance that also others can have a look and give
>>> some
>>> hints when problems arise.
>>>
>>> Marcus
>>>
>> +1
>>
>> Keith
>>>
 On 09.12.20 18:24, Dick Groskamp wrote:
> On 2020/12/09 11:34:03, Carl Marcum  wrote:
>> Hi Dick,
>>
>> I have copied it out and it's contents are below.
>>
>> It should be in github or svn but I haven't had time to do anything
>> with it.
>>
>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
>>> On 2020/12/08 18:56:25, Carl Marcum  wrote:
 There are still hundreds of broken pages in the dev guide.
 Yes it seems to be idls and ildm tags.

 There is a new upgraded VM setup for the wiki waiting to get
 changed to
 but I had hoped to look into before it get switched over.
 But I have had limited time and I haven't been able to do any
 testing
 with it since the URL is being redirected.
 I don't know anything about MediaWiki extensions, yet anyway :)

 The Infra ticket for our VM is [1].

 The only place I know where the code is in the current wiki under:
 extensions/OOoIDLtags/OOoIDLtags.php


 [1] https://issues.apache.org/jira/browse/INFRA-20339

 Best regards,
 Carl


 -

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


>>> Carl, thanks i will check into it.
>>>
>>> Is it possible to export/copy the IDLTags extension from the MWiki
>>> to a more accessible place ?
>>> That way it might be accessible for editing or reversed
>>> engineering. I think for now it is not reachable.
>>>
>>>
>> The filename is OOoIDLtags.php
>> 
>> > /**
>>     * IDL Tag extension
>>     * The IDLTagExtension was written to manage the IDL links in the
>> OpenOffice.org Developer's Guide.
>>     * The extension converts Java paths to links back to the
>> online IDL
>> documentation.
>>     * @version 1.0.2
>>     * @link
>> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
>>     */
>>
>> if ( !defined( 'MEDIAWIKI' ) ) {
>>        die( 'This file is a MediaWiki extension, it is not a
>> valid entry
>> point' );
>> }
>>
>> // Extension credits that will show up on Special:Version
>> $wgExtensionCredits['parserhook'][] = array(
>>        'name' => 'IDL Tags',
>>        'version' => '1.0.2',
>>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>>        'description' => 'Manage the IDL links in the OOo Dev
>> Guide ',
>>        'url' =>
>> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
>> );
>>
>> global $wgExtIDLtags;
>> $wgExtIDLtags   = new RenderIDLtags;
>> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
>>
>> class RenderIDLtags {
>>
>>        function oooIDLTags() {
>>            global $wgParser;
>>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
>> ) );
>>            $wgParser->setHook( 'idlm', array( &$this,
>> 'renderIDLM' ) );
>>            $wgParser->setHook( 'idls', array( &$this,
>> 'renderIDLS' ) );
>>            $wgParser->setHook( 'idlmodule', array( &$this,
>> 'renderIDLMODULE' ) );
>>            $wgParser->setHook( 'idltopic', array( &$this,
>> 'renderIDLTOPIC'
>> ) );
>>        }
>>
>>        function renderIDL( $input, $args, $parser ) {
>>            $parser->disableCache();
>>            $output = $parser->recursiveTagParse( $input );
>>            $output = '> href="http://api.openoffice.org/docs/common/ref/' .
>>                str_replace ('.','/',$output).'.html" class="external
>> text">'.$output.'';
>>            return $output;
>>        }
>>
>>        function renderIDLM( $input

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Peter Kovacs]

I have created the Repository for MWiki extensions with my Proposed name:

openoffice-mwiki-ext.git 



It is ready to add our MWiki extensions.


On 10.12.20 20:35, Keith N. McKenna wrote:

On 12/9/2020 5:38 PM, Marcus wrote:

Am 09.12.20 um 18:35 schrieb Peter Kovacs:

How about we create a OpenOffice-Mwiki-ext Repo in gitbox?

We could do the same for the forums customizations.

So we have more control over our support code.

+1
This increases the chance that also others can have a look and give some
hints when problems arise.

Marcus


+1

Keith



On 09.12.20 18:24, Dick Groskamp wrote:

On 2020/12/09 11:34:03, Carl Marcum  wrote:

Hi Dick,

I have copied it out and it's contents are below.

It should be in github or svn but I haven't had time to do anything
with it.

On 12/9/20 5:42 AM, Dick Groskamp wrote:

On 2020/12/08 18:56:25, Carl Marcum  wrote:

There are still hundreds of broken pages in the dev guide.
Yes it seems to be idls and ildm tags.

There is a new upgraded VM setup for the wiki waiting to get
changed to
but I had hoped to look into before it get switched over.
But I have had limited time and I haven't been able to do any testing
with it since the URL is being redirected.
I don't know anything about MediaWiki extensions, yet anyway :)

The Infra ticket for our VM is [1].

The only place I know where the code is in the current wiki under:
extensions/OOoIDLtags/OOoIDLtags.php


[1] https://issues.apache.org/jira/browse/INFRA-20339

Best regards,
Carl


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



Carl, thanks i will check into it.

Is it possible to export/copy the IDLTags extension from the MWiki
to a more accessible place ?
That way it might be accessible for editing or reversed
engineering. I think for now it is not reachable.



The filename is OOoIDLtags.php

http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
    */

if ( !defined( 'MEDIAWIKI' ) ) {
       die( 'This file is a MediaWiki extension, it is not a valid entry
point' );
}

// Extension credits that will show up on Special:Version
$wgExtensionCredits['parserhook'][] = array(
       'name' => 'IDL Tags',
       'version' => '1.0.2',
       'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
       'description' => 'Manage the IDL links in the OOo Dev Guide ',
       'url' =>
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);

global $wgExtIDLtags;
$wgExtIDLtags   = new RenderIDLtags;
$wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );

class RenderIDLtags {

       function oooIDLTags() {
           global $wgParser;
           $wgParser->setHook( 'idl', array( &$this, 'renderIDL' ) );
           $wgParser->setHook( 'idlm', array( &$this, 'renderIDLM' ) );
           $wgParser->setHook( 'idls', array( &$this, 'renderIDLS' ) );
           $wgParser->setHook( 'idlmodule', array( &$this,
'renderIDLMODULE' ) );
           $wgParser->setHook( 'idltopic', array( &$this,
'renderIDLTOPIC'
) );
       }

       function renderIDL( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               str_replace ('.','/',$output).'.html" class="external
text">'.$output.'';
           return $output;
       }

       function renderIDLM( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $page = ereg_replace ('\.','/',$output);
           $anchor = ereg_replace (':','.html#',$page);
           $function = ereg_replace ('^.*:','',$page);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               $anchor.'" class="external text">'.$function.'';
           return $output;
       }

       function renderIDLS( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $function = ereg_replace ('^.*\.','',$output);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               ereg_replace ('\.','/',$output).'.html" class="external
text">'.$function.'';
           return $output;
       }

       function renderIDLMODULE( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $function = ereg_replace ('^.*\.','',$output);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               ereg_replace ('\.','/',$output).'/module-ix.html"
class="external text">'.$output.'';
           return $output;
       }

       function renderIDLTOPIC( $input, $args, $parser ) {
           $parser->disableCache();
           return '';
       }
}


Be

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/10 23:12:06, Carl Marcum  wrote: 
> Hi Dick,
> 
> On 12/10/20 8:27 AM, Dick Groskamp wrote:
> >
> > On 2020/12/10 01:09:49, Carl Marcum  wrote:
> >> Hi Arrigo,
> >>
> >>
> >> On 12/9/20 2:51 PM, Arrigo Marchiori wrote:
> >>> Hello,
> >>>
> >>> trying a shot in the dark...
> >>>
> >>> On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> >>>
>  On 2020/12/09 11:34:03, Carl Marcum  wrote:
> > Hi Dick,
> >
> > I have copied it out and it's contents are below.
> >
> > On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >> On 2020/12/08 18:56:25, Carl Marcum  wrote:
> >>> There are still hundreds of broken pages in the dev guide.
> >>> Yes it seems to be idls and ildm tags.
> >>> [...]
> >    function renderIDLM( $input, $args, $parser ) {
> >        $parser->disableCache();
> >        $output = $parser->recursiveTagParse( $input );
> >        $page = ereg_replace ('\.','/',$output);
> >        $anchor = ereg_replace (':','.html#',$page);
> >        $function = ereg_replace ('^.*:','',$page);
> >>> [...]
>  Thanks,
>  now I only have to figure out why it isn't working :-)
> >>> Could the culprit be the deprecated ereg_replace function, that was
> >>> removed since PHP 7.0.0?
> >>>
> >>> Pointers:
> >>> https://www.php.net/manual/en/function.ereg-replace.php
> >>> https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> >>>
> >>> HTH,
> >> Thanks for the tip.
> >>
> >> If I can get the redirect removed from the new mwiki VM I can try that.
> >>
> >> Best regards,
> >> Carl
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> > Carl,  would it then make sense to stop changing the tags to hardcoded urls 
> > and wait to see if replacing ereg_replace works?
> > If that should be a yes should I than revert the changes I have already 
> > made ?
> >
> > I think Rigo has a point since we use PHP 7.0.33 on the wiki, which has 
> > ereg_replace removed.
> > If it won't work I can always resume changing again.
> >
> 
> I started down this road back in May [1] and soon discovered there are 
> hundreds of affected pages in the dev guide alone.
> If I thought we couldn't fix it I would say go ahead.
> 
> I found out at the same time a new VM was being provisioned for us with 
> an updated OS so I have access to that machine to look into this.
> I ran into a roadblock in that the URL I should be able to see the test 
> wiki is being redirected.
> 
> I've been occupied with other things in the meantime at let it slide but 
> now that the subject has come up again it would be good to put it to 
> rest one way or another.
> Last night I put in a ticket to have the redirect removed so I can see 
> the results of any changes.
> 
> I can change that method call and see if that works once I can see the 
> test wiki.
> I'm hesitant to make the change live on our production instance however.
> 
> [1] 
> https://lists.apache.org/thread.html/rda96615951628eb0fafc004a8f0aa1177559fd3b5d9c9f30ce9cebc9%40%3Cdev.openoffice.apache.org%3E
> 
> Best regards,
> Carl
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
Carl,
thanks for the response. I must have been hibernating in May. Missed that 
completely. ;-)

I'm no tech or programmer but replacing ereg_replace by pereg_replace (which 
should work on > PHP 7.0.*) seems to be the best and fastest way to correct 
this.

Since IDLTags is "just" a way to put rendering or format on to the tags it 
probably won't affect the actual text in the wiki. No big impact on the 
existing wiki I think. Just my 2 cents

If that works, everything is OK and we don't have to change anything more.
If it fails we can put the old OOoIDLTags.php back I should think. Then we 
should replace all the failing tags ,  and .  
seems to do nothing.

I will look into pereg_replace today to see if I can help make it function 
again.
Let me know if I can do anything else to help.

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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Carl Marcum]

Hi Dick,

On 12/10/20 8:27 AM, Dick Groskamp wrote:


On 2020/12/10 01:09:49, Carl Marcum  wrote:

Hi Arrigo,


On 12/9/20 2:51 PM, Arrigo Marchiori wrote:

Hello,

trying a shot in the dark...

On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:


On 2020/12/09 11:34:03, Carl Marcum  wrote:

Hi Dick,

I have copied it out and it's contents are below.

On 12/9/20 5:42 AM, Dick Groskamp wrote:

On 2020/12/08 18:56:25, Carl Marcum  wrote:

There are still hundreds of broken pages in the dev guide.
Yes it seems to be idls and ildm tags.

[...]

       function renderIDLM( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $page = ereg_replace ('\.','/',$output);
           $anchor = ereg_replace (':','.html#',$page);
           $function = ereg_replace ('^.*:','',$page);

[...]

Thanks,
now I only have to figure out why it isn't working :-)

Could the culprit be the deprecated ereg_replace function, that was
removed since PHP 7.0.0?

Pointers:
https://www.php.net/manual/en/function.ereg-replace.php
https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace

HTH,

Thanks for the tip.

If I can get the redirect removed from the new mwiki VM I can try that.

Best regards,
Carl


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


Carl,  would it then make sense to stop changing the tags to hardcoded urls and 
wait to see if replacing ereg_replace works?
If that should be a yes should I than revert the changes I have already made ?

I think Rigo has a point since we use PHP 7.0.33 on the wiki, which has 
ereg_replace removed.
If it won't work I can always resume changing again.



I started down this road back in May [1] and soon discovered there are 
hundreds of affected pages in the dev guide alone.

If I thought we couldn't fix it I would say go ahead.

I found out at the same time a new VM was being provisioned for us with 
an updated OS so I have access to that machine to look into this.
I ran into a roadblock in that the URL I should be able to see the test 
wiki is being redirected.


I've been occupied with other things in the meantime at let it slide but 
now that the subject has come up again it would be good to put it to 
rest one way or another.
Last night I put in a ticket to have the redirect removed so I can see 
the results of any changes.


I can change that method call and see if that works once I can see the 
test wiki.

I'm hesitant to make the change live on our production instance however.

[1] 
https://lists.apache.org/thread.html/rda96615951628eb0fafc004a8f0aa1177559fd3b5d9c9f30ce9cebc9%40%3Cdev.openoffice.apache.org%3E


Best regards,
Carl


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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Keith N. McKenna]

On 12/9/2020 5:38 PM, Marcus wrote:
> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>> How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
>>
>> We could do the same for the forums customizations.
>>
>> So we have more control over our support code.
> 
> +1
> This increases the chance that also others can have a look and give some
> hints when problems arise.
> 
> Marcus
> 

+1

Keith
> 
> 
>> On 09.12.20 18:24, Dick Groskamp wrote:
>>>
>>> On 2020/12/09 11:34:03, Carl Marcum  wrote:
 Hi Dick,

 I have copied it out and it's contents are below.

 It should be in github or svn but I haven't had time to do anything
 with it.

 On 12/9/20 5:42 AM, Dick Groskamp wrote:
> On 2020/12/08 18:56:25, Carl Marcum  wrote:
>> There are still hundreds of broken pages in the dev guide.
>> Yes it seems to be idls and ildm tags.
>>
>> There is a new upgraded VM setup for the wiki waiting to get
>> changed to
>> but I had hoped to look into before it get switched over.
>> But I have had limited time and I haven't been able to do any testing
>> with it since the URL is being redirected.
>> I don't know anything about MediaWiki extensions, yet anyway :)
>>
>> The Infra ticket for our VM is [1].
>>
>> The only place I know where the code is in the current wiki under:
>> extensions/OOoIDLtags/OOoIDLtags.php
>>
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-20339
>>
>> Best regards,
>> Carl
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
> Carl, thanks i will check into it.
>
> Is it possible to export/copy the IDLTags extension from the MWiki
> to a more accessible place ?
> That way it might be accessible for editing or reversed
> engineering. I think for now it is not reachable.
>
>
 The filename is OOoIDLtags.php
 
 >>> /**
    * IDL Tag extension
    * The IDLTagExtension was written to manage the IDL links in the
 OpenOffice.org Developer's Guide.
    * The extension converts Java paths to links back to the online IDL
 documentation.
    * @version 1.0.2
    * @link
 http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
    */

 if ( !defined( 'MEDIAWIKI' ) ) {
       die( 'This file is a MediaWiki extension, it is not a valid entry
 point' );
 }

 // Extension credits that will show up on Special:Version
 $wgExtensionCredits['parserhook'][] = array(
       'name' => 'IDL Tags',
       'version' => '1.0.2',
       'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
       'description' => 'Manage the IDL links in the OOo Dev Guide ',
       'url' =>
 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
 );

 global $wgExtIDLtags;
 $wgExtIDLtags   = new RenderIDLtags;
 $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );

 class RenderIDLtags {

       function oooIDLTags() {
           global $wgParser;
           $wgParser->setHook( 'idl', array( &$this, 'renderIDL' ) );
           $wgParser->setHook( 'idlm', array( &$this, 'renderIDLM' ) );
           $wgParser->setHook( 'idls', array( &$this, 'renderIDLS' ) );
           $wgParser->setHook( 'idlmodule', array( &$this,
 'renderIDLMODULE' ) );
           $wgParser->setHook( 'idltopic', array( &$this,
 'renderIDLTOPIC'
 ) );
       }

       function renderIDL( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $output = '>>> href="http://api.openoffice.org/docs/common/ref/' .
               str_replace ('.','/',$output).'.html" class="external
 text">'.$output.'';
           return $output;
       }

       function renderIDLM( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $page = ereg_replace ('\.','/',$output);
           $anchor = ereg_replace (':','.html#',$page);
           $function = ereg_replace ('^.*:','',$page);
           $output = '>>> href="http://api.openoffice.org/docs/common/ref/' .
               $anchor.'" class="external text">'.$function.'';
           return $output;
       }

       function renderIDLS( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $function = ereg_replace ('^.*\.','',$output);
           $output = '>>> href="http://api.openoffice.org/docs/common/ref/' .
               ereg_replace ('\.','/',$outp

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/10 13:57:39, Dick Groskamp  wrote: 
> 
> 
> On 2020/12/09 19:51:57, Arrigo Marchiori  wrote: 
> > Hello,
> > 
> > trying a shot in the dark...
> > 
> > On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> > 
> > > On 2020/12/09 11:34:03, Carl Marcum  wrote: 
> > > > Hi Dick,
> > > > 
> > > > I have copied it out and it's contents are below.
> > > > 
> > > > On 12/9/20 5:42 AM, Dick Groskamp wrote:
> > > > >
> > > > > On 2020/12/08 18:56:25, Carl Marcum  wrote:
> > > > >> There are still hundreds of broken pages in the dev guide.
> > > > >> Yes it seems to be idls and ildm tags.
> > 
> > [...]
> > > >      function renderIDLM( $input, $args, $parser ) {
> > > >          $parser->disableCache();
> > > >          $output = $parser->recursiveTagParse( $input );
> > > >          $page = ereg_replace ('\.','/',$output);
> > > >          $anchor = ereg_replace (':','.html#',$page);
> > > >          $function = ereg_replace ('^.*:','',$page);
> > [...]
> > > Thanks,
> > > now I only have to figure out why it isn't working :-)
> > 
> > Could the culprit be the deprecated ereg_replace function, that was
> > removed since PHP 7.0.0?
> > 
> > Pointers:
> > https://www.php.net/manual/en/function.ereg-replace.php
> > https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> > 
> > HTH,
> > -- 
> > rigo
> > 
> > http://rigo.altervista.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> > 
> That might probably also be the reason why the tag   does work. It uses 
> str_replace and NOT ereg_replace.
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
Just tested with a page with just one  tag .
Changing it to  renders the page correctly.
Changing to  does NOT render the page, nor does 

Seems to me that ereg_replace is the culprit, but I'm no developer, nor 
technician

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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/09 19:51:57, Arrigo Marchiori  wrote: 
> Hello,
> 
> trying a shot in the dark...
> 
> On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> 
> > On 2020/12/09 11:34:03, Carl Marcum  wrote: 
> > > Hi Dick,
> > > 
> > > I have copied it out and it's contents are below.
> > > 
> > > On 12/9/20 5:42 AM, Dick Groskamp wrote:
> > > >
> > > > On 2020/12/08 18:56:25, Carl Marcum  wrote:
> > > >> There are still hundreds of broken pages in the dev guide.
> > > >> Yes it seems to be idls and ildm tags.
> 
> [...]
> > >      function renderIDLM( $input, $args, $parser ) {
> > >          $parser->disableCache();
> > >          $output = $parser->recursiveTagParse( $input );
> > >          $page = ereg_replace ('\.','/',$output);
> > >          $anchor = ereg_replace (':','.html#',$page);
> > >          $function = ereg_replace ('^.*:','',$page);
> [...]
> > Thanks,
> > now I only have to figure out why it isn't working :-)
> 
> Could the culprit be the deprecated ereg_replace function, that was
> removed since PHP 7.0.0?
> 
> Pointers:
> https://www.php.net/manual/en/function.ereg-replace.php
> https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> 
> HTH,
> -- 
> rigo
> 
> http://rigo.altervista.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
That might probably also be the reason why the tag   does work. It uses 
str_replace and NOT ereg_replace.



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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

[Dick Groskamp]

On 2020/12/10 01:09:49, Carl Marcum  wrote: 
> Hi Arrigo,
> 
> 
> On 12/9/20 2:51 PM, Arrigo Marchiori wrote:
> > Hello,
> >
> > trying a shot in the dark...
> >
> > On Wed, Dec 09, 2020 at 05:24:41PM -, Dick Groskamp wrote:
> >
> >> On 2020/12/09 11:34:03, Carl Marcum  wrote:
> >>> Hi Dick,
> >>>
> >>> I have copied it out and it's contents are below.
> >>>
> >>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
>  On 2020/12/08 18:56:25, Carl Marcum  wrote:
> > There are still hundreds of broken pages in the dev guide.
> > Yes it seems to be idls and ildm tags.
> > [...]
> >>>       function renderIDLM( $input, $args, $parser ) {
> >>>           $parser->disableCache();
> >>>           $output = $parser->recursiveTagParse( $input );
> >>>           $page = ereg_replace ('\.','/',$output);
> >>>           $anchor = ereg_replace (':','.html#',$page);
> >>>           $function = ereg_replace ('^.*:','',$page);
> > [...]
> >> Thanks,
> >> now I only have to figure out why it isn't working :-)
> > Could the culprit be the deprecated ereg_replace function, that was
> > removed since PHP 7.0.0?
> >
> > Pointers:
> > https://www.php.net/manual/en/function.ereg-replace.php
> > https://stackoverflow.com/questions/3649574/replace-ereg-replace-with-preg-replace
> >
> > HTH,
> Thanks for the tip.
> 
> If I can get the redirect removed from the new mwiki VM I can try that.
> 
> Best regards,
> Carl
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
Carl,  would it then make sense to stop changing the tags to hardcoded urls and 
wait to see if replacing ereg_replace works?
If that should be a yes should I than revert the changes I have already made ?

I think Rigo has a point since we use PHP 7.0.33 on the wiki, which has 
ereg_replace removed.
If it won't work I can always resume changing again.

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