Re: PR Backlog

[Matthias Seidel]

Hi Dave,

Am 17.12.20 um 01:20 schrieb Dave Fisher:
> We’ve got a backlog of PRs. Many seem to have been reviewed. Who will do the 
> merges?
I often build PRs and can judge on that.
But when it is more than one line that changed it needs someone who can
understand the code.

In the end, "everyone" can merge.

Regards,

   Matthias

>
> Regards,
> Dave
>
> Sent from my iPhone
>
> -
> 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 commented on pull request #113: Avoid "dmake clean" to wipe out the whole tree

[GitBox]

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


   hmm, that echo needs no quotes in 
   ` echo Build environment not set; works without Quotes?` 
   looks strange. Is it special on make files that they can omit these?



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

[PROPOSAL] restructuring build documentation

[Arrigo Marchiori]

Dear All,

I am cross-posting to dev@ and doc@ because... I am not sure which one
fits best. Please excuse me if this is wrong, and only reply on the
correct list.

I personally find building OpenOffice a bit too difficult today, in
terms of _understanding_ what needs to be done. We have build
instructions on the Wiki, build scripts on a SVN repository, but IMHO
a little ``integration'' among these pieces would help every newcomers
(like me) to get a big picture, complete the first successful build
and start helping with the code.

Here are my ideas. I don't know if these topics were already discussed
before my subscription to this list; if so, kindly send me a pointer
so I can avoid you repeating ideas that are already consolidated.

I would like to propose the following layout on the Wiki:

  - build instructions for trunk (currently
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
that needs some updating anyway, such as removing SVN)

- specialized build instructions for trunk on individual
  O.S. (Linux, Windows, BSD etc)

 - build instructions for the latest release (4.1.8)

- specialized build instructions for the latest release on
  individual O.S.

The distinction between trunk and release is IMHO necessary. For
example, Jim is doing a very good work of updating core parts of the
build system, and this changes for one the initial call to the
configure script.  In addition, deprecated information such as the SVN
repository could be deleted from the trunk build instructions, and
only remain in the once-applicable instructions.

The current build scripts on SVN should be explicitly indicated in the
instructions, so that everyone will be able to get (almost) the exact
same release build, as what they can download from the web site.

Moreover, having very clear instructions could make DevOps experience
useful, if we ever need it. For those subscribed to the recruitment
mailing list: yes, I am referring to a recent email received
there. :-)

When a new release is out, a ``snapshot'' of the trunk build
instructions will become the release's build instructions. Similarly
to a git or SVN branch. The trunk instructions always document... the
trunk.

If the above is approved, I will be willing to help achieving it. The
roadmap I can think of is the following:

 1- copy the current build instructions to a "release" build
 instructions page.

 2- fix the "release" build pages (starting from going back in the
 page history) so that they contain the actual steps to build AOO
 4.1.8.

 3- remove outdated parts from the trunk build instructions (such as
 the SVN repository)

Thank you in advance for your feedback and comments!

Best regards,
--
rigo

http://rigo.altervista.org

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

Re: [proposal} Trying to re-generate the Documentation effort

[Matthias Seidel]

Hi Marcia,

Am 17.12.20 um 07:36 schrieb marcia wilbur:
> Hi Keith, 
> please send slack invite. 
>
> Additionally - dev team - I am working on Pi port still - just updated to dec 
> release of Pi OS.

That's good news. I have just installed Raspberry Pi OS and can't wait
to replace LO on that device! ;-)

Regards,

   Matthias

