[GitHub] [openoffice] DonLewisFreeBSD commented on pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be

2020-12-18 Thread GitBox


DonLewisFreeBSD commented on pull request #93:
URL: https://github.com/apache/openoffice/pull/93#issuecomment-748416075


   > How about we define a stlport::unique_ptr?
   > We use
   > auto_ptr for older builds and unique_ptr for newer.
   
   They are similar but unique_ptr is not a drop in replacement, otherwise they 
would have kept the same name.  I'm assuming that there would be some amount of 
porting and testing effort involved in switching.
   
   I don't thing gcc is new enough to support unique_ptr for anything older 
than CentOS 7.  I'm pretty sure that we would have to switch to a newer version 
of Visual C++ as well.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



Re: Design Docs?

2020-12-18 Thread Carl Marcum

Hi Steve,

On 12/18/20 8:06 PM, Steve Lubbs wrote:

Hi All,

I asked this question in recruitment but this may be the proper place 
for it.


Is there any design documentation, especially related to structure 
(what are the modules, what is their function, how do they interact, 
etc.), however minimal, that you can point me to to help in wading 
through the code? I'm hoping to avoid reverse engineering the code.


If the answer to my query is available somewhere I should have seen 
it, I apologize.


Thanks in advance,

Steve Lubbs



Maybe one of the developers can point you to better information.
I have found a page for the modules here [1].
And links to specifications here [2].


[1] https://wiki.openoffice.org/wiki/Modules
[2] http://www.openoffice.org/specs/

Best regards,
Carl

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



Design Docs?

2020-12-18 Thread Steve Lubbs

Hi All,

I asked this question in recruitment but this may be the proper place 
for it.


Is there any design documentation, especially related to structure (what 
are the modules, what is their function, how do they interact, etc.), 
however minimal, that you can point me to to help in wading through the 
code? I'm hoping to avoid reverse engineering the code.


If the answer to my query is available somewhere I should have seen it, 
I apologize.


Thanks in advance,

Steve Lubbs



Old build Documentation

2020-12-18 Thread Peter Kovacs

Hello all,

do we still need the documentation description for:

https://www.openoffice.org/dev_docs/source/build_windows_pre638.html

http://www.openoffice.org/tools/dev_docs/build_windows.html

https://wiki.openoffice.org/wiki/Documentation/Building_Guide


I mean, the first link is the first relevant result on my search results 
on duck duck go.


And then you click through the history.

My search words are: OpenOffice windopws build


Can we retire those pages? We have them in the repository if needed.

All the Best

Peter

--
This is the Way! http://www.apache.org/theapacheway/index.html

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



Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-12-18 Thread Matthias Seidel
Am 18.12.20 um 21:09 schrieb Jim Jagielski:
>
>> On Dec 12, 2020, at 5:21 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> I have been able to open docx with your version (en-US) on Big Sur.
>> However, I am not sure if this bug ever applied to 4.2.x.
>>
>> The Extension Manager is still broken. But similar behavior is to be
>> seen in 4.2.x on Windows, so the UNO problem is not mac specific.
>>
> Can you Help->Check For Updates? I always get a
>
> Checking for an update failed.

Yes, update check was broken for me with your latest version.

Haven't checked earlier versions. on mac.

>
> So I'm wondering if the 2 are related?
Maybe, but Extension Manager is also somehow broken on Windows and
update check is working.
>
>
> -
> 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


[GitHub] [openoffice] leginee edited a comment on pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be

2020-12-18 Thread GitBox


leginee edited a comment on pull request #93:
URL: https://github.com/apache/openoffice/pull/93#issuecomment-748299936


   How about we define a stlport::unique_ptr?
   We use
   auto_ptr for older builds and unique_ptr for newer.
   
   but basically I am fine in general with building with gnu++98



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [openoffice] leginee commented on pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be

2020-12-18 Thread GitBox


