Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-03-07 Thread via GitHub
Pilot-Pirx merged PR #199: URL: https://github.com/apache/openoffice/pull/199 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) [openoffice]

2024-03-11 Thread via GitHub
ardovm closed pull request #198: Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) URL: https://github.com/apache/openoffice/pull/198 -- 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

Re: [PR] Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) [openoffice]

2024-03-11 Thread via GitHub
ardovm commented on PR #198: URL: https://github.com/apache/openoffice/pull/198#issuecomment-1987694519 It was better to start from trunk. Trunk now builds on Jammy and we will be able to cherry-pick the relevant commits into AOO41X. -- This is an automated message from the Apache Git

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-03-29 Thread via GitHub
ardovm commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2027708940 The logic had to be a little more complex than that. If there is a visible slides after the selection, then it has to be selected. Otherwise, we have to search for a visible slide

Re: [PR] Link pthread library when using OpenSSL on Linux [openoffice]

2024-03-29 Thread via GitHub
DamjanJovanovic commented on PR #206: URL: https://github.com/apache/openoffice/pull/206#issuecomment-2027757168 Oh right, on Linux pthreads is in a separate library, and internal OpenSSL is linked statically, so the binary linking to OpenSSL has to link to pthreads as well. Forgot about

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-03-31 Thread via GitHub
Pilot-Pirx commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2028644068 It did build fine and I have no crashes anymore. The behavior now is logical for me. Maybe this is something we would want to backport for AOO41X? -- This is an automated

Re: [PR] Blog post about development on trunk branch [openoffice-project]

2024-04-03 Thread via GitHub
ardovm merged PR #11: URL: https://github.com/apache/openoffice-project/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-04-02 Thread via GitHub
ardovm merged PR #200: URL: https://github.com/apache/openoffice/pull/200 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling in comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #209: URL: https://github.com/apache/openoffice/pull/209 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Link pthread library when using OpenSSL on Linux [openoffice]

2024-04-01 Thread via GitHub
ardovm merged PR #206: URL: https://github.com/apache/openoffice/pull/206 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #210: URL: https://github.com/apache/openoffice/pull/210 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in comments [openoffice]

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

[PR] Fix spelling in code comments [openoffice]

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

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #208: URL: https://github.com/apache/openoffice/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx commented on PR #208: URL: https://github.com/apache/openoffice/pull/208#issuecomment-2029737332 Thanks again! -- 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.

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-04-01 Thread via GitHub
pedlino commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2030108118 Windows build tested. Bug is fixed in trunk -- 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

[PR] Fix spelling in code comments [openoffice]

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

[PR] Fix spelling in code comments and descriptions only [openoffice]

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