>
> -marcia
>
> - Original Message -
> From: "Keith N. McKenna" 
> To: d...@openoffice.apache.org
> Cc: dev@openoffice.apache.org
> Sent: Wednesday, December 16, 2020 1:12:41 PM
> Subject: Re: [proposal} Trying to re-generate the Documentation effort
>
> On 6/13/2020 4:52 PM, Keith N. McKenna wrote:
>> Greetings all;
>>
>> As the subject states I am proposing a new methodology to try to
>> reinvigorate the stalled documentation effort for AOO. For the first
>> step in this I have created a draft document that lays out the problems
>> and also some proposed solutions. As all most of you have been involved
>> in the documentation effort I would appreciate your comments and
>> suggested changes to it. The document was created in Writer and has
>> record and read changes turned on. Feel free to make any changes or
>> additions you feel could be helpful. Of course comments or suggestions
>> are welcome as replies to the to this mailing list as well.
>>
>> Thank you all in advance for taking time to contribute to this effort
>> and I hope many of you will return to the documentation team as we move
>> forward with this.
>>
>> Regards
>> Keith N. McKenna
>>
>>
> As I have received no further comments from either list I have attached
> the final document to both lists. I will be starting conversations on
> doc@ to decide how we implement this new process. I will of course keep
> dev@ apprised as to the progress of our efforts.
>
> Regards
> Keith
>
> -
> 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: [PROPOSAL] restructuring build documentation

[Mechtilde]

Hello Arrigo,

a very big ++1

so far I had the problem how to begin with the restructure.

After you start I can try to put in my description how to build under
Debian 9 (Stretch) and (if it works) under Debian 10 (buster) with java 11.

Regards

Am 17.12.20 um 14:05 schrieb Arrigo Marchiori:
> Dear All,
> 
> I am cross-posting to dev@ and doc@ because... I am not sure which one
> fits best. Please excuse me if this is wrong, and only reply on the
> correct list.
> 
> I personally find building OpenOffice a bit too difficult today, in
> terms of _understanding_ what needs to be done. We have build
> instructions on the Wiki, build scripts on a SVN repository, but IMHO
> a little ``integration'' among these pieces would help every newcomers
> (like me) to get a big picture, complete the first successful build
> and start helping with the code.
> 
> Here are my ideas. I don't know if these topics were already discussed
> before my subscription to this list; if so, kindly send me a pointer
> so I can avoid you repeating ideas that are already consolidated.
> 
> I would like to propose the following layout on the Wiki:
> 
>   - build instructions for trunk (currently
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
> that needs some updating anyway, such as removing SVN)
> 
> - specialized build instructions for trunk on individual
>   O.S. (Linux, Windows, BSD etc)
> 
>  - build instructions for the latest release (4.1.8)
> 
> - specialized build instructions for the latest release on
>   individual O.S.
> 
> The distinction between trunk and release is IMHO necessary. For
> example, Jim is doing a very good work of updating core parts of the
> build system, and this changes for one the initial call to the
> configure script.  In addition, deprecated information such as the SVN
> repository could be deleted from the trunk build instructions, and
> only remain in the once-applicable instructions.
> 
> The current build scripts on SVN should be explicitly indicated in the
> instructions, so that everyone will be able to get (almost) the exact
> same release build, as what they can download from the web site.
> 
> Moreover, having very clear instructions could make DevOps experience
> useful, if we ever need it. For those subscribed to the recruitment
> mailing list: yes, I am referring to a recent email received
> there. :-)
> 
> When a new release is out, a ``snapshot'' of the trunk build
> instructions will become the release's build instructions. Similarly
> to a git or SVN branch. The trunk instructions always document... the
> trunk.
> 
> If the above is approved, I will be willing to help achieving it. The
> roadmap I can think of is the following:
> 
>  1- copy the current build instructions to a "release" build
>  instructions page.
> 
>  2- fix the "release" build pages (starting from going back in the
>  page history) so that they contain the actual steps to build AOO
>  4.1.8.
> 
>  3- remove outdated parts from the trunk build instructions (such as
>  the SVN repository)
> 
> Thank you in advance for your feedback and comments!
> 
> Best regards,
> --
> rigo
> 
> http://rigo.altervista.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows und OS/2
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



OpenPGP_signature
Description: OpenPGP digital signature

Re: [PROPOSAL] restructuring build documentation

[Peter Kovacs]

sure, try what you have in mind.

We wont loose anything by trying.


On 17.12.20 14:05, Arrigo Marchiori wrote:

Dear All,

I am cross-posting to dev@ and doc@ because... I am not sure which one
fits best. Please excuse me if this is wrong, and only reply on the
correct list.