leginee commented on pull request #93:
URL: https://github.com/apache/openoffice/pull/93#issuecomment-748299936


   How about we define a stlport::unique_ptr?
   We use
   auto_ptr for older builds and unique_ptr for newer.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-12-18 Thread Jim Jagielski



> On Dec 12, 2020, at 5:21 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> I have been able to open docx with your version (en-US) on Big Sur.
> However, I am not sure if this bug ever applied to 4.2.x.
> 
> The Extension Manager is still broken. But similar behavior is to be
> seen in 4.2.x on Windows, so the UNO problem is not mac specific.
> 

Can you Help->Check For Updates? I always get a

Checking for an update failed.

So I'm wondering if the 2 are related?


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



Re: MWiki Developer Guide Blank Pages

2020-12-18 Thread Carl Marcum

Hi Dick,

On 12/18/20 11:25 AM, Dick Groskamp wrote:


On 2020/12/17 23:42:31, Carl Marcum  wrote:

Hi Dick,

On 12/17/20 12:57 PM, Dick Groskamp wrote:

On 2020/12/16 23:53:56, Carl Marcum  wrote:

Hi All,

I think I've fixed the blank pages problem in the Developer Guide.
I've spot checked through all of the spreadsheet pages that had many
broken and they all display now.

Please check any that you have reported and let me know if you find any
that are still blank.

For those interested it was in the OOoIDLtags.php extension and the
solution was pointed out by Arrigo Marchiori as a deprecated method in
new versions of PHP.

So a big thanks to Arrigo!

Thanks,
Carl

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



Just checked the odd 50 pages I worked on this week in case your solution might 
not work.

Guess what.. IT WORKS.

All pages display correct.

Thanks for the fix and your effort, also a big thanks to Rigo for pointing us 
in the right direction.

Did encounter some odd tags  and [IDL: ], but that has nothing to do 
with the solution.
I'll try to find the odd tags and fix them. For now I think all is well,,. 
. as it should be in this times.



And thanks to you for trying to do something to fix it as well.

  From what I can tell from the extension the tags are idl, idlm, idls,
idlmodule, and idltopic [1].

It looks like someone deleted a wiki page about the idl tag extension 8
years ago [2].
Although I don't know if it had any content.

It would be good to have a page about it one day :)

[1] https://github.com/apache/openoffice-mwiki/blob/main/OOoIDLtags.php
[2] http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension


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



Just put up a new page on the wiki
https://wiki.openoffice.org/wiki/MediaWiki_Extension/Extension_IDLTags#IDLTags_extension_for_Mediawiki

Feel free to adjust/add



That was fast.  Nice job and thanks for putting all that together.
I updated the one link I know about that pointed to the old missing page 
here [1].


[1] 
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Contributing_to_the_Developers_Guide#IDL_extension_and_links


Thanks again,
Carl

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



Re: MWiki Developer Guide Blank Pages

2020-12-18 Thread Dick Groskamp



On 2020/12/17 23:42:31, Carl Marcum  wrote: 
> Hi Dick,
> 
> On 12/17/20 12:57 PM, Dick Groskamp wrote:
> >
> > On 2020/12/16 23:53:56, Carl Marcum  wrote:
> >> Hi All,
> >>
> >> I think I've fixed the blank pages problem in the Developer Guide.
> >> I've spot checked through all of the spreadsheet pages that had many
> >> broken and they all display now.
> >>
> >> Please check any that you have reported and let me know if you find any
> >> that are still blank.
> >>
> >> For those interested it was in the OOoIDLtags.php extension and the
> >> solution was pointed out by Arrigo Marchiori as a deprecated method in
> >> new versions of PHP.
> >>
> >> So a big thanks to Arrigo!
> >>
> >> Thanks,
> >> Carl
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
> > Just checked the odd 50 pages I worked on this week in case your solution 
> > might not work.
> >
> > Guess what.. IT WORKS.
> >
> > All pages display correct.
> >
> > Thanks for the fix and your effort, also a big thanks to Rigo for pointing 
> > us in the right direction.
> >
> > Did encounter some odd tags  and [IDL: ], but that has nothing to do 
> > with the solution.
> > I'll try to find the odd tags and fix them. For now I think all is well,,. 
> > . as it should be in this times.
> >
> >
> And thanks to you for trying to do something to fix it as well.
> 
>  From what I can tell from the extension the tags are idl, idlm, idls, 
> idlmodule, and idltopic [1].
> 
> It looks like someone deleted a wiki page about the idl tag extension 8 
> years ago [2].
> Although I don't know if it had any content.
> 
> It would be good to have a page about it one day :)
> 
> [1] https://github.com/apache/openoffice-mwiki/blob/main/OOoIDLtags.php
> [2] http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
Just put up a new page on the wiki
https://wiki.openoffice.org/wiki/MediaWiki_Extension/Extension_IDLTags#IDLTags_extension_for_Mediawiki

