Re: Request for PR reviews

[Peter Kovacs]

I am sorry. I am just to slow at the moment.. I hope tonight I find time but I 
am not sure. It depends how stressful my working day is. 
Maybe we are to view that look at PRs. And do 4 eye principle.


Am 22. Februar 2021 18:24:07 MEZ schrieb Matthias Seidel 
:
>Hi Arrigo,
>
>Am 21.02.21 um 16:01 schrieb Arrigo Marchiori:
>> Dear All,
>>
>> please help me review and finalize PR 122:
>> https://github.com/apache/openoffice/pull/122
>> as it should fix a top-priority AOO bug, and hopefully help us spot
>> other similar problems in the future.
>>
>> Moreover, I would really like to merge PR 111:
>> https://github.com/apache/openoffice/pull/111
>> because I do work on openSUSE and I cannot build AOO without it.  I
>> dare proposing it as a "Good Thing" for me, and a "Mostly Harmless"
>> change for anyone else. FWIW I could build 4.1.9 for Linux on the
>> CentOS 5 version in both 32-bit and 64-bit versions with that commit
>> included.
>>
>> I'll be more than happy to answer anybody's concerns over both PR's
>> either on GitHub, or on this list.
>
>Yes, I am a bit puzzled that PRs are so neglected.
>They are a great tool and can really speed up things.
>
>I have merged some of your PRs, but only those I could build and test
>against the (fixed) problem.
>Commenting on code isn't something I can do... ;-)
>
>Regards,
>
>   Matthias
>
>>
>> Thank you in advance and best regards,

Re: Priority Issues: (was: How to cope with duplicate attributes in XML tags )

[Peter]

Sure pick one. No issues I have wrote more on purpose. 

Am 22. Februar 2021 18:53:02 MEZ schrieb Arrigo Marchiori 
:
>Hello Peter,
>
>thank you very much for replying.
>
>On Sun, Feb 21, 2021 at 01:40:15AM +0100, Peter Kovacs wrote:
>
>> I would like to answer the priority list first.
>> 
>> Currently I have following Issues on my mind. The list may not be
>complete
>> or others may have other Opinions, which is fine.
>> 
>> 
>> On 07.02.21 21:51, Arrigo Marchiori wrote:
>> > If we approve it, I will surely need your indication (as per a
>> > previous thread on this ML) about the next "high priority issue" to
>> > address.
>> 
>> Next:
>> 
>> File corruption:
>> 
>> https://bz.apache.org/ooo/show_bug.cgi?id=126846 and
>> https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=1532
>
>I'm starting with the related report
>https://bz.apache.org/ooo/show_bug.cgi?id=126869
>There are too many and... I have to choose one ;-)
>
>Best regards,
>-- 
>Arrigo
>
>http://rigo.altervista.org
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Re: [CONF] Apache OpenOffice Community > AOO 4.1.9 Release Notes (de)

[Marcus]

Hi Joerg,

you have started this page to translate the release notes into German. 
Do you still have an interest to do so or should others take over?


Thanks

Marcus



Am 23.02.21 um 20:10 schrieb Keith McKenna (Confluence):

There's *1 new edit* on this page

	AOO 4.1.9 Release Notes (de) 
 
	

Keith McKenna edited this page

Here's the version comment

Keith McKenna edited at 08:09 PM 
 
	

Removed the draft notice

Here's what changed:

Das ist ein Entwurf, AOO 4.1.9 ist noch nicht veröffentlicht



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

Re: Request for PR reviews

[Dylan Pham]

Hello,

I think the wording on the Buildbot info page should be changed from
"slaves" to something like "worker" or something like that in order to be
culturally sensitive in this day and age.

https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info


my 2c,
Dylan

On Mon, Feb 22, 2021 at 10:39 AM Matthias Seidel 
wrote:

> Hi Arrigo,
>
> Am 22.02.21 um 19:28 schrieb Arrigo Marchiori:
> > Hello Matthias,
> >
> > On Mon, Feb 22, 2021 at 06:24:07PM +0100, Matthias Seidel wrote:
> >
> >> Hi Arrigo,
> >>
> >> Am 21.02.21 um 16:01 schrieb Arrigo Marchiori:
> >>> Dear All,
> >>>
> >>> please help me review and finalize PR 122:
> >>> https://github.com/apache/openoffice/pull/122
> >>> as it should fix a top-priority AOO bug, and hopefully help us spot
> >>> other similar problems in the future.
> >>>
> >>> Moreover, I would really like to merge PR 111:
> >>> https://github.com/apache/openoffice/pull/111
> >>> because I do work on openSUSE and I cannot build AOO without it.  I
> >>> dare proposing it as a "Good Thing" for me, and a "Mostly Harmless"
> >>> change for anyone else. FWIW I could build 4.1.9 for Linux on the
> >>> CentOS 5 version in both 32-bit and 64-bit versions with that commit
> >>> included.
> >>>
> >>> I'll be more than happy to answer anybody's concerns over both PR's
> >>> either on GitHub, or on this list.
> >> Yes, I am a bit puzzled that PRs are so neglected.
> >> They are a great tool and can really speed up things.
> >>
> >> I have merged some of your PRs, but only those I could build and test
> >> against the (fixed) problem.
> > That's very kind of you.  And I did receive some comments from other
> > people as well, that I appreciate.
> >
> > But can we establish a sort of ``emergency exit'' in the
> > "commit-then-review" process, like ``if no-one comments a PR it could
> > be merged in X time''? A sort of lazy consensus?
> I am not sure, since I really can't evaluate the quality of the code
> (old and new one).
> >
> > Personally, I would really like to see the development branches go
> > "live" with nightly builds. I see lots of people available to report
> > bugs and test fixes, and I cannot submit anything to them for testing,
> > mostly because I cannot build Windows releases!
>
> Regarding Windows builds:
>
> We have nightly builds of trunk and weekly builds for AOO42X:
>
> https://www.openoffice.org/download/devbuilds.html
>
> And you can always find my personal Test Builds here:
>
> https://home.apache.org/~mseidel/AOO-builds/
>
> If you are interested in building for Windows, I would be happy to help
> you with it.
> After all these years, I am still the only one that does release builds
> for Windows and is able to sign them. Just for redundancy it would be
> great to have a second person available.
>
> Regards,
>
>Matthias
>
> >
> > Thank you and best regards,
>
>

Re: Request for PR reviews

[Dave Fisher]

> On Feb 23, 2021, at 9:18 PM, Dylan Pham  wrote:
> 
> Hello,
> 
> I think the wording on the Buildbot info page should be changed from
> "slaves" to something like "worker" or something like that in order to be
> culturally sensitive in this day and age.

We will have to see if we can get this changed. It’s a Foundation resource that 
uses other’s software. Please be patient and don’t take lack of change as this 
project not being sensitive. Please keep in mind that we are volunteers her.

You should notice that OpenOffice is using “main” and “trunk” for the default 
branch in our Git Repositories. We’ve made sure not to use “master”.

Regards,
Dave

> 
> https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info
> 
> 
> my 2c,
> Dylan
> 
> On Mon, Feb 22, 2021 at 10:39 AM Matthias Seidel 
> wrote:
> 
>> Hi Arrigo,
>> 
>> Am 22.02.21 um 19:28 schrieb Arrigo Marchiori:
>>> Hello Matthias,
>>> 
>>> On Mon, Feb 22, 2021 at 06:24:07PM +0100, Matthias Seidel wrote:
>>> 
 Hi Arrigo,
 
 Am 21.02.21 um 16:01 schrieb Arrigo Marchiori:
> Dear All,
> 
> please help me review and finalize PR 122:
> https://github.com/apache/openoffice/pull/122
> as it should fix a top-priority AOO bug, and hopefully help us spot
> other similar problems in the future.
> 
> Moreover, I would really like to merge PR 111:
> https://github.com/apache/openoffice/pull/111
> because I do work on openSUSE and I cannot build AOO without it.  I
> dare proposing it as a "Good Thing" for me, and a "Mostly Harmless"
> change for anyone else. FWIW I could build 4.1.9 for Linux on the
> CentOS 5 version in both 32-bit and 64-bit versions with that commit
> included.
> 
> I'll be more than happy to answer anybody's concerns over both PR's
> either on GitHub, or on this list.
 Yes, I am a bit puzzled that PRs are so neglected.
 They are a great tool and can really speed up things.
 
 I have merged some of your PRs, but only those I could build and test
 against the (fixed) problem.
>>> That's very kind of you.  And I did receive some comments from other
>>> people as well, that I appreciate.
>>> 
>>> But can we establish a sort of ``emergency exit'' in the
>>> "commit-then-review" process, like ``if no-one comments a PR it could
>>> be merged in X time''? A sort of lazy consensus?
>> I am not sure, since I really can't evaluate the quality of the code
>> (old and new one).
>>> 
>>> Personally, I would really like to see the development branches go
>>> "live" with nightly builds. I see lots of people available to report
>>> bugs and test fixes, and I cannot submit anything to them for testing,
>>> mostly because I cannot build Windows releases!
>> 
>> Regarding Windows builds:
>> 
>> We have nightly builds of trunk and weekly builds for AOO42X:
>> 
>> https://www.openoffice.org/download/devbuilds.html
>> 
>> And you can always find my personal Test Builds here:
>> 
>> https://home.apache.org/~mseidel/AOO-builds/
>> 
>> If you are interested in building for Windows, I would be happy to help
>> you with it.
>> After all these years, I am still the only one that does release builds
>> for Windows and is able to sign them. Just for redundancy it would be
>> great to have a second person available.
>> 
>> Regards,
>> 
>>   Matthias
>> 
>>> 
>>> Thank you and best regards,
>> 
>> 


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

Adding Open Office to new Apple Mini

[Skip Lehman]

Hi, I am not computer savvy.  I'm trying to add Open Office to my new Apple 
Mini computer, version 11.2. Apple won't let me, saying “OpenOffice” cannot be 
opened because the developer cannot be verified." Then it says my macOS cannot 
verify that this app is free from malware.  What to do?

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

photo by text ....

[Storm Gill]

Hello.
I want to insert a photo next to text. as is seen .  All efforts separate the 
text and insert the photo in the middle of it.  I have tried a 2 section table, 
local columns, inserting a photo after editing format, making a pdf with the 
photo scanned and trying to transform that to a .doc, and nothing works.
Please, what can I do to have a photo next to my introduction of self on a 
resume or biography?
Otherwise I love Open Office and loath MS products. 

Keep up the good work, and thank you.
Storm Gill

Re: Request for PR reviews

[Dylan Pham]

Thank you Dave for the clarification.

Dylan

On Tue, Feb 23, 2021 at 9:28 PM Dave Fisher  wrote:

>
>
> > On Feb 23, 2021, at 9:18 PM, Dylan Pham  wrote:
> >
> > Hello,
> >
> > I think the wording on the Buildbot info page should be changed from
> > "slaves" to something like "worker" or something like that in order to be
> > culturally sensitive in this day and age.
>
> We will have to see if we can get this changed. It’s a Foundation resource
> that uses other’s software. Please be patient and don’t take lack of change
> as this project not being sensitive. Please keep in mind that we are
> volunteers her.
>
> You should notice that OpenOffice is using “main” and “trunk” for the
> default branch in our Git Repositories. We’ve made sure not to use “master”.
>
> Regards,
> Dave
>
> >
> > https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info
> >
> >
> > my 2c,
> > Dylan
> >
> > On Mon, Feb 22, 2021 at 10:39 AM Matthias Seidel <
> matthias.sei...@hamburg.de>
> > wrote:
> >
> >> Hi Arrigo,
> >>
> >> Am 22.02.21 um 19:28 schrieb Arrigo Marchiori:
> >>> Hello Matthias,
> >>>
> >>> On Mon, Feb 22, 2021 at 06:24:07PM +0100, Matthias Seidel wrote:
> >>>
>  Hi Arrigo,
> 
>  Am 21.02.21 um 16:01 schrieb Arrigo Marchiori:
> > Dear All,
> >
> > please help me review and finalize PR 122:
> > https://github.com/apache/openoffice/pull/122
> > as it should fix a top-priority AOO bug, and hopefully help us spot
> > other similar problems in the future.
> >
> > Moreover, I would really like to merge PR 111:
> > https://github.com/apache/openoffice/pull/111
> > because I do work on openSUSE and I cannot build AOO without it.  I
> > dare proposing it as a "Good Thing" for me, and a "Mostly Harmless"
> > change for anyone else. FWIW I could build 4.1.9 for Linux on the
> > CentOS 5 version in both 32-bit and 64-bit versions with that commit
> > included.
> >
> > I'll be more than happy to answer anybody's concerns over both PR's
> > either on GitHub, or on this list.
>  Yes, I am a bit puzzled that PRs are so neglected.
>  They are a great tool and can really speed up things.
> 
>  I have merged some of your PRs, but only those I could build and test
>  against the (fixed) problem.
> >>> That's very kind of you.  And I did receive some comments from other
> >>> people as well, that I appreciate.
> >>>
> >>> But can we establish a sort of ``emergency exit'' in the
> >>> "commit-then-review" process, like ``if no-one comments a PR it could
> >>> be merged in X time''? A sort of lazy consensus?
> >> I am not sure, since I really can't evaluate the quality of the code
> >> (old and new one).
> >>>
> >>> Personally, I would really like to see the development branches go
> >>> "live" with nightly builds. I see lots of people available to report
> >>> bugs and test fixes, and I cannot submit anything to them for testing,
> >>> mostly because I cannot build Windows releases!
> >>
> >> Regarding Windows builds:
> >>
> >> We have nightly builds of trunk and weekly builds for AOO42X:
> >>
> >> https://www.openoffice.org/download/devbuilds.html
> >>
> >> And you can always find my personal Test Builds here:
> >>
> >> https://home.apache.org/~mseidel/AOO-builds/
> >>
> >> If you are interested in building for Windows, I would be happy to help
> >> you with it.
> >> After all these years, I am still the only one that does release builds
> >> for Windows and is able to sign them. Just for redundancy it would be
> >> great to have a second person available.
> >>
> >> Regards,
> >>
> >>   Matthias
> >>
> >>>
> >>> Thank you and best regards,
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Adding Open Office to new Apple Mini

[David Robley]

Please read the Mac section, especially the part about Gatekeeper, of 
Instructions for Downloading and Installing Apache OpenOffice 4.0, 4.1 
Versions at 
https://www.openoffice.org/download/common/instructions.html#apple


Note - this sort of problem should be asked on the user list at 
, or at the AOO forum 
https://forum.openoffice.org; this mailing list is for developers.


Since you are not subscribed to this list you may not see all the 
replies to your query. To subscribe to Apache OpenOffice mailing lists 
go to http://openoffice.apache.org/mailing-lists.html


As a courtesy I have forwarded a copy of this reply to you as well as to 
the mailing list. Do Not reply to me personally  - replies to my 
personal email address will be ignored.


On 24/2/21 10:58 am, Skip Lehman wrote:

Hi, I am not computer savvy.  I'm trying to add Open Office to my new Apple Mini 
computer, version 11.2. Apple won't let me, saying “OpenOffice” cannot be opened 
because the developer cannot be verified." Then it says my macOS cannot verify 
that this app is free from malware.  What to do?

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



Cheers
--
David Robley

Useless Invention: Reversible garbage disposal.
 



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