I personally find building OpenOffice a bit too difficult today, in
terms of _understanding_ what needs to be done. We have build
instructions on the Wiki, build scripts on a SVN repository, but IMHO
a little ``integration'' among these pieces would help every newcomers
(like me) to get a big picture, complete the first successful build
and start helping with the code.

Here are my ideas. I don't know if these topics were already discussed
before my subscription to this list; if so, kindly send me a pointer
so I can avoid you repeating ideas that are already consolidated.

I would like to propose the following layout on the Wiki:

   - build instructions for trunk (currently
 https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
 that needs some updating anyway, such as removing SVN)

 - specialized build instructions for trunk on individual
   O.S. (Linux, Windows, BSD etc)

  - build instructions for the latest release (4.1.8)

 - specialized build instructions for the latest release on
   individual O.S.

The distinction between trunk and release is IMHO necessary. For
example, Jim is doing a very good work of updating core parts of the
build system, and this changes for one the initial call to the
configure script.  In addition, deprecated information such as the SVN
repository could be deleted from the trunk build instructions, and
only remain in the once-applicable instructions.

The current build scripts on SVN should be explicitly indicated in the
instructions, so that everyone will be able to get (almost) the exact
same release build, as what they can download from the web site.

Moreover, having very clear instructions could make DevOps experience
useful, if we ever need it. For those subscribed to the recruitment
mailing list: yes, I am referring to a recent email received
there. :-)

When a new release is out, a ``snapshot'' of the trunk build
instructions will become the release's build instructions. Similarly
to a git or SVN branch. The trunk instructions always document... the
trunk.

If the above is approved, I will be willing to help achieving it. The
roadmap I can think of is the following:

  1- copy the current build instructions to a "release" build
  instructions page.

  2- fix the "release" build pages (starting from going back in the
  page history) so that they contain the actual steps to build AOO
  4.1.8.

  3- remove outdated parts from the trunk build instructions (such as
  the SVN repository)

Thank you in advance for your feedback and comments!

Best regards,
--
rigo

http://rigo.altervista.org

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


--
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

[GitHub] [openoffice] leginee commented on pull request #113: Avoid "dmake clean" to wipe out the whole tree

[GitBox]

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


   Worth a test. :)



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?

[Rony G. Flatscher (Apache)]

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:

[GitHub] [openoffice] ardovm commented on pull request #113: Avoid "dmake clean" to wipe out the whole tree

[GitBox]

ardovm commented on pull request #113:
URL: https://github.com/apache/openoffice/pull/113#issuecomment-747509362


   By the way, I followed that "pattern" as is it the same for the `install` 
target in the same file:
   
   ```Makefile
   install .PHONY :
@test "$(DESTDIR)$(prefix)" != "" || (echo Usage: make install 
[DESTDIR=DIR] prefix=DIR; exit 2)
   [...]
   ```



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: [proposal} Trying to re-generate the Documentation effort

[Peter Kovacs]

Hi all,


I took the liberty to execute the invite to slack.


All the best

Peter

On 17.12.20 07:36, marcia wilbur wrote:

Hi Keith,
please send slack invite.

Additionally - dev team - I am working on Pi port still - just updated to dec 
release of Pi OS.

-marcia

- Original Message -
From: "Keith N. McKenna" 
To: d...@openoffice.apache.org
Cc: dev@openoffice.apache.org
Sent: Wednesday, December 16, 2020 1:12:41 PM
Subject: Re: [proposal} Trying to re-generate the Documentation effort

On 6/13/2020 4:52 PM, Keith N. McKenna wrote:

Greetings all;

As the subject states I am proposing a new methodology to try to
reinvigorate the stalled documentation effort for AOO. For the first
step in this I have created a draft document that lays out the problems
and also some proposed solutions. As all most of you have been involved
in the documentation effort I would appreciate your comments and
suggested changes to it. The document was created in Writer and has
record and read changes turned on. Feel free to make any changes or
additions you feel could be helpful. Of course comments or suggestions
are welcome as replies to the to this mailing list as well.

Thank you all in advance for taking time to contribute to this effort
and I hope many of you will return to the documentation team as we move
forward with this.

