[PR] Tried to translate Code Comments into English Language [openoffice]

2025-06-24 Thread via GitHub
mettbroetchen43 opened a new pull request, #370: URL: https://github.com/apache/openoffice/pull/370 (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] Fix spelling [openoffice]

2025-05-29 Thread via GitHub
Pilot-Pirx commented on PR #368: URL: https://github.com/apache/openoffice/pull/368#issuecomment-2919551169 I had to revert the fix in "main/graphite/graphite-2.3.1.patch" because it could not be applied while building. The typo is in the original graphite code. ;-) --

Re: [PR] pre-commit clean up whitespace for `.cl` and `.xba` files [openoffice]

2025-05-29 Thread via GitHub
Pilot-Pirx merged PR #369: URL: https://github.com/apache/openoffice/pull/369 -- 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: dev-unsubscr

Re: [PR] Fix spelling [openoffice]

2025-05-29 Thread via GitHub
Pilot-Pirx merged PR #368: URL: https://github.com/apache/openoffice/pull/368 -- 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: dev-unsubscr

[PR] pre-commit clean up whitespace for `.cl` and `.xba` files [openoffice]

2025-05-28 Thread via GitHub
jbampton opened a new pull request, #369: URL: https://github.com/apache/openoffice/pull/369 Enforced 3 hooks: - end-of-file-fixer - mixed-line-ending - trailing-whitespace -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[PR] Fix spelling [openoffice]

2025-05-28 Thread via GitHub
jbampton opened a new pull request, #368: URL: https://github.com/apache/openoffice/pull/368 General spelling clean up in many different file types Updated the codespell ignored words list -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] Fix spelling [openoffice]

2025-05-28 Thread via GitHub
Pilot-Pirx merged PR #367: URL: https://github.com/apache/openoffice/pull/367 -- 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: dev-unsubscr

[PR] Fix spelling [openoffice]

2025-05-28 Thread via GitHub
jbampton opened a new pull request, #367: URL: https://github.com/apache/openoffice/pull/367 General spelling clean up in many different file types Updated the codespell ignored words list -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-24 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2907012634 Hehe, I took the strings from AOO42X, so maybe you did the job? ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-24 Thread via GitHub
Pilot-Pirx merged PR #366: URL: https://github.com/apache/openoffice/pull/366 -- 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: dev-unsubscr

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-24 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2906630675 Doing a fresh installation the AES-256 encryption is *not* set as default. Users can decide if they want to activate it. We need to announce the option in our Release Notes when

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-24 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2906623808 Test build en-US: https://www.dropbox.com/scl/fi/esut6i2gzbnc5id0cy6qe/Apache_OpenOffice_4.1.16_Win_x86_install_en-US_aes.exe?rlkey=qwldaemlt9nszuj0fsunyu8cx&st=hlzjtoe7&

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-23 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2905975408 Test build (en-US): https://www.dropbox.com/scl/fi/esut6i2gzbnc5id0cy6qe/Apache_OpenOffice_4.1.16_Win_x86_install_en-US_aes.exe?rlkey=qwldaemlt9nszuj0fsunyu8cx&st=p1gck28l&

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-23 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2905110902 I am doing a build with patched German translation. If this works well I will commit at least the German SDF. We can always work on other languages afterwards. -- This is an

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-23 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2904893664 Yes, the new strings are there, but as expected in English. Translation would need patching the SDF files. IMHO we cannot wait forever to release this, it is almost 11 years old