Re: [PR] Fix spelling in code comments and descriptions only [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #207: URL: https://github.com/apache/openoffice/pull/207 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Blog post about development on trunk branch [openoffice-project]

2024-04-01 Thread via GitHub
ardovm opened a new pull request, #11: URL: https://github.com/apache/openoffice-project/pull/11 Proposal for blog post about our latest development on the trunk branch. **Note**: The post is dated 2 April. -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] Update boost - Part 1 [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx commented on PR #202: URL: https://github.com/apache/openoffice/pull/202#issuecomment-1959880734 **Let boost promote to double the sinc_pi() operation.** Modern processors should handle this without any trouble. -- This is an automated message from the Apache Git

Re: [PR] docs: fix spelling in code comments [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx merged PR #205: URL: https://github.com/apache/openoffice/pull/205 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Update boost - Part 1 [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx commented on PR #202: URL: https://github.com/apache/openoffice/pull/202#issuecomment-1959879198 Original comments from Pedro: Minor cleanup to internal boost header packaging We normally don't install all the headers available in boost. There is an interesting

[PR] Add new icon set [openoffice]

2024-05-24 Thread via GitHub
Pilot-Pirx opened a new pull request, #214: URL: https://github.com/apache/openoffice/pull/214 This is a proof of concept how to add a new icon set. I am not sure if we should go with "Remix" but that needs to be discussed -- This is an automated message from the Apache Git

Re: [PR] Add new icon set [openoffice]

2024-05-24 Thread via GitHub
Pilot-Pirx commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-2129948002 Hi Pedro, technically it is good. But there are still a lot of icons missing. I will do a build for Windows soon. -- This is an automated message from the Apache

Re: [PR] Add new icon set [openoffice]

2024-05-24 Thread via GitHub
Pilot-Pirx commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-2129810868 ![VirtualBox_Windows 10 AOO-Build_24_05_2024_17_19_55](https://github.com/apache/openoffice/assets/6442166/ecd6b677-14b3-4e76-b53c-db3f00a5866d) The complete Remix iconset can

Re: [PR] Add new icon set [openoffice]

2024-05-25 Thread via GitHub
Pilot-Pirx commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-2131116502 ![VirtualBox_Windows 10 AOO-Build_25_05_2024_10_10_34](https://github.com/apache/openoffice/assets/6442166/ea312705-27b0-41a4-989e-13f55036ee2c) Windows build can be found

Re: [PR] Fix spelling [openoffice]

2024-06-07 Thread via GitHub
Pilot-Pirx merged PR #216: URL: https://github.com/apache/openoffice/pull/216 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling [openoffice]

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

[PR] Fix spelling [openoffice]

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

[PR] Fix spelling [openoffice]

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

Re: [PR] Fix spelling [openoffice]

2024-06-11 Thread via GitHub
Pilot-Pirx merged PR #218: URL: https://github.com/apache/openoffice/pull/218 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling [openoffice]

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

Re: [PR] Fix spelling [openoffice]

2024-06-11 Thread via GitHub
Pilot-Pirx merged PR #217: URL: https://github.com/apache/openoffice/pull/217 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

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

2024-06-02 Thread via GitHub
sebbASF merged PR #12: URL: https://github.com/apache/openoffice-project/pull/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] docs: fix spelling [openoffice-project]

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

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

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

[PR] blog: fix spelling [openoffice-project]

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

Re: [PR] docs: fix spelling [openoffice-project]

2024-06-02 Thread via GitHub
sebbASF merged PR #14: URL: https://github.com/apache/openoffice-project/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling [openoffice]

2024-06-02 Thread via GitHub
Pilot-Pirx merged PR #215: URL: https://github.com/apache/openoffice/pull/215 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] blog: fix spelling [openoffice-project]

2024-06-02 Thread via GitHub
sebbASF merged PR #13: URL: https://github.com/apache/openoffice-project/pull/13 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] blog: fix spelling [openoffice-project]

2024-06-02 Thread via GitHub
sebbASF commented on PR #13: URL: https://github.com/apache/openoffice-project/pull/13#issuecomment-2143908436 Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Fix spelling [openoffice]

2024-06-12 Thread via GitHub
astepukonis commented on PR #218: URL: https://github.com/apache/openoffice/pull/218#issuecomment-2163208142 “Temporally” is indeed spelled correctly, but it is a wrong word in this context. “Temporarily” should be used instead. The reader is being alerted that the removal will not last

Re: [PR] Fix spelling [openoffice]

2024-06-12 Thread via GitHub
Pilot-Pirx commented on PR #218: URL: https://github.com/apache/openoffice/pull/218#issuecomment-2163242856 Feel free to open a Pull Request. -- 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

Re: [PR] Fix spelling [openoffice]

2024-06-12 Thread via GitHub
Pilot-Pirx commented on PR #218: URL: https://github.com/apache/openoffice/pull/218#issuecomment-2163154087 No, this is not a typo: https://dictionary.cambridge.org/dictionary/english/temporally But if you find typos, feel free to open a Pull Request.  -- This is an

Re: [PR] Fix spelling [openoffice]

2024-06-12 Thread via GitHub
DiGro commented on PR #218: URL: https://github.com/apache/openoffice/pull/218#issuecomment-2162481044 @jbampton @Pilot-Pirx , don't wanna be pickie, but one typo survived the fix: diff --git a/main/sal/qa/libs2test.txt b/main/sal/qa/libs2test.txt index

[PR] Uodated two strings "temporally" to "temporarily" [openoffice]

2024-06-13 Thread via GitHub
DiGro opened a new pull request, #219: URL: https://github.com/apache/openoffice/pull/219 Seems to me "temporarily" is the more suitable word to use. https://github.com/apache/openoffice/commit/ec2a2135550c5a95447b01c64aa9130806c27c75

[PR] Fix spelling [openoffice]

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

Re: [PR] Remove Urchin Tracker - a use of google analytics [openoffice-org]

2024-07-03 Thread via GitHub
dave2wave merged PR #92: URL: https://github.com/apache/openoffice-org/pull/92 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Update 05200100.xhp : par_id was disabled [openoffice]

2024-07-05 Thread via GitHub
DiGro opened a new pull request, #221: URL: https://github.com/apache/openoffice/pull/221 par_id "par_id3154586" was disabled by changing "id" to "nil". Reverted back to field "id" -- This is an automated message from the Apache Git Service. To respond to the message, please log

[PR] Fix spelling [openoffice]

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

[PR] Drop Adfinis SyGroup from consultants.xml [openoffice-org]

2024-07-23 Thread via GitHub
winged opened a new pull request, #93: URL: https://github.com/apache/openoffice-org/pull/93 Adfinis SyGroup is not providing AOO consultant services to new clients anymore, and therefore request to be removed from the public consultants list. -- This is an automated message from the

Re: [PR] Drop Adfinis SyGroup from consultants.xml [openoffice-org]

2024-07-23 Thread via GitHub
dave2wave merged PR #93: URL: https://github.com/apache/openoffice-org/pull/93 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Drop Adfinis SyGroup from consultants.xml [openoffice-org]

2024-07-23 Thread via GitHub
Pilot-Pirx commented on PR #93: URL: https://github.com/apache/openoffice-org/pull/93#issuecomment-2245716502 It is not enough to remove the entry from the xml file. We also need to remove it from the html file that was (originally) generated from that xml file:

Re: [PR] Update 05200100.xhp : par_id was disabled [openoffice]

2024-07-05 Thread via GitHub
Pilot-Pirx commented on PR #221: URL: https://github.com/apache/openoffice/pull/221#issuecomment-2211154559 I agree that this looks suspicious. It also is the only occurrence of "nil" in our Help files. However, it has been that way since the files were imported. For those who

Re: [PR] Fix spelling [openoffice]

2024-07-05 Thread via GitHub
Pilot-Pirx commented on PR #220: URL: https://github.com/apache/openoffice/pull/220#issuecomment-2211098447 Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] Fix spelling [openoffice]

2024-07-05 Thread via GitHub
Pilot-Pirx merged PR #220: URL: https://github.com/apache/openoffice/pull/220 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling [openoffice]

2024-07-08 Thread via GitHub
Pilot-Pirx merged PR #222: URL: https://github.com/apache/openoffice/pull/222 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

<    1   2   3   4