Regards
Keith N. McKenna



As I have received no further comments from either list I have attached
the final document to both lists. I will be starting conversations on
doc@ to decide how we implement this new process. I will of course keep
dev@ apprised as to the progress of our efforts.

Regards
Keith

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


--
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

[GitHub] [openoffice] ardovm commented on pull request #113: Avoid "dmake clean" to wipe out the whole tree

[GitBox]

ardovm commented on pull request #113:
URL: https://github.com/apache/openoffice/pull/113#issuecomment-747507745


   @leginee I was also surprised it works :-)
   
   Proof:
   ```
   $ echo Hello world; echo Hallo Welt
   Hello world
   Hallo Welt
   $
   ```



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: [PROPOSAL] restructuring build documentation

[Dave Fisher]

Hi Arrigo,

I really appreciate your enthusiasm and excellent help on AOO!

There was another thread where we discussed moving devtools to git.

I think this would be the perfect time to move/rewrite build instructions as 
markdown files on these GitHub repos:

Apache/openoffice - README.md
Apache/openoffice-project source.md
A new Apache/openoffice-devtools

I would deprecate the Wiki instructions.

Regards,
Dave

> On Dec 17, 2020, at 5:05 AM, Arrigo Marchiori  wrote:
> 
> Dear All,
> 
> I am cross-posting to dev@ and doc@ because... I am not sure which one
> fits best. Please excuse me if this is wrong, and only reply on the
> correct list.
> 
> I personally find building OpenOffice a bit too difficult today, in
> terms of _understanding_ what needs to be done. We have build
> instructions on the Wiki, build scripts on a SVN repository, but IMHO
> a little ``integration'' among these pieces would help every newcomers
> (like me) to get a big picture, complete the first successful build
> and start helping with the code.
> 
> Here are my ideas. I don't know if these topics were already discussed
> before my subscription to this list; if so, kindly send me a pointer
> so I can avoid you repeating ideas that are already consolidated.
> 
> I would like to propose the following layout on the Wiki:
> 
>  - build instructions for trunk (currently
>https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>that needs some updating anyway, such as removing SVN)
> 
>- specialized build instructions for trunk on individual
>  O.S. (Linux, Windows, BSD etc)
> 
> - build instructions for the latest release (4.1.8)
> 
>- specialized build instructions for the latest release on
>  individual O.S.
> 
> The distinction between trunk and release is IMHO necessary. For
> example, Jim is doing a very good work of updating core parts of the
> build system, and this changes for one the initial call to the
> configure script.  In addition, deprecated information such as the SVN
> repository could be deleted from the trunk build instructions, and
> only remain in the once-applicable instructions.
> 
> The current build scripts on SVN should be explicitly indicated in the
> instructions, so that everyone will be able to get (almost) the exact
> same release build, as what they can download from the web site.
> 
> Moreover, having very clear instructions could make DevOps experience
> useful, if we ever need it. For those subscribed to the recruitment
> mailing list: yes, I am referring to a recent email received
> there. :-)
> 
> When a new release is out, a ``snapshot'' of the trunk build
> instructions will become the release's build instructions. Similarly
> to a git or SVN branch. The trunk instructions always document... the
> trunk.
> 
> If the above is approved, I will be willing to help achieving it. The
> roadmap I can think of is the following:
> 
> 1- copy the current build instructions to a "release" build
> instructions page.
> 
> 2- fix the "release" build pages (starting from going back in the
> page history) so that they contain the actual steps to build AOO
> 4.1.8.
> 
> 3- remove outdated parts from the trunk build instructions (such as
> the SVN repository)
> 
> Thank you in advance for your feedback and comments!
> 
> Best regards,
> --
> rigo
> 
> http://rigo.altervista.org
> 
> -
> 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: new person

[Dave Fisher]

> 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.
> 
> 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  class="date">2020-06-19 05:25
> 
> LordofNoob commented on  class="date">2020-06-20 09:18
> 
> kikislater commented on  class="date">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/ 
...

Regards,
Dave