Re: [PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-23 Thread via GitHub
Pilot-Pirx commented on PR #366: URL: https://github.com/apache/openoffice/pull/366#issuecomment-2903883915 One problem I see here is that the changes include new strings. So for en-US it should work, but all other translated versions would have English text (at best). I will do a test

[PR] Backporting UI changes for enabling AES-256 encryption to AOO41X [openoffice]

2025-05-23 Thread via GitHub
Pilot-Pirx opened a new pull request, #366: URL: https://github.com/apache/openoffice/pull/366 Working towards backporting UI changes for enabling AES-256 encryption to AOO41X. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-21 Thread Dick Groskamp
tthias Seidel wrote: > > Am 18.05.25 um 11:47 schrieb Dick Groskamp: > >> Keith, > >> > >> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > >> Should probably be OpenOffice or Apache OpenOffice > > > > Ad

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-21 Thread Dick Groskamp
> > > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > > > >>>> Keith, > > > >>>> > > > >>>> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > > >

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-21 Thread Dick Groskamp
el wrote: > > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > > >>>> Keith, > > >>>> > > >>>> Caption of Figure 16 still refers to: "OpenOffice.org Start Center" > > >>>> Should probably be OpenOffice or Apach

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-21 Thread Dick Groskamp
> > Hi Keith, > > > > Am 20.05.25 um 18:30 schrieb Keith N. McKenna: > >> Matthias Seidel wrote: > >>> Am 18.05.25 um 11:47 schrieb Dick Groskamp: > >>>> Keith, > >>>> > >>>> Caption of Figure 16 still r

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-20 Thread Keith N. McKenna
Matthias Seidel wrote: Hi Keith, Am 20.05.25 um 18:30 schrieb Keith N. McKenna: Matthias Seidel wrote: Am 18.05.25 um 11:47 schrieb Dick Groskamp: Keith, Caption of Figure 16 still refers to: "OpenOffice.org Start Center" Should probably be OpenOffice or Apache OpenOffice Addit

Re: [PR] Fix spelling [openoffice]

2025-05-20 Thread via GitHub
Pilot-Pirx merged PR #365: URL: https://github.com/apache/openoffice/pull/365 -- 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: dev-unsubscr

[PR] Fix spelling [openoffice]

2025-05-20 Thread via GitHub
jbampton opened a new pull request, #365: URL: https://github.com/apache/openoffice/pull/365 Fixes typos in `main`. Typos mainly fixed in code comments. Update the ignored words list. -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] Fix spelling [openoffice]

2025-05-20 Thread via GitHub
Pilot-Pirx merged PR #364: URL: https://github.com/apache/openoffice/pull/364 -- 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: dev-unsubscr

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-20 Thread Matthias Seidel
Hi Keith, Am 20.05.25 um 18:30 schrieb Keith N. McKenna: Matthias Seidel wrote: Am 18.05.25 um 11:47 schrieb Dick Groskamp: Keith, Caption of Figure 16 still refers to: "OpenOffice.org Start Center" Should probably be OpenOffice or Apache OpenOffice Additionally, I changed a

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-20 Thread Keith N. McKenna
Matthias Seidel wrote: Am 18.05.25 um 11:47 schrieb Dick Groskamp: Keith, Caption of Figure 16 still refers to: "OpenOffice.org Start Center" Should probably be OpenOffice or Apache OpenOffice Additionally, I changed a control in Navigator some time ago, that graphic (graphics

[PR] Fix spelling [openoffice]

2025-05-20 Thread via GitHub
jbampton opened a new pull request, #364: URL: https://github.com/apache/openoffice/pull/364 Fixes lots of typos in `main`. Updated the ignored words list. Typos mostly fixed in code comments -- This is an automated message from the Apache Git Service. To respond to the

Re: (openoffice-docs) branch Writer-Guide updated: Update AOO41WG1-IntroducingWriter.odt

2025-05-20 Thread Matthias Seidel
Am 18.05.25 um 11:47 schrieb Dick Groskamp: Keith, Caption of Figure 16 still refers to: "OpenOffice.org Start Center" Should probably be OpenOffice or Apache OpenOffice Additionally, I changed a control in Navigator some time ago, that graphic (graphics28) should also be updated.

Re: Fwd: OpenOffice commits - 99% are formatting changes

2025-05-12 Thread Aivaras Stepukonis
Since Alex Schwartz cares so much about OpenOffice, here’s the plan for him and his colleagues: divert your currently misplaced energies to OpenOffice by contributing relevant code. If you still want to keep LibreOffice, reuse those contributions. Otherwise, shut down LibreOffice and focus on

Re: Fwd: OpenOffice commits - 99% are formatting changes

2025-05-12 Thread Matthias Seidel
rg. If you choose to respond to it, please respond to the original sender. BKP -- Forwarded message - From: Alex Schwartz Date: Mon, May 12, 2025 at 4:05 PM Subject: OpenOffice commits - 99% are formatting changes To: Please close the project OpenOffice. There are multipl

Fwd: OpenOffice commits - 99% are formatting changes

2025-05-12 Thread Brian Proffitt
This is forwarded from pr...@apache.org. If you choose to respond to it, please respond to the original sender. BKP -- Forwarded message - From: Alex Schwartz Date: Mon, May 12, 2025 at 4:05 PM Subject: OpenOffice commits - 99% are formatting changes To: Please close the

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
eyesaider commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868892872 The documentation in this repository is excellent! Very clear and comprehensive. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
eyesgodcode commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868839458 The documentation in this repository is excellent! Very clear and comprehensive. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
fivemserverhostings commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868839134 This is a well-structured codebase. I appreciate the clean separation of concerns. -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
fivemservereyestore commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868839836 This is a well-structured codebase. I appreciate the clean separation of concerns. -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
godofcodeeyes commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868840115 Excellent contribution to open source! The community will benefit greatly from this. -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
myeyestore commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868840040 Excellent contribution to open source! The community will benefit greatly from this. -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
eyestorefivem commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868839244 The performance optimizations here are quite clever. Nice engineering work! -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
scriptforfivem commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868839083 This is a well-structured codebase. I appreciate the clean separation of concerns. -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
fivemeyestore commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868838968 This is a well-structured codebase. I appreciate the clean separation of concerns. -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] pre-commit: add markdownlint and standardize Markdown files [openoffice]

2025-05-10 Thread via GitHub
fivemhostingserver commented on PR #338: URL: https://github.com/apache/openoffice/pull/338#issuecomment-2868838748 Very clean code with good test coverage. This is a great example of best practices. -- This is an automated message from the Apache Git Service. To respond to the message

Fwd: Your proposal: Apache OpenOffice (T-DOSE 2025)

2025-05-06 Thread Dr. Michael Stehmann
Source Software. During this event, Open Source projects, developers and visitors can exchange ideas and knowledge. Kind regards Michael Weitergeleitete Nachricht Betreff: Your proposal: Apache OpenOffice Datum: Tue, 06 May 2025 18:22:09 - Von: T-DOSE 2025 Antwort an: T

Re: [PR] Clean up ASP files [openoffice]

2025-05-05 Thread via GitHub
Pilot-Pirx merged PR #363: URL: https://github.com/apache/openoffice/pull/363 -- 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: dev-unsubscr

Re: [PR] pre-commit clean up `.common` files [openoffice]

2025-05-04 Thread via GitHub
Pilot-Pirx merged PR #362: URL: https://github.com/apache/openoffice/pull/362 -- 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: dev-unsubscr

[PR] Clean up ASP files [openoffice]

2025-05-04 Thread via GitHub
jbampton opened a new pull request, #363: URL: https://github.com/apache/openoffice/pull/363 - Use lowercase HTML tags - Add quotes to all HTML tag attribute values - fix meta tag attribute "http-equiv" value for "refresh" -- This is an automated message from th

[PR] pre-commit clean up `.common` files [openoffice]

2025-05-04 Thread via GitHub
jbampton opened a new pull request, #362: URL: https://github.com/apache/openoffice/pull/362 Enforce 3 hooks: - end-of-file-fixer - mixed-line-ending - trailing-whitespace -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] misc: fix spelling [openoffice]

2025-04-25 Thread via GitHub
Pilot-Pirx commented on PR #361: URL: https://github.com/apache/openoffice/pull/361#issuecomment-2831025996 Gitbox is not synchronizing again, so the cherry-pick to AOO42X must wait until it works again... -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] misc: fix spelling [openoffice]

2025-04-25 Thread via GitHub
Pilot-Pirx merged PR #361: URL: https://github.com/apache/openoffice/pull/361 -- 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: dev-unsubscr

[PR] misc: fix spelling [openoffice]

2025-04-25 Thread via GitHub
jbampton opened a new pull request, #361: URL: https://github.com/apache/openoffice/pull/361 General typo fixes and updated the ignored words list -- 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

Re: [PR] pre-commit clean up `.mod` files [openoffice]

2025-04-24 Thread via GitHub
Pilot-Pirx merged PR #360: URL: https://github.com/apache/openoffice/pull/360 -- 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: dev-unsubscr

[PR] pre-commit clean up `.mod` files [openoffice]

2025-04-24 Thread via GitHub
jbampton opened a new pull request, #360: URL: https://github.com/apache/openoffice/pull/360 Enforce 3 hooks: - end-of-file-fixer - mixed-line-ending - trailing-whitespace -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] misc: fix spelling [openoffice]

2025-04-24 Thread via GitHub
Pilot-Pirx merged PR #359: URL: https://github.com/apache/openoffice/pull/359 -- 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: dev-unsubscr

[PR] misc: fix spelling [openoffice]

2025-04-24 Thread via GitHub
jbampton opened a new pull request, #359: URL: https://github.com/apache/openoffice/pull/359 General typo fixes similar to other PRs and updated the ignored words list -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [PR] misc: fix spelling [openoffice]

2025-04-23 Thread via GitHub
Pilot-Pirx merged PR #358: URL: https://github.com/apache/openoffice/pull/358 -- 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: dev-unsubscr

[PR] misc: fix spelling [openoffice]

2025-04-22 Thread via GitHub
jbampton opened a new pull request, #358: URL: https://github.com/apache/openoffice/pull/358 Fix typos and update the ignored words list -- 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]

2025-04-12 Thread via GitHub
Pilot-Pirx merged PR #357: URL: https://github.com/apache/openoffice/pull/357 -- 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: dev-unsubscr

[PR] Fix spelling [openoffice]

2025-04-11 Thread via GitHub
jbampton opened a new pull request, #357: URL: https://github.com/apache/openoffice/pull/357 Fixes typos in many file types. -- 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

Re: (openoffice) branch trunk updated: Address FreeBSD bug 281612

2025-04-10 Thread Don Lewis
On 22 Sep, ard...@apache.org wrote: > This is an automated email from the ASF dual-hosted git repository. > > ardovm pushed a commit to branch trunk > in repository https://gitbox.apache.org/repos/asf/openoffice.git > > > The following commit(s) were added to refs/heads/trunk by this push: >

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

2025-04-10 Thread via GitHub
Pilot-Pirx commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-2788958462 > > Almost a year old now and the interest seems to be low? > > Not at all! I use this theme everyday! I really need to allocate some time to finish this!

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

2025-04-09 Thread via GitHub
pedlino commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-275687 > Almost a year old now and the interest seems to be low? Not at all! I use this theme everyday! I really need to allocate some time to finish this! -- This is an automa

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

2025-04-08 Thread via GitHub
Pilot-Pirx commented on PR #214: URL: https://github.com/apache/openoffice/pull/214#issuecomment-2787846169 Almost a year old now and the interest seems to be low? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] pre-commit fix mixed line endings and end of file [openoffice]

2025-04-05 Thread via GitHub
Pilot-Pirx merged PR #352: URL: https://github.com/apache/openoffice/pull/352 -- 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: dev-unsubscr

Re: [PR] pre-commit autofix `.mm` files [openoffice]

2025-04-05 Thread via GitHub
Pilot-Pirx merged PR #353: URL: https://github.com/apache/openoffice/pull/353 -- 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: dev-unsubscr

[PR] Fix spelling [openoffice]

2025-04-05 Thread via GitHub
jbampton opened a new pull request, #339: URL: https://github.com/apache/openoffice/pull/339 (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, e

[PR] pre-commit(whitespace): autofix `.in` files [openoffice]

2025-04-05 Thread via GitHub
jbampton opened a new pull request, #349: URL: https://github.com/apache/openoffice/pull/349 (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, e

Re: [PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-05 Thread via GitHub
jbampton commented on PR #351: URL: https://github.com/apache/openoffice/pull/351#issuecomment-2769078533 Hello @gmcdonald if you have been following the last 3+ months or so of development of Apache OpenOffice you will in fact see that many PRs have been merged with this same format

Re: [PR] Fix spelling [openoffice]

2025-04-05 Thread via GitHub
Pilot-Pirx merged PR #356: URL: https://github.com/apache/openoffice/pull/356 -- 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: dev-unsubscr

Re: [PR] Fix for issue 121222 [openoffice]

2025-04-05 Thread via GitHub
Pilot-Pirx commented on PR #328: URL: https://github.com/apache/openoffice/pull/328#issuecomment-2739979988 Can anyone verify this fix? -- 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

[PR] Fix spelling [openoffice]

2025-04-05 Thread via GitHub
jbampton opened a new pull request, #356: URL: https://github.com/apache/openoffice/pull/356 Mainly fixed 3 typos of a similar word across many files. Update the ignored words list -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] Fix spelling; Fix bug with `ifndef` statement [openoffice]

2025-04-05 Thread via GitHub
Pilot-Pirx merged PR #355: URL: https://github.com/apache/openoffice/pull/355 -- 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: dev-unsubscr

[PR] Fix spelling; Fix bug with `ifndef` statement [openoffice]

2025-04-04 Thread via GitHub
jbampton opened a new pull request, #355: URL: https://github.com/apache/openoffice/pull/355 General typo fixes in many file types Fix bug with `ifndef` statement Update ignored words list -- This is an automated message from the Apache Git Service. To respond to the message

Re: [PR] misc: fix spelling in `main` [openoffice]

2025-04-04 Thread via GitHub
Pilot-Pirx merged PR #354: URL: https://github.com/apache/openoffice/pull/354 -- 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: dev-unsubscr

Re: [PR] Fix spelling [openoffice]

2025-04-04 Thread via GitHub
Pilot-Pirx merged PR #339: URL: https://github.com/apache/openoffice/pull/339 -- 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: dev-unsubscr

[PR] misc: fix spelling in `main` [openoffice]

2025-04-03 Thread via GitHub
jbampton opened a new pull request, #354: URL: https://github.com/apache/openoffice/pull/354 Typos have been fixed in a lot of file types. Updated the codespell ignored words list. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[PR] pre-commit autofix `.mm` files [openoffice]

2025-04-01 Thread via GitHub
jbampton opened a new pull request, #353: URL: https://github.com/apache/openoffice/pull/353 Enforced 3 hooks: - end-of-file-fixer - mixed-line-ending - trailing-whitespace -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[PR] pre-commit fix mixed line endings and end of file [openoffice]

2025-04-01 Thread via GitHub
jbampton opened a new pull request, #352: URL: https://github.com/apache/openoffice/pull/352 Fixed README.md end of file and mixed line endings in test/testgui Replaces or checks mixed line ending. https://github.com/pre-commit/pre-commit-hooks?tab=readme-ov-file#mixed-line

Re: [PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-01 Thread via GitHub
gmcdonald commented on PR #351: URL: https://github.com/apache/openoffice/pull/351#issuecomment-2769025440 You cant just create a PR with 433 changed files and not provide a description of what you did and why - please do that, and for all future PRs please -- This is an automated

Re: [PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-01 Thread via GitHub
Pilot-Pirx commented on PR #351: URL: https://github.com/apache/openoffice/pull/351#issuecomment-2769226551 From time to time GitHub and GitBox do not synchronize... Like just now. Then I have to do another small change to get it in sync. -- This is an automated message from the Apache

Re: [PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-01 Thread via GitHub
Pilot-Pirx merged PR #351: URL: https://github.com/apache/openoffice/pull/351 -- 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: dev-unsubscr

Re: [PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-01 Thread via GitHub
gmcdonald commented on PR #351: URL: https://github.com/apache/openoffice/pull/351#issuecomment-2769182534 All PRs should have descriptions, that what the field is there for. Yes I have been following along, as a PMC member I do take an interest. -- This is an automated message

[PR] pre-commit(end-of-file-fixer): autofix XML files [openoffice]

2025-04-01 Thread via GitHub
jbampton opened a new pull request, #351: URL: https://github.com/apache/openoffice/pull/351 (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, e

Re: [PR] pre-commit(trailing-whitespace): autofix .hrc files [openoffice]

2025-04-01 Thread via GitHub
Pilot-Pirx merged PR #350: URL: https://github.com/apache/openoffice/pull/350 -- 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: dev-unsubscr

[PR] pre-commit(trailing-whitespace): autofix .hrc files [openoffice]

2025-04-01 Thread via GitHub
jbampton opened a new pull request, #350: URL: https://github.com/apache/openoffice/pull/350 (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, e

Re: [PR] pre-commit(whitespace): autofix `.in` files [openoffice]

2025-04-01 Thread via GitHub
Pilot-Pirx merged PR #349: URL: https://github.com/apache/openoffice/pull/349 -- 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: dev-unsubscr

Re: [PR] HTML clean ups for ASP files [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #348: URL: https://github.com/apache/openoffice/pull/348 -- 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: dev-unsubscr

Re: [PR] pre-commit clean ups for `.el` and `.pas` files [openoffice]

2025-03-30 Thread via GitHub
dave2wave commented on PR #342: URL: https://github.com/apache/openoffice/pull/342#issuecomment-2764599714 > I think the ASF licenses were added in an automated way at that time, maybe this was an error. Andrew Rist was the individual from Oracle who made the license header chan

Re: [PR] pre-commit clean ups for `.el` and `.pas` files [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx commented on PR #342: URL: https://github.com/apache/openoffice/pull/342#issuecomment-2764590973 Regarding the .pas files: Is it OK to add the ASF license when it is already licensed under BSD? I think the ASF licenses were added in an automated way at that time, maybe this

Re: [PR] pre-commit(trailing-whitespace): autofix `.pm` files [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #346: URL: https://github.com/apache/openoffice/pull/346 -- 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: dev-unsubscr

[PR] HTML clean ups for ASP files [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #348: URL: https://github.com/apache/openoffice/pull/348 (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, e

Re: [PR] editpic.asp: clean up HTML [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #347: URL: https://github.com/apache/openoffice/pull/347 -- 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: dev-unsubscr

[PR] pre-commit(trailing-whitespace): autofix `.pm` files [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #346: URL: https://github.com/apache/openoffice/pull/346 (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, e

[PR] editpic.asp: clean up HTML [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #347: URL: https://github.com/apache/openoffice/pull/347 (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, e

Re: [PR] pre-commit clean ups for `.m` files [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #345: URL: https://github.com/apache/openoffice/pull/345 -- 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: dev-unsubscr

Re: [PR] Fix spelling [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #343: URL: https://github.com/apache/openoffice/pull/343 -- 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: dev-unsubscr

[PR] pre-commit clean ups for `.m` files [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #345: URL: https://github.com/apache/openoffice/pull/345 Enforced 3 hooks: - end-of-file-fixer - mixed-line-ending - trailing-whitespace -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] Fix spelling [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #344: URL: https://github.com/apache/openoffice/pull/344 -- 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: dev-unsubscr

[PR] Fix spelling [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #344: URL: https://github.com/apache/openoffice/pull/344 (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, e

[PR] Fix spelling [openoffice]

2025-03-30 Thread via GitHub
jbampton opened a new pull request, #343: URL: https://github.com/apache/openoffice/pull/343 (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, e

Re: [PR] pre-commit clean ups for `.el` and `.pas` files [openoffice]

2025-03-30 Thread via GitHub
Pilot-Pirx merged PR #342: URL: https://github.com/apache/openoffice/pull/342 -- 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: dev-unsubscr

  1   2   3   4   5   6   7   8   9   10   >