Feel free to adjust/add 

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



Re: Does AOO 4.1.8 run under macOS Big Sur?

2020-12-18 Thread Jim Jagielski
Can you try with:

http://home.apache.org/~jim/AOO-builds/

> On Dec 18, 2020, at 8:45 AM, Jim Jagielski  wrote:
> 
> Ahh. that's good info. There is something somewhere that still expects that 
> COMID on macOS
> is s5abi or, at least, !=gcc3. That gives me some hint to what to look for.
> 
>> On Dec 17, 2020, at 11:34 AM, Rony G. Flatscher (Apache)  
>> wrote:
>> 
>> On 14.12.2020 13:33, Jim Jagielski wrote:
 On Dec 12, 2020, at 5:21 AM, Matthias Seidel  
 wrote:
 
 Hi Jim,
 
 I have been able to open docx with your version (en-US) on Big Sur.
 However, I am not sure if this bug ever applied to 4.2.x.
 
 The Extension Manager is still broken. But similar behavior is to be
 seen in 4.2.x on Windows, so the UNO problem is not mac specific.
 
>>> Yes... I am also looking into issues w/ 4.2.0-dev and check for updates 
>>> (main level)
>> 
>> Ah, o.k. that might explain this. Got a minute so tried to test 4.2 beta 
>> w.r.t. issue 127966  [1]
>> and was not able to get ooRexx functional. When trying to register the oxt 
>> package manually with
>> unopkg, I got this error message:
>> 
>>   wu114216:~ rony$ "/Applications/OpenOffice.app/Contents/program/unopkg" 
>> add -f --shared 
>> /Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt
>>   dyld: Library not loaded: @___URELIB/libuno_cppu.dylib
>> Referenced from: /Applications/OpenOffice.app/Contents/MacOS/uno.bin
>> Reason: image not found
>> 
>> ---rony
>> 
>> [1] MacOS: Current directory wrongly set to root directory "/" for scripts:
>> 
>> 
>> 
> 
> 
> -
> 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: Help with GIT. PR #74 Removed whitespace from files Helpcontent2

2020-12-18 Thread Dave Fisher
+1.

Also, if Mechtilde agrees, these should be “cherry picked” to the 4.2 branch as 
well.

Sent from my iPhone

> On Dec 18, 2020, at 5:28 AM, Peter Kovacs  wrote:
> 
> 
>> On 18.12.20 14:16, Dick Groskamp wrote:
>> I should have mentioned that there was 1 conflict, which I resolved.
>> Should I now again do git commit or not ?
>> 
> In my Opinion you should recommit
> -- 
> This is the Way! http://www.apache.org/theapacheway/index.html
> 
> -
> 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: Does AOO 4.1.8 run under macOS Big Sur?

2020-12-18 Thread Jim Jagielski
Ahh. that's good info. There is something somewhere that still expects that 
COMID on macOS
is s5abi or, at least, !=gcc3. That gives me some hint to what to look for.

> On Dec 17, 2020, at 11:34 AM, Rony G. Flatscher (Apache)  
> wrote:
> 
> On 14.12.2020 13:33, Jim Jagielski wrote:
>>> On Dec 12, 2020, at 5:21 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> I have been able to open docx with your version (en-US) on Big Sur.
>>> However, I am not sure if this bug ever applied to 4.2.x.
>>> 
>>> The Extension Manager is still broken. But similar behavior is to be
>>> seen in 4.2.x on Windows, so the UNO problem is not mac specific.
>>> 
>> Yes... I am also looking into issues w/ 4.2.0-dev and check for updates 
>> (main level)
> 
> Ah, o.k. that might explain this. Got a minute so tried to test 4.2 beta 
> w.r.t. issue 127966  [1]
> and was not able to get ooRexx functional. When trying to register the oxt 
> package manually with
> unopkg, I got this error message:
> 
>wu114216:~ rony$ "/Applications/OpenOffice.app/Contents/program/unopkg" 
> add -f --shared 
> /Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt
>dyld: Library not loaded: @___URELIB/libuno_cppu.dylib
>  Referenced from: /Applications/OpenOffice.app/Contents/MacOS/uno.bin
>  Reason: image not found
> 
> ---rony
> 
> [1] MacOS: Current directory wrongly set to root directory "/" for scripts:
> 
> 
> 


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



Re: Help with GIT. PR #74 Removed whitespace from files Helpcontent2

2020-12-18 Thread Peter Kovacs



On 18.12.20 14:16, Dick Groskamp wrote:

I should have mentioned that there was 1 conflict, which I resolved.
Should I now again do git commit or not ?


In my Opinion you should recommit
--
This is the Way! http://www.apache.org/theapacheway/index.html

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



Re: Help with GIT. PR #74 Removed whitespace from files Helpcontent2

2020-12-18 Thread Dick Groskamp



On 2020/12/18 12:56:06, Dick Groskamp  wrote: 
> Back in February I started working on removing superfluous whitespace between 
> tags  in files in the folder Helpcontent2.
> These files contain the content for the Help files in AOo. In the very past 
> superfluous whitespace was introduced by former participants, probably to 
> make the code in the files more readable.
> 
> However, in the application POOTLE, which we use for translating the Help 
> files, these whitespace needlessly  shows up in the segments to translate. 
> This creates confusion for the translators whether they should remove the 
> whitespace or not. Removing it will instantiate errors in POOTLE.
> 
> Removing these whitespaces would bring the original segments in sync with 
> translated ones in terms of formatting. It should also removed unneccessary 
> warnings/errors in Pootle.  The changes I made are only to text, no coding, 
> also some typo's corrected if I can across them.
> 
> Starting this was also my first attempt to try using GIT. Obviously I made 
> some mistakes, for instance by not incorporating all changes in one commit 
> but acrosse several, but I had no idea how many changes GIT could handle in 
> one time. Now I'm ended up with four outstanding PR's which should contain my 
> changes and are waiting to be incorporated.
> 
> Today I had another look at the changes for PR 74 by fetching upstream trunk 
> to my local fork.
> Then I merged upstream trunk to my local fork.
> Checked out to branch Latest and rebased that.
> 
> Now I need help to continue. 
> How can I integrate my changes in upstream trunk/main/source/helpcontent2
> Can I do that myself or does someone has to approve my PR and have a look at 
> it.
> 
> Or would it be more simple to start over en delte the old PR's ?
> 
> Greetings,
> Dick
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
I should have mentioned that there was 1 conflict, which I resolved.
Should I now again do git commit or not ?

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



Help with GIT. PR #74 Removed whitespace from files Helpcontent2

2020-12-18 Thread Dick Groskamp
Back in February I started working on removing superfluous whitespace between 
tags  in files in the folder Helpcontent2.
These files contain the content for the Help files in AOo. In the very past 
superfluous whitespace was introduced by former participants, probably to make 
the code in the files more readable.