> Aborting...
> ==> ERROR: Makepkg was unable to build openoffice.
> ==> Restart building openoffice ? [y/N]
> ==> ---
> ==> n
> 
> AUR see old version openoffice 4.1.7-1 not 4.1.8 and can't download
> package from source to build.
> If it is possible i Can start try help us like main as package
> maintainer on Archlinux.
> I was never before any package maintainer.
> 
> If you have any other task for me, I turn into ears.
> 
> Bartosz
> 
> 

[GitHub] [openoffice] dave2wave commented on pull request #74: Removed whitespace between tags and other superfluous whitespace (branch Latest)

[GitBox]

dave2wave commented on pull request #74:
URL: https://github.com/apache/openoffice/pull/74#issuecomment-747643540


   Please review your PRs and then start a thread on dev@openoffice to discuss 
approval.



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: MWiki Developer Guide Blank Pages

[Dick Groskamp]

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.

Greetings


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

Re: Chromebook

[Marcus]

Forwarding the answer as the poster is not subscribed to this mailing list.



Am 17.12.20 um 08:59 schrieb Bidouille:

Latest AOO version works.
Here the guide how to do this:
https://youtu.be/MJUUUp3ufN8

- Mail original -

De: "Richard Mccain" 
À: dev@openoffice.apache.org
Envoyé: Jeudi 17 Décembre 2020 02:40:13
Objet: Chromebook

Do you have anything in the pipes for chrome/OS or Chromebooks?



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

Re: [PROPOSAL] restructuring build documentation

[Arrigo Marchiori]

Hello Dave,

On Thu, Dec 17, 2020 at 11:09:15AM -0800, Dave Fisher wrote:

> Hi Arrigo,
> 
> I really appreciate your enthusiasm and excellent help on AOO!

Thank you! I am just doing what I can.

> There was another thread where we discussed moving devtools to git.

I think you mean this one?
https://lists.apache.org/thread.html/r64090cf9de98c0147098b5d7d58b5f248c71b42e06d3dcb1c536bc88%40%3Cdev.openoffice.apache.org%3E

> I think this would be the perfect time to move/rewrite build instructions as
markdown files on these GitHub repos:
> 
> Apache/openoffice - README.md
> Apache/openoffice-project source.md
> A new Apache/openoffice-devtools
> 
> I would deprecate the Wiki instructions.

I think I get your point. This would ensure that the doc is always
paired with the software it talks about.

However, I suggest to keep this documentation on the Wiki, at least at
a first stage. I think it is quicker and easier to edit, and better
allows people to cooperate on the same document, than using Git and
pull requests.

When finished, the ``snapshots'' could be saved into the source tree
when a release is published, and this could avoid us ``branches'' on
the wiki as well as on the code.  But I would leave such decision to a
later stage.

I hope this makes sense.

Best regards,
-- 
rigo

http://rigo.altervista.org

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

new person

[Bartosz Bartczak]

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.

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   Time    Time Time 
Current
 Dload  Upload   Total   Spent    Left 
Speed
100   306  100   306    0 0   2528  0 --:--:-- --:--:--
--:--:--  2508
  0 0    0 0    0 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
    Aborting...
==> ERROR: Makepkg was unable to build openoffice.
==> Restart building openoffice ? [y/N]
==> ---
==> n

AUR see old version openoffice 4.1.7-1 not 4.1.8 and can't download
package from source to build.
If it is possible i Can start try help us like main as package
maintainer on Archlinux.
I was never before any package maintainer.

If you have any other task for me, I turn into ears.

Bartosz

Re: new person

[Pedro Lino]

Hi Bartosz

Welcome!

> On 12/17/2020 9:16 PM Bartosz Bartczak  wrote:
 
> 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.

There is no debt ;) but any help is very welcome!
 
> 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.

Testing on non-Debian based distros like ArchLinux is very welcome!

> If it is possible i Can start try help us like main as package
> maintainer on Archlinux.
> I was never before any package maintainer.

Yes, please!
 
> If you have any other task for me, I turn into ears.

You should be the one to find the items that you can help and that fulfill your 
needs and curiosity.

Best regards,
Pedro
(just another grateful user)

-
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

[Carl Marcum]

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