However, in the application POOTLE, which we use for translating the Help 
files, these whitespace needlessly  shows up in the segments to translate. This 
creates confusion for the translators whether they should remove the whitespace 
or not. Removing it will instantiate errors in POOTLE.

Removing these whitespaces would bring the original segments in sync with 
translated ones in terms of formatting. It should also removed unneccessary 
warnings/errors in Pootle.  The changes I made are only to text, no coding, 
also some typo's corrected if I can across them.

Starting this was also my first attempt to try using GIT. Obviously I made some 
mistakes, for instance by not incorporating all changes in one commit but 
acrosse several, but I had no idea how many changes GIT could handle in one 
time. Now I'm ended up with four outstanding PR's which should contain my 
changes and are waiting to be incorporated.

Today I had another look at the changes for PR 74 by fetching upstream trunk to 
my local fork.
Then I merged upstream trunk to my local fork.
Checked out to branch Latest and rebased that.

Now I need help to continue. 
How can I integrate my changes in upstream trunk/main/source/helpcontent2
Can I do that myself or does someone has to approve my PR and have a look at it.

Or would it be more simple to start over en delte the old PR's ?

Greetings,
Dick



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



Re: new person

2020-12-18 Thread Peter Kovacs



On 17.12.20 22:26, Dave Fisher wrote:



On Dec 17, 2020, at 1:16 PM, Bartosz Bartczak  wrote:

Hello developers,

I'm using OO and AOO very long time in IT Businesses.
I think I can "pay my debt" for what you have been doing for me through
the AOO program.

All participation is appreciated.

I don't know what a help we need but I think that can:
- testing "beta" version AOO for windows and Linux many distribution
like Archlinux, Debian, CentOS, maybe enough for this moment and Windows
10 too.
- I see that in distribution Archlinux don't working openoffice even as
a package from AUR repositories.

Example form this day:

$ yaourt -S openoffice

==> Downloading openoffice PKGBUILD from AUR...
x .SRCINFO
x PKGBUILD
kikislater commented on 2020-06-19 05:25

LordofNoob commented on 2020-06-20 09:18

kikislater commented on 2020-06-22 05:11

micwoj92 commented on 2020-11-05
08:32

gameboy commented on 2020-12-08
13:06

openoffice 4.1.7-1  (2019-10-17 11:05)
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> 
==> n

==> openoffice dependencies:
  - freetype2 (already installed)
  - glibc>=2.5 (already installed)
  - gtk2>=2.10.4 (already installed)
  - hicolor-icon-theme (already installed)
  - desktop-file-utils (already installed)
  - shared-mime-info (already installed)


==> Continue building openoffice ? [Y/n]
==> 
==>
==> Building and installing package
==> Making package: openoffice 4.1.7-1 (Thu Dec 17 22:08:40 2020)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
   -> Downloading v4.1.7-x86_64...
   % Total% Received % Xferd  Average Speed   TimeTime Time
Current
  Dload  Upload   Total   SpentLeft
Speed
100   306  100   3060 0   2528  0 --:--:-- --:--:--
--:--:--  2508
   0 00 00 0  0  0 --:--:-- --:--:--
--:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading
http://apache.org/dist/openoffice/4.1.7/binaries/en-US/Apache_OpenOffice_4.1.7_Linux_x86-64_install-rpm_en-US.tar.gz

The url domain should be https://archive.apache.org 


This is where old versions exist. New versions are there or at 
https://downloads.apache.org/openoffice/4.1.8/ 
...


Ahh, Of course. I have been wondering what the issue is. Well I am 
working on a package that uses SF.net again.


However the Package is abandoned, and I just taken the next step in 
marking it orphaned in order to become the maintainer.


We will see. How that will be the outcome.


--
This is the Way! http://www.apache.org/theapacheway/index.html

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