Re: Progress plan??? (was Re: New icon theme)

[Matthias Seidel]

Hi Pedro, All,

Am 11.06.24 um 16:19 schrieb Pedro Lino:

Hi Matthias, all


On 06/11/2024 2:37 PM WEST Matthias Seidel  wrote:

If any programmer would like to look into this, it would be great. For the moment under 
Linux (at least Ubuntu) switching the Gnome UI to  Dark mode causes OpenOffice to switch 
to High Contrast (if the Accessibility option "Automatically detect high contrast 
mode of operating system" is enabled, which is the default)

We could change the default, but would that help?

On Windows, I never managed to get AOO use a dark UI. I could only
enable HC mode and then AOO switches accordingly.

Yes, the problem needs to be solved properly and the solution is not the same 
under Windows and Linux.
  

In any case the current High Contrast icon theme is also a "quick and dirty" 
solution which doesn't work on a light background...

High Contrast was initially dark UI. But Microsoft added some new themes
in Windows. So now we also have a white HC theme.

Yes, I had not tried that before! Unfortunately it does not work for AOO 
because there is only one HC mode and so everything is HC white except for AOO 
which is HC black :)

In any case, there are quite a few inconsistencies regarding HC mode. I 
particularly don't like that it also inverts the AOO and Apache logos!


These are simply graphics. If you have a better solution just commit 
them, e.g. here:


https://github.com/apache/openoffice/blob/trunk/main/default_images/framework/res/backing_hc.png

  

That would be the goal. But honestly, we have more important things on
our list.

Adding a new icon set is (technically) easy when we have the icons. But
users will never see them if we cannot release it.

I fully agree!

Can we (all) agree on a progress plan?


Yes, a Roadmap for 2024 (and beyond) would be great!

Most of my plans are on hold until we have a solution for releasing 4.2.0.

Regards,

   Matthias



All the best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi Pedro,

Am 03.06.24 um 01:17 schrieb Pedro Lino:

Hi Matthias


On 06/02/2024 11:28 PM WEST Matthias Seidel  wrote:
See my explanation above. Your image still shows High Contrast UI. This
is NOT Dark mode. It is High Contrast with other icons.

The green elements (e.g. in Sidebar) are defined in our code, and there
are many more of them. We cannot simply (mis)use HC icons for Dark Mode.

This would just be a "quick and dirty" solution, sorry.

I see what you mean.

If any programmer would like to look into this, it would be great. For the moment under 
Linux (at least Ubuntu) switching the Gnome UI to  Dark mode causes OpenOffice to switch 
to High Contrast (if the Accessibility option "Automatically detect high contrast 
mode of operating system" is enabled, which is the default)


We could change the default, but would that help?

On Windows, I never managed to get AOO use a dark UI. I could only 
enable HC mode and then AOO switches accordingly.



In any case the current High Contrast icon theme is also a "quick and dirty" 
solution which doesn't work on a light background...


High Contrast was initially dark UI. But Microsoft added some new themes 
in Windows. So now we also have a white HC theme.



The more obvious solution is to that each icon set has a light and dark modes 
that switches according to the OS and that HC is a separate mode (set in 
Acessibility) which uses a particular HC icon set also with light and dark 
modes, among other changes (like the green lines)


That would be the goal. But honestly, we have more important things on 
our list.


Adding a new icon set is (technically) easy when we have the icons. But 
users will never see them if we cannot release it.


Regards,

   Matthias


All the best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi,

Am 07.06.24 um 11:41 schrieb Aivaras Stepukonis:

Hi,

2024-06-04 14:42, Matthias Seidel rašė:
Of course SVG would be the best, but AOO is not yet ready for it. At 
the moment we need to export small and large icons as PNG.


I think, it is still more prudent if they supply the icon set in SVG, 
and if SVG is not available in AOO by v4.2, it would be easy to 
convert them to PNGs, while keeping the SVG versions for a future 
upgrade.
Definitely, icons should be designed as SVG. We can always export them 
to the needed PNG later.


2024-06-04 14:42, Matthias Seidel rašė:

Hard to say, Galaxy is the most complete set:

https://github.com/apache/openoffice/tree/trunk/main/default_images

8,530 graphics overall. Assuming half of them being for HC and some 
are not used at all that could be around 4.000 icons (small and large).


Beware that there are not only icons but also other graphics 
(StartCenter, Wizards, ...) in an icon set.


For missing icons (graphics) our code uses "Industrial" as fallback.


Thank you for this info! So the target is to produce some 2000 
original drawings (regardless of the sizes).


In fact some icons (e.g. Folder open) are used in multiple places. So 
the actual number should be smaller.


As a starting point I changed (most of) the icons that are visible in 
Writer:


https://github.com/apache/openoffice/pull/214#issuecomment-2131116502

In fact, the icon set can be built step by step until it is complete.



One last question: how is AOO UI performing on 4K monitors, in 
particular its icons? Is there anything to take into consideration 
while planning for the new icon set? (I’ll be switching to a 4K 
monitor next year, but for now have no experience to rely on.)


I have no idea, I use no 4K monitor. ;-) The icons can be scaled but 
since they are PNG the quality will decrease at some point.


Regards,

   Matthias


--
Pagarbiai / Sincerely,
 Aivaras Stepukonis <mailto:astepuko...@gmail.com>




smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

Hi Peter,

Am 17.02.24 um 13:17 schrieb Peter kovacs:

Hi all,
Getting the translation integration running and migrating to a different we 
frontend are in my opinion 2 different things.


Do you plan to get the translation integration running again in Pootle?

That would be sufficient to get a 4.2.0 release out after all these years...

Regards,

   Matthias


I have planed to look into the translation tomorrow. But I am still unsure how 
that works out.

I want to open a hotbox repository for translations.
And the check if we can optimize the process there a bit.

All the best
Peter


Am 17. Februar 2024 11:44:32 MEZ schrieb Matthias Seidel 
:

Hi All,

Any news on this one? What is the status of the translation process?

Without a working translation we are unable to do a new release. I think we 
should start NOW if we ever want to do release AOO 4.2.0 (I still assume that 
we want to do that).

Regards,

    Matthias

Am 01.11.23 um 19:37 schrieb Dave Fisher:

The OpenOffice project wishes to update the Pootle server 
(translate.Apache.org) that we share to translation software that is 
maintained. Pootle development stopped over four years ago.

Please let OpenOffice know if you still use the service and if you do would you 
like to cooperate on the upgrade?

For OpenOffice,
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: Kryptografische S/MIME-Signatur

Re: T-DOSE 2024

[Matthias Seidel]

Hi Michael (and Mechtilde),

Thanks again for your participation!

Regards,

   Matthias

Am 04.06.24 um 14:44 schrieb Dr. Michael Stehmann:

Hello,

like in the past Apache OpenOffice (and Apache) had a booth at 2024 
edition of T-DOSE.


T-DOSE 2024 happened on 1 and 2 June, again at the Weeffabriek in 
Geldrop (near Eindhoven) [0].


T-DOSE is a free and yearly event held in The Netherlands to promote 
use and development of Free Software. During this event, Free Software 
projects, developers and visitors can exchange ideas and knowledge.


Because Apache OpenOffice is a well known office suite, we showcased 
some more free programs for business and professional tasks. And we 
presented the feather.


But common questions have been again: What is the difference between 
Apache OpenOffice and LibreOffice? Why are there two projects and will 
they unite again? Ok, easy to answer that FAQs meanwhile, even in 
english.


We took the opportunity the exchange ideas with competent visitors 
(not only from The Netherlands) and participants.


It was also this year an interesting weekend.

Kind regards
Michael

[0] https://t-dose.org/2024/


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi Aivaras,

Am 03.06.24 um 11:07 schrieb Aivaras Stepukonis:

Hi,

2024-06-03 01:28, Matthias Seidel rašė:

[…] we would need icon sets for Light UI, Dark UI and High Contrast.

If we decide to work on a new icon set it should be suitable for all 
these use cases. And we could make it the default theme in a later 
(major) release.


2024-06-03 02:17, Pedro Lino rašė:

The more obvious solution is to that each icon set has a light and dark
modes that switches according to the OS and that HC is a separate mode
(set in Acessibility) which uses a particular HC icon set also with
light and dark modes, among other changes (like the green lines)
I’ve made a note about the need to also supply the dark mode variant. 
I’ll ask the designer (if I find one) about high contrast as well.


What is the file format of the icons in OO 4.1.x; PNG, SVG, something 
else? SVG would open a number of possibilities to control the 
appearance of icons via logic (such as inversion/change of color).


Of course SVG would be the best, but AOO is not yet ready for it. At the 
moment we need to export small and large icons as PNG.


We use 16x16 for the small ones. Large icons can have 26x26 (Galaxy), 
24x24 (Industrial)...


The sizes are defined in our code:

https://github.com/apache/openoffice/blob/trunk/main/vcl/inc/toolbox.h#L44



How many icons are there in the OO4.1.x set (to get an idea of the 
scope of labor required)?


Hard to say, Galaxy is the most complete set:

https://github.com/apache/openoffice/tree/trunk/main/default_images

8,530 graphics overall. Assuming half of them being for HC and some are 
not used at all that could be around 4.000 icons (small and large).


Beware that there are not only icons but also other graphics 
(StartCenter, Wizards, ...) in an icon set.


For missing icons (graphics) our code uses "Industrial" as fallback.

Regards,

   Matthias



--

Pagarbiai / Sincerely,
 Aivaras Stepukonis <mailto:astepuko...@gmail.com>



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi Pedro,

Am 02.06.24 um 23:58 schrieb Pedro Lino:

Hi Aivaras, Matthias, all


On 06/02/2024 12:36 PM WEST Aivaras Stepukonis  wrote:
  

The way I see it, we do need a designer for the new OO icon style to be
complete and to look consistent and up-to-date. Thus, my proposal is to
reach out and see whether we can attract one. I’ll make an effort to do
so, but before I do, I need to collect additional information, so I can
present our needs to the Iconify.design crowd in a clear and concise
fashion.

First off, what visual goals are we trying to achieve through the new
icon style?

I think it would be perfect to have a designer. If you can attract one that 
would be fantastic. For the moment Remixicon is a quite complete image set and 
apparently the authors are available to add new ones.
  

As a result, our visual goal for the new icon style could be to produce
a style that hearkens back to Galaxy but is further refined to look
current and in line with the latest generation of OS (the most
widespread being Windows 11) and productivity suites (the most
widespread being Microsoft Office). The style should still be originally
conceived and executed, with the roots in Galaxy (innovation of
tradition, as it were).

Does this sound like a reasonable path to tread in terms of our visual
expectations?

That would be my preference too. I think that monochromatic icons are dull and 
require more focus than colored ones which are more easily identifiable. But 
again, a custom designed icon set requires a designer. Using existing icons 
only requires technical skills.


(I think it’s worth pursuing this task only if it is done well and
feels like a stylistic upgrade; otherwise, the current set of icons
isn’t broken, and needs no fix.)

Current icon sets are not broken but they are incomplete. But this new icon set 
would bring not only a UI modernization (for those who want it) but most 
importantly to add a proper Dark Icon set instead of the High Contrast which is 
currently the Dark style by default.


That problem cannot be solved by a new icon set. This must be done in 
code! We need a logic to differentiate between High Contrast and Dark Mode.


But of course, when we have achieved this, we would need icon sets for 
Light UI, Dark UI and High Contrast.


If we decide to work on a new icon set it should be suitable for all 
these use cases. And we could make it the default theme in a later 
(major) release.





2024-05-31 22:31, Matthias Seidel wrote:

Until we have consensus on this topic the PR will remain a draft
open for everyone.

First of all thank you for your effort to investigate how to add a new icon set!

I would call this theme simply Remixicon (not remixdark) and the inverted, 
(i.e. light image icons) can be added in the same folder without affecting High 
Contrast.

As I explained in a previous message the High Contrast icons are the fallback 
if the icon set does not contain the lch or sch icons.
You (Matthias) can test this by simply copying the lch and sch icons I sent you 
in a zip to
/source/openoffice/main/ooo_custom_images/remixdark/res/commandimagelist/

Please see a screenshot of my latest Linux build based on the 
Pilot-Pirx-iconset branch

https://i.imgur.com/Gx0rlyo.png

I believe these are excellent news because it solves the Linux Dark mode 
problem without affecting people who use the High Contrast
icon style.


See my explanation above. Your image still shows High Contrast UI. This 
is NOT Dark mode. It is High Contrast with other icons.


The green elements (e.g. in Sidebar) are defined in our code, and there 
are many more of them. We cannot simply (mis)use HC icons for Dark Mode.


This would just be a "quick and dirty" solution, sorry.

Regards,

   Matthias



With this said, if a designer can be attracted it would be ideal, regardless if 
he/she creates a new theme from scratch or creates a set based on Remixicon (or 
other existing icon set).

All the best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi Marcus,

Am 31.05.24 um 22:15 schrieb Marcus:

Am 31.05.24 um 18:06 schrieb Matthias Seidel:

Some may already have seen it, I opened a PR to add a new icon theme.

https://github.com/apache/openoffice/pull/214

This is just a proof of concept. I used icons from Remix because they 
are available and under ALv2:


https://remixicon.com/

However, if someone knows other icons to use, please speak up.

Until we have consensus on this topic the PR will remain a draft open 
for everyone.


thanks, looks good. Very minimalist but many people like this style, 
So, it's perfect to have an icon set - in a future release.


Yes, a simple set, maybe one for light themes, one for dark themes.

But that is only a proposal from me (and I had to use *something*)



PS:
I thought "remix" is a mix of existing icons. ;-)


In fact, the "Remix" icon set is not nearly complete and the fallback is 
the "Industrial" icon set.


So it is kind of a mix at the moment! ;-)

Matthias



Marcus


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: New icon theme

[Matthias Seidel]

Hi Aivaras,

Am 31.05.24 um 18:40 schrieb Aivaras Stepukonis:
However, if someone knows other icons to use, please speak up. 

Another good resource is https://iconify.design/

It is important that the icons share the same style, though.

Perhaps we could settle on a stylistic direction we are happy with 
from what is publicly available, and ask the author to contribute to 
OpenOffice a complete set? There is a chance they might be interested 
in doing this.


In fact, I happen to know the developer of iconify.design personally, 
I could ask for help finding a professional graphics volunteer for 
this task.
Under which license ist it released now? And if they would do a complete 
set and contribute it, would it be OK for them that it will be under 
ALv2 then?


(I think it’s worth pursuing this task only if it is done well and 
feels like a stylistic upgrade; otherwise, the current set of icons 
isn’t broken, and needs no fix.)


This is work in progress...

The PR could be merged to trunk, which is our development branch that 
will never be released.


Even if we cherry-pick it for AOO42X that version will not be released 
any time soon.


And I doubt that a new icon set will ever get into AOO41X (just because 
we are not able to add new strings there).


Regards,

   Matthias



--
Pagarbiai / Sincerely,
 Aivaras Stepukonis <mailto:astepuko...@gmail.com>

2024-05-31 19:06, Matthias Seidel rašė:

Hi All,

Some may already have seen it, I opened a PR to add a new icon theme.

https://github.com/apache/openoffice/pull/214

This is just a proof of concept. I used icons from Remix because they 
are available and under ALv2:


https://remixicon.com/

However, if someone knows other icons to use, please speak up.

Until we have consensus on this topic the PR will remain a draft open 
for everyone.


Thoughts?

Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

New icon theme

[Matthias Seidel]

Hi All,

Some may already have seen it, I opened a PR to add a new icon theme.

https://github.com/apache/openoffice/pull/214

This is just a proof of concept. I used icons from Remix because they 
are available and under ALv2:


https://remixicon.com/

However, if someone knows other icons to use, please speak up.

Until we have consensus on this topic the PR will remain a draft open 
for everyone.


Thoughts?

Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

Documenting our source code structure

[Matthias Seidel]

Hi All,

Some time ago I added some rudimentary Readme to some directories in our 
code, e.g.:


https://github.com/apache/openoffice/edit/trunk/main/sw/README.md

Please feel encouraged to add more information to describe what a 
specific directory is meant for.


Of course, this is a work in progress, but it would help volunteers to 
understand our code better.


In this case, who should know, that "sw" stands for "StarWriter" and 
contains the code for the "Writer" part of our software?


Opinions?

Regards,

   Matthias




smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi All,

Am 02.05.24 um 14:02 schrieb Matthias Seidel:

Hi Arrigo,

Am 01.05.24 um 20:31 schrieb Arrigo Marchiori:

Hello All,

TL;DR: I think that keeping distinct branches for trunk and AOO42X is
good practice, and we shall work on stabilizing AOO42X. More below.
To be clear, I am not thinking of build or stability problems when I 
say that we cannot release AOO 4.2.0.


Even if all release blockers in AOO42X are fixed, we do not have a 
working release process!


Translations are outdated and we have no way to get them into our code 
or new strings into our translation process.


This should be a primary problem to be solved.


I would have expected that we start a discussion about improving the 
release process at this point.


Or at least start with a new "Roadmap" for 2024?

Regards,

   Matthias



Regards,

   Matthias



On Wed, May 01, 2024 at 03:52:19PM +0200, Matthias Seidel wrote:


Hi Pedro,

Am 01.05.24 um 15:39 schrieb Pedro Lino:

Hi Matthias

On 05/01/2024 1:30 PM WEST Matthias Seidel 
 wrote:
Maybe it is easier to delete the current 42x branch and start a 
new 42X

branch? If any patches were added to 42X only (and they are still
relevant), then these should be cherry picked to trunk before 
splitting...




+1.

The AOO42X branch is quite old. Development only really happens 
on trunk.
The best maintained branch is trunk, and any branches should be 
as close to

trunk as possible.

Trunk is an unstable branch.

That is the nature of Trunk ;)

Yes! And should not be the nature of AOO42X, IMHO.

Everything we want to have in AOO42X (which was branched from 
trunk some

years ago) should have been cherry-picked early.

Do you mean that all patches/fixes in 42X are in Trunk also?
Trunk has all patches, AOO42X only those that were cherry-picked 
from trunk.

I confirm this. I personally made some patch ``backwards'' (first in
another branch, and then cherry-picked into trunk) but it was my
mistake: our best practice shall be as Matthias described above.

Therefore there would not be a problem in deleting the current 
branch 42X and start a new one?
This would make sense because Damjan mentioned that many relevant 
fixes in trunk are not included in 42X

If he didn't cherry-pick them (for a reason?) they are not included.

...and if no one else did ;-)

I personally cherry-picked the SSL- and curl-related commits because
of some tests I am doing on AOO42X. I think that it makes sense to
cherry-pick also his latest change of 16-bit into 32-bit indices.

Also why is the next release 4.2.x? Haven't we made enough 
changes for

5.0.x? If not, what should be in 5.0.x?
It is quite hypothetical to discuss about versions we are NOT 
capable to

release.
It is. But Damjan's question is still valid? What would be the 
change needed to consider this 5.0? I would say that having a 
Winx64 would be such a condition. As it is, I still see this as 42X

For AOO 5.0 I would expect at least that we support ODF 1.3.

A Win64 build would be great for AOO 4.5.0.

I personally would see both these improvements good for AOO 4.2.0, but
I think it's only a matter of... marketing and promotion. This topic
is worth another thread.

But again, we are not able to do a release, we should work on that 
problem

first.

If we are talking about ``technical'' issues, then I agree that AOO42X
is unstable and for this reason it cannot be released.


The next version we CAN release is 4.1.16 (AOO41X).

That is true!

If we become able to do a release for a newer branch (AOO42X), we 
should

simply release what we have...
Exactly, but including all valid updates that have been added to 
trunk but not cherry picked to 42X

+1

If they were not cherry-picked I would expect there was a reason for 
it?

I think that we have to discuss the meaning of the ``valid'' word as
used above by Pedro.

Almost all commits I saw to trunk would be IMHO applicable to
AOO42X. I do not think there is anything so ``revolutionary'' or
``experimental'', that I would rather delay to 4.3.0, 4.5.0, 5.0.0 or
whatever future AOO version.

However, the author of each commit has IMHO the right to the first
opinion about the opportunity of cherry-picking into AOO42X, AOO41X
etc.

_My_ latest commits to trunk were all targeted to AOO42X. If I did not
cherry-pick them is just because... I forgot to. And Matthias,
sometimes, kindly reminded me about them.

Only trunk should be allowed to be blatantly unstable. The reason for
AOO42X also being unstable is because we inherited it this way. This
is what I understood, at least, and I believe we have to fix this.

I hope I could explain myself clearly.

Best regards,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Arrigo,

Am 01.05.24 um 20:31 schrieb Arrigo Marchiori:

Hello All,

TL;DR: I think that keeping distinct branches for trunk and AOO42X is
good practice, and we shall work on stabilizing AOO42X. More below.
To be clear, I am not thinking of build or stability problems when I say 
that we cannot release AOO 4.2.0.


Even if all release blockers in AOO42X are fixed, we do not have a 
working release process!


Translations are outdated and we have no way to get them into our code 
or new strings into our translation process.


This should be a primary problem to be solved.

Regards,

   Matthias



On Wed, May 01, 2024 at 03:52:19PM +0200, Matthias Seidel wrote:


Hi Pedro,

Am 01.05.24 um 15:39 schrieb Pedro Lino:

Hi Matthias


On 05/01/2024 1:30 PM WEST Matthias Seidel  wrote:

Maybe it is easier to delete the current 42x branch and start a new 42X
branch? If any patches were added to 42X only (and they are still
relevant), then these should be cherry picked to trunk before splitting...



+1.

The AOO42X branch is quite old. Development only really happens on trunk.
The best maintained branch is trunk, and any branches should be as close to
trunk as possible.

Trunk is an unstable branch.

That is the nature of Trunk ;)

Yes! And should not be the nature of AOO42X, IMHO.


Everything we want to have in AOO42X (which was branched from trunk some
years ago) should have been cherry-picked early.

Do you mean that all patches/fixes in 42X are in Trunk also?

Trunk has all patches, AOO42X only those that were cherry-picked from trunk.

I confirm this. I personally made some patch ``backwards'' (first in
another branch, and then cherry-picked into trunk) but it was my
mistake: our best practice shall be as Matthias described above.


Therefore there would not be a problem in deleting the current branch 42X and 
start a new one?
This would make sense because Damjan mentioned that many relevant fixes in 
trunk are not included in 42X

If he didn't cherry-pick them (for a reason?) they are not included.

...and if no one else did ;-)

I personally cherry-picked the SSL- and curl-related commits because
of some tests I am doing on AOO42X. I think that it makes sense to
cherry-pick also his latest change of 16-bit into 32-bit indices.


Also why is the next release 4.2.x? Haven't we made enough changes for
5.0.x? If not, what should be in 5.0.x?

It is quite hypothetical to discuss about versions we are NOT capable to
release.

It is. But Damjan's question is still valid? What would be the change needed to 
consider this 5.0? I would say that having a Winx64 would be such a condition. 
As it is, I still see this as 42X

For AOO 5.0 I would expect at least that we support ODF 1.3.

A Win64 build would be great for AOO 4.5.0.

I personally would see both these improvements good for AOO 4.2.0, but
I think it's only a matter of... marketing and promotion. This topic
is worth another thread.


But again, we are not able to do a release, we should work on that problem
first.

If we are talking about ``technical'' issues, then I agree that AOO42X
is unstable and for this reason it cannot be released.


The next version we CAN release is 4.1.16 (AOO41X).

That is true!


If we become able to do a release for a newer branch (AOO42X), we should
simply release what we have...

Exactly, but including all valid updates that have been added to trunk but not 
cherry picked to 42X

+1


If they were not cherry-picked I would expect there was a reason for it?

I think that we have to discuss the meaning of the ``valid'' word as
used above by Pedro.

Almost all commits I saw to trunk would be IMHO applicable to
AOO42X. I do not think there is anything so ``revolutionary'' or
``experimental'', that I would rather delay to 4.3.0, 4.5.0, 5.0.0 or
whatever future AOO version.

However, the author of each commit has IMHO the right to the first
opinion about the opportunity of cherry-picking into AOO42X, AOO41X
etc.

_My_ latest commits to trunk were all targeted to AOO42X. If I did not
cherry-pick them is just because... I forgot to. And Matthias,
sometimes, kindly reminded me about them.

Only trunk should be allowed to be blatantly unstable. The reason for
AOO42X also being unstable is because we inherited it this way. This
is what I understood, at least, and I believe we have to fix this.

I hope I could explain myself clearly.

Best regards,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Pedro,

Am 01.05.24 um 15:39 schrieb Pedro Lino:

Hi Matthias


On 05/01/2024 1:30 PM WEST Matthias Seidel  wrote:

Maybe it is easier to delete the current 42x branch and start a new 42X
branch? If any patches were added to 42X only (and they are still
relevant), then these should be cherry picked to trunk before splitting...



+1.

The AOO42X branch is quite old. Development only really happens on trunk.
The best maintained branch is trunk, and any branches should be as close to
trunk as possible.

Trunk is an unstable branch.

That is the nature of Trunk ;)
  

Everything we want to have in AOO42X (which was branched from trunk some
years ago) should have been cherry-picked early.

Do you mean that all patches/fixes in 42X are in Trunk also?

Trunk has all patches, AOO42X only those that were cherry-picked from trunk.

Therefore there would not be a problem in deleting the current branch 42X and 
start a new one?
This would make sense because Damjan mentioned that many relevant fixes in 
trunk are not included in 42X


If he didn't cherry-pick them (for a reason?) they are not included.




Also why is the next release 4.2.x? Haven't we made enough changes for
5.0.x? If not, what should be in 5.0.x?

It is quite hypothetical to discuss about versions we are NOT capable to
release.

It is. But Damjan's question is still valid? What would be the change needed to 
consider this 5.0? I would say that having a Winx64 would be such a condition. 
As it is, I still see this as 42X


For AOO 5.0 I would expect at least that we support ODF 1.3.

A Win64 build would be great for AOO 4.5.0.

But again, we are not able to do a release, we should work on that 
problem first.


  

The next version we CAN release is 4.1.16 (AOO41X).

That is true!


If we become able to do a release for a newer branch (AOO42X), we should
simply release what we have...

Exactly, but including all valid updates that have been added to trunk but not 
cherry picked to 42X


If they were not cherry-picked I would expect there was a reason for it?

Regards,

   Matthias



Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Damjan, Pedro, All,

Am 01.05.24 um 03:42 schrieb Damjan Jovanovic:

On Sun, Apr 28, 2024 at 10:55 AM Pedro Lino 
wrote:


Hi Arrigo, all


On 04/27/2024 5:36 PM WEST Arrigo Marchiori  wrote:
The build can be downloaded from here:


https://home.apache.org/~ardovm/openoffice/linux/openoffice4-2024-04-27-x86_64-installed.tar.bz2

Tested in Ubuntu 20.04 x64 and WebDAV works perfectly!


Cherry-picking was not a trivial task, because AOO42X was quite
behind. It still is, WRT Damjan's last work on 32 bit indices. One
step at a time... :-)

Maybe it is easier to delete the current 42x branch and start a new 42X
branch? If any patches were added to 42X only (and they are still
relevant), then these should be cherry picked to trunk before splitting...



+1.

The AOO42X branch is quite old. Development only really happens on trunk.
The best maintained branch is trunk, and any branches should be as close to
trunk as possible.

Trunk is an unstable branch.

Everything we want to have in AOO42X (which was branched from trunk some 
years ago) should have been cherry-picked early.




Also why is the next release 4.2.x? Haven't we made enough changes for
5.0.x? If not, what should be in 5.0.x?
It is quite hypothetical to discuss about versions we are NOT capable to 
release.


The next version we CAN release is 4.1.16 (AOO41X).

If we become able to do a release for a newer branch (AOO42X), we should 
simply release what we have...


Regards,

   Matthias





smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Damjan,

Am 22.04.24 um 19:21 schrieb Damjan Jovanovic:

On Tue, Apr 9, 2024 at 9:21 PM Arrigo Marchiori  wrote:




I think this thread excerpt explains it:
https://lists.apache.org/thread/3rvvgxnws9867krk75rw6bvhmds1t2co



Is that horrible bug fixed now, or does Curl/OpenSSL still crash AOO in
certain setups?

Now when I check for update I see a dialog box with the following
error message:

Status
   Checking for an update failed.
Description
   Error reading data from the Internet.
   Server error message: Problem with the SSL CA cert (path? access
rights?).

I think that on trunk we had solved the crash, but automatic updates
were just failing silently.

I need to build ``untouched'' trunk and try again the above.



In curl lib/strerror.c, function curl_easy_strerror(), that message comes
from:

---snip---
   case CURLE_SSL_CACERT_BADFILE:
 return "Problem with the SSL CA cert (path? access rights?)";
---snip---

Searching for where CURLE_SSL_CACERT_BADFILE appears then takes us to
lib/vtls/openssl.c (since we use OpenSSL).

In that file, it's only set in one region of the lengthy
ossl_connect_step1() function, when ssl_cafile or ssl_capath are set,
verifypeer is set, and calling SSL_CTX_load_verify_file() or
SSL_CTX_load_verify_dir() on them fails.

The ssl_cafile and ssl_capath come from options to ./configure, but those
are impossible to change, read acinclude.m4 around CURL_CHECK_CA_BUNDLE,
where if neither --with-ca-bundle nor --with-ca-path are given (or both are
given but disabled), it auto-detects the local location of the bundle. Even
a wrong path is overridden by the auto-detected one. And this auto-detected
one won't work on other Linux distributions.

So one way to fix the error would be to patch Curl's configure and/or code.

But there is another way, and that is to always call:
curl_easy_setopt( m_pCurl, CURLOPT_CAINFO, "/path/to/certificates" );
at run-time, so that the compile-time path is overridden by the one we
specify there.

Curl version 7.77.0 also added the even better option CURLOPT_CAINFO_BLOB,
which can use an in-memory PEM list, instead of a file.

But here we face a problem.

Our ::com::sun::star::xml::crypto::XSecurityEnvironment is intended to own
the certificate verification process. We just ask it whether a certificate
chain is valid, using the verifyCertificate() method. But no method exists,
to tell us what certificates are trusted.

Thus we cannot populate our trusted certificates from Mozilla/Windows, into
Curl/OpenSSL.

There are 2 ways to get it working:
1. Patch XSecurityEnvironment to add further methods to retrieve the
trusted CA root certificates from Mozilla/Windows, and use these to build
the initial certificate list to pass to Curl/OpenSSL. Then use OpenSSL to
do verification, but on certificates that fail OpenSSL's verification, use
our own verification process instead, like we do now.
2. Specify an initial nonsense certificate to Curl and OpenSSL, just to get
them to initialize, then completely override the certificate verification
with our own using the XSecurityEnvironment, before that nonsense
certificate can be used.

Option 1 seems counter-productive: why do certificate verification twice,
first in OpenSSL, and then again in XSecurityEnvironment (via NSS or
Windows's mscrypt)? Also it's quite a pain to develop, UNO interfaces are
immutable so we'd need new interfaces, new services, and many code changes.

Instead, I have successfully developed option 2:
- Curl has been upgraded to the latest version, 8.7.1.
- A nonsense self-signed expired certificate is fed into Curl to get it to
initialize.
- In Curl's CURLOPT_SSL_CTX_FUNCTION, our Curl_SSLContextCallback, we then
completely override OpenSSL's verification process with ours, using
SSL_CTX_set_cert_verify_callback() (instead of the previous
SSL_CTX_set_verify() which just allows us to override OpenSSL's
verification result).
- The verification is largely the same as before, we just have to call
slightly different functions to retrieve the certificate to verify and the
untrusted chain.
- Various other cleanups, better logging, etc. were made in the process.

And it's working! We should now be able to use HTTPS and WebDAV on any
Linux distribution, including those whose system trusted CA certificates
are in a different location or missing entirely, as long as they have the
Mozilla certificates.

Now what would you guys prefer:
- Should I do more testing, on Windows and Linux, and push my changes in a
few days?
- Should I push my changes now, and let you guys test too, and fix any
problems as we discover them?


Can you create a Pull Request?

Then I could try to build it on Windows.

Regards,

   Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Damjan,

Thanks, it builds fine now!

https://www.dropbox.com/scl/fi/mee9swkwgpa1gsw0axhl1/Apache_OpenOffice_4.5.0_Win_x86_install_en-US_openssl.exe?rlkey=3f9kyqdh4fmztllsda9pqbhmx=0

Regards,

   Matthias

Am 18.04.24 um 03:39 schrieb Damjan Jovanovic:

On Wed, Apr 17, 2024 at 7:13 PM Matthias Seidel 
wrote:


Hi Damjan,

I just tried to build trunk on Windows and it stops in "curl":

...

LINK : fatal error LNK1181: cannot open input file 'libeay32.lib'
NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~1.0\VC\bin\link.exe' :
return code '0x49d'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
Studio 9.0\VC\bin\nmake.exe"' : return code '0x2'
Stop.
dmake:  Error code 2, while making
'./wntmsci12.pro/misc/build/so_built_so_curl'

1 module(s):
  curl
need(s) to be rebuilt

Regards,

 Matthias



Hi Matthias

Please try again now, this might fix it:

commit 9b51720274ee0b7c1ade0e9b4cd4b8417efd1b6c (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Thu Apr 18 03:38:14 2024 +0200

 Fix a regression in 8eb9a7e66a3128669216ddb884f844d50ac59fb9, which
broke
 delivering libcrypto.lib and libssl.lib on Windows.


Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Dynamic OpenSSL causes Curl regression on *nix

[Matthias Seidel]

Hi Damjan,

I just tried to build trunk on Windows and it stops in "curl":

...

LINK : fatal error LNK1181: cannot open input file 'libeay32.lib'
NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~1.0\VC\bin\link.exe' : 
return code '0x49d'

Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual 
Studio 9.0\VC\bin\nmake.exe"' : return code '0x2'

Stop.
dmake:  Error code 2, while making 
'./wntmsci12.pro/misc/build/so_built_so_curl'


1 module(s):
    curl
need(s) to be rebuilt

Regards,

   Matthias

Am 15.04.24 um 19:38 schrieb Damjan Jovanovic:

On Tue, Apr 9, 2024 at 10:14 PM Arrigo Marchiori  wrote:


Hello Damjan, All,

replying to this other message.

On Mon, Apr 08, 2024 at 02:42:01PM +, Damjan Jovanovic wrote:

[...]

Here's how you set RPATH in Curl:

---snip---
diff --git a/main/curl/makefile.mk b/main/curl/makefile.mk
index 044bf4d8c9..ecef11820a 100644
--- a/main/curl/makefile.mk
+++ b/main/curl/makefile.mk
@@ -59,6 +59,7 @@ curl_LDFLAGS+:=$(ARCH_FLAGS)
  ssl_param=--with-ssl
  .ELSE
  ssl_param=--with-ssl=$(OUTDIR)
+curl_LDFLAGS+=-Wl,-z,origin -Wl,-rpath,\\\$$\$$ORIGIN
  PATCH_FILES+= curl-bundled_openssl.patch
  .ENDIF

---snip---

which gets libcurl.so to search for the OpenSSL dynamic libraries in its
own directory before the system directories:

$ ldd solver/450/unxfbsdx.pro/lib/libcurl.so
...
libssl.so.3 => /path/to/openoffice-git/main/solver/450/
unxfbsdx.pro/lib/libssl.so.3 (0x299f766bc000)
libcrypto.so.3 => /path/to/openoffice/openoffice-git/main/solver/450/
unxfbsdx.pro/lib/libcrypto.so.3 (0x299f77747000)

It works under Linux too!


Great, thank you for testing.



If we want to use the dynamically linked OpenSSL, then, we have to
amend 0ca5b4b7b8e66fbc937f89173ce45fcc179e72b3 and have
main/scp2/source/ooo/file_library_ooo.scp include "libssl.so.3" and
"libcrypto.so.3" instead of "libssl.so" and "libcrypto.so".

I think the same should happen under FreeBSD, so you may want to
commit all these edits together after testing them?


Here is my change:

commit 8eb9a7e66a3128669216ddb884f844d50ac59fb9 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Apr 7 10:41:42 2024 +0200

 Build OpenSSL as a dynamic link library, instead of a static library.
 Patch its users to use an RPATH of $ORIGIN, so they use the correct
copy.
 This reduces the size of the build by about 4615 KiB, or 3.78%.



Next step will be asking p11-kit for the CA certificates, as you
proposed here:
https://lists.apache.org/thread/3rb1t9jf5fnp4nfxr2z9dxmzt9l61tjq
otherwise Linux builds may be unable to validate certificate chains,
unfortunately.


No, that was a separate issue. I wanted to make a new xmlsecurity provider
that could be used on Linux instead of Mozilla (which requires category B
nss) and mscrypto for Windows. As currently, --disable-category-b badly
breaks AOO: the macro security dialog won't open, the document signatures
dialog won't open, and a few other features probably break.

We'd need to provide at least the following:
- Cryptographic functions. We could do that with OpenSSL.
- The read-only trusted system certificate store. We could do that with
p11-kit's trust policy module.
- The writable user certificate store, with client certificates. There is
currently no way to do that on the Linux desktop. See my detailed
investigation on https://gitlab.gnome.org/GNOME/seahorse/-/issues/205 for
details, which found several bugs and even design defects that stop it from
working.

However what I am now thinking, is that we could make a partially working
provider, with just the cryptographic functions and system certificate
store, and add the user certificates later. It should only break document
signatures, rather than the macro dialog.

As for Linux validating certificate chains, I'll cover that in another
email.



Best regards,
--
Arrigo



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Fwd: Open office for apple M2?

[Matthias Seidel]

Hi All,

Am 16.04.24 um 10:28 schrieb serena castaldi:

Hello,
I have been trying to install Open Office on my most recent MacBook Air M2 and 
then found that there is not an updated version that can work on this computer. 
Or at least I could not find it to download.
DO you have any information on this topic?
Thank you
Serena Castaldi


The "Platform Hints" section for macOS needs to be updated for a along 
time. (Coming soon...)


Any volunteer?

Matthias

[1] https://www.openoffice.org/download/platform_hints.html



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Next blog post

[Matthias Seidel]

Hi Arrigo,

Am 04.04.24 um 08:20 schrieb Arrigo Marchiori:

Dear All,

On Mon, Apr 01, 2024 at 09:18:07AM +0200, Arrigo Marchiori wrote:

[...]

I prepared a draft on our wiki at [1], so anyone can contribute to the
text.  I am no native English speaker, nor marketing expert... feel
free to correct it!

Can we sort out something in this weekend? It would be great to
publish, say, on April 2nd!

There is now a pull request at [2]. Merging it will cause the post to
be published. As the post is dated 2 April, let us wait until tomorrow.

References:
  
  1: https://cwiki.apache.org/confluence/x/1gniEQ

  2: https://github.com/apache/openoffice-project/pull/11

I pushed commit 6316c11 to the "main" branch of "openoffice-project"
but, apparently, the web site was not published.

Can someone please look into it?


Somehow it didn't build yesterday.

I just committed a small change and now your post is online. To be 
honest, I didn't have a look before my commit, it may be coincidence.


Regards,

   Matthias



Best regards,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO Writer - Line Spacing icons

[Matthias Seidel]

Hi Pedro,

Am 03.04.24 um 15:19 schrieb Pedro Lino:

Hi Matthias

I'm not sure if Dean W is on the dev@ mailing list so I'm adding his/her email 
in copy.

Should I open the bugzilla issue or it is not needed any longer?


This issue is fixed now in all branches.

I don't think we need to open an issue for it.

Regards,

   Matthias



Best,
Pedro


On 04/03/2024 11:36 AM WEST Matthias Seidel  wrote:

  
Hi All,


Am 03.04.24 um 11:33 schrieb Pedro Lino:

Hi Dean


On 04/03/2024 8:54 AM WEST Dean W  wrote:
On my copy of AOO Writer the icons for 1.0 and 1.5 line spacing seem to be
transposed. I have 1.0, 1.5 and 2.0 line spacing in my toolbar, and the gap
for 1.5 (on the icon) is smaller than the gap for the 1.0 line spacing (on
the icon). Line spacing works as otherwise intended, except the icons seem
to be incorrect.

I can confirm this error in the High Contrast theme (which unfortunately is the 
default for Dark Mode desktops)

Confirmed on Windows in High Contrast mode with large icons.


I will add a bug report for this issue.

I just renamed the two icons, that should work.

Should be fixed in our next version.

Regards,

     Matthias


Thank you for reporting!

Best,
Pedro

-
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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO Writer - Line Spacing icons

[Matthias Seidel]

Hi All,

Am 03.04.24 um 11:33 schrieb Pedro Lino:

Hi Dean


On 04/03/2024 8:54 AM WEST Dean W  wrote:
On my copy of AOO Writer the icons for 1.0 and 1.5 line spacing seem to be
transposed. I have 1.0, 1.5 and 2.0 line spacing in my toolbar, and the gap
for 1.5 (on the icon) is smaller than the gap for the 1.0 line spacing (on
the icon). Line spacing works as otherwise intended, except the icons seem
to be incorrect.

I can confirm this error in the High Contrast theme (which unfortunately is the 
default for Dark Mode desktops)


Confirmed on Windows in High Contrast mode with large icons.



I will add a bug report for this issue.


I just renamed the two icons, that should work.

Should be fixed in our next version.

Regards,

   Matthias



Thank you for reporting!

Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi All,

Am 01.04.24 um 18:31 schrieb Matthias Seidel:

Hi Pedro,

Am 01.04.24 um 18:18 schrieb Pedro Lino:

Hi Matthias

On 04/01/2024 10:33 AM WEST Matthias Seidel 
 wrote:

And you are right, the buildbot workers are offline for 9 days now...

Maybe the Bots were celebrating Electric Easter or Digital Fools Day ;)


Somehow this isn't monitored and/or nobody cares. ;-)
If a message is received when it is successful, then it would require 
a second script to warn when it fails? Is this how it works? Who 
takes of this?


If there is someone from our project interested in our buildbots 
he/she can always look here:


https://www.openoffice.org/download/devbuilds.html

And follow the "Summary" link.

BTW: This "Worker" isn't exclusive for OpenOffice, it builds a lot of 
other projects.


Correction: Apart from the OpenOffice tasks only one JMeter task is 
running on that machine and that fails every time.


JIRA ticket is now here:

https://issues.apache.org/jira/browse/INFRA-25677

Regards,

   Matthias



Regards,

   Matthias



Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi Pedro,

Am 01.04.24 um 18:18 schrieb Pedro Lino:

Hi Matthias


On 04/01/2024 10:33 AM WEST Matthias Seidel  wrote:
And you are right, the buildbot workers are offline for 9 days now...

Maybe the Bots were celebrating Electric Easter or Digital Fools Day ;)


Somehow this isn't monitored and/or nobody cares. ;-)

If a message is received when it is successful, then it would require a second 
script to warn when it fails? Is this how it works? Who takes of this?


If there is someone from our project interested in our buildbots he/she 
can always look here:


https://www.openoffice.org/download/devbuilds.html

And follow the "Summary" link.

BTW: This "Worker" isn't exclusive for OpenOffice, it builds a lot of 
other projects.


Regards,

   Matthias



Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi Pedro,

Am 01.04.24 um 11:27 schrieb Pedro Lino:

Hi Matthias


On 03/31/2024 5:40 PM WEST Matthias Seidel  wrote:
You could try the build from our buildbot? ;-)

https://nightlies.apache.org/openoffice/install/linux64/?C=M;O=D

The most recent "daily" build is from the 22nd of March. I'm not sure it will 
include this update?


No, the commit was on March 29.

And you are right, the buildbot workers are offline for 9 days now... 
Somehow this isn't monitored and/or nobody cares. ;-)


Regards,

   Matthias



Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Back to the Future Initiative

[Matthias Seidel]

Hi Arrigo,

Am 01.04.24 um 08:46 schrieb Arrigo Marchiori:

Dear All,

The Apache OpenOffice Development Team is proud to announce that the
next releases will introduce an important change: a text-only user
interface.


And most important for me: It is strictly CUA compliant. [1]

No Ribbons!

Regards,

   Matthias

[1] https://en.wikipedia.org/wiki/IBM_Common_User_Access



Read more:
https://openoffice.apache.org/blog/back-to-the-future-initiative.html

:-)


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Next blog post

[Matthias Seidel]

Hi Arrigo,

Am 31.03.24 um 21:31 schrieb Arrigo Marchiori:

Hello Matthias, All,

On Sun, Mar 31, 2024 at 03:29:19PM +0200, Matthias Seidel wrote:


Hi Arrigo,

Am 29.03.24 um 19:25 schrieb Arrigo Marchiori:

Dear All,

trunk has seen quite a lot of work recently, and because it's trunk,
it is proceeding in a somewhat hidden way.

Due to the fact that the last post on our blog is already 3 months
old, I suggest we make a new post to just tell what it is going on
behind the scenes.

The most relevant things that we I could list are the following:

   - OpenSSL upgrade (this is related to security, encryption
 and digital signatures);

   - implementation of OOXML encryption (this helps compatibility with
 other office suites);

   - fix of compilation errors under the latest Ubuntu (this helps
 contributors build and test AOO on their systems)

   - allow pasting of vector graphics (this helps making prettier documents)

   - various fixes in documentation, help files and interface (this
 makes the overall user experience smoother)

   - various spelling fixes in the source code and documentation (this
 helps developers)

   - various code fixes and cleanups (this helps developers focus on
 interesting things)

Some other commits look ``important'' but I cannot explain them and
need some help:

   * 00ab6c3f8bc46b7dee5058d1206cc64de18809de
 Removing all High Contrast icons from 'Classic' icon set.

This is just a cleanup.

Preparation for the (planned) separation of icon sets.

Ok, do you think it is worth mentioning on the article at [1]?


No, this is still a long way to go...

Regards,

   Matthias




I prepared a draft on our wiki at [1], so anyone can contribute to the
text.  I am no native English speaker, nor marketing expert... feel
free to correct it!

Can we sort out something in this weekend? It would be great to
publish, say, on April 2nd!

Comments and suggestions welcome.

Best regards.

References:

   1: https://cwiki.apache.org/confluence/x/1gniEQ


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi Pedro,

Am 31.03.24 um 18:34 schrieb Pedro Lino:

Hi all


On 03/31/2024 5:09 PM WEST Damjan Jovanovic  wrote:
OpenSSL is used for:
* opening encrypted OOXML files.
* WebDAV connections to https:// servers.
* Python scripting, for hashing, SSL, possibly others.
* possibly Curl, during automatic updates.

Opening WebDAV is working perfectly under Windows 10
I'm curious if this fixes the long standing SMB issue under Linux
https://bz.apache.org/ooo/show_bug.cgi?id=128049

If someone has already built for Linux x64 please share a link.


You could try the build from our buildbot? ;-)

https://nightlies.apache.org/openoffice/install/linux64/?C=M;O=D

Regards,

   Matthias



Best,
Pedro

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi All,

Please find a Windows build here:

https://www.dropbox.com/scl/fi/mee9swkwgpa1gsw0axhl1/Apache_OpenOffice_4.5.0_Win_x86_install_en-US_openssl.exe?rlkey=3f9kyqdh4fmztllsda9pqbhmx=0

Happy testing!

Regards,

   Matthias

Am 31.03.24 um 15:27 schrieb Matthias Seidel:

Hi Damjan, All,

Am 29.03.24 um 15:32 schrieb Matthias Seidel:

Hi Damjan,

Am 29.03.24 um 10:33 schrieb Damjan Jovanovic:

Hi

I've now pushed commit 4c5b548fb6ece87dd30bbf720aca0d994a749167 into 
trunk,

upgrading our OpenSSL version from 1.0.2u to 3.0.13.


Great!

I am just doing a build on Windows.


Builds fine for me!

But I am not sure how to test OpenSSL functionality?

Regards,

   Matthias



Regards,

   Matthias



Some issues to consider:

-
PLATFORMS
-
It works on FreeBSD 14, both with system OpenSSL linked dynamically and
internal OpenSSL linked statically.

Linux hasn't been tested but is so similar to FreeBSD that it really 
should

work.

It works on Windows, with the following changes:
- OpenSSL requires Perl to build, but doesn't like Cygwin's Perl.
Previously, OpenSSL 1.0.2u was patched to use Cygwin's Perl, but 
OpenSSL 3
completely changed the build system, and I couldn't port the old 
patches.
Now note how traditionally our build tools (eg. make, Apache Ant, 
awk, sed,

etc.) were all installed prior to building OpenOffice, detected by
./configure, and then used during the build. I've done something 
different:
during ./bootstrap it will now download the Win32 Strawberry Perl 
portable
binaries as a dependency, and while building OpenSSL, it will unzip 
these
and temporarily use them as the Perl for building OpenSSL. This 
works, and
should reliably continue to work, but is a bit unusual, uses close 
to 800
MB extra disk space, and cannot use a system-wide Strawberry Perl 
instead
of the portable binaries, so it is something we may want to change 
going

forward. On the plus side, this new approach neither requires any
additional options to ./configure, nor babysitting any more build
dependencies, nor dragging around long patches to change OpenSSL to use
Cygwin's Perl. If anybody objects, speak up.
- Some defines were missing from MSVC's header files, for the ancient
version of the MSVC compiler we use, so I had to add them as command 
line

parameters to the compiler instead, eg.
"-DINT64_MAX=9223372036854775807i64".
- OpenSSL normally requires fairly recent versions of Windows, but also
supports the more minimal Windows CE, and so has fallback paths that 
can be
used for older versions of Windows. I've configured it to target 
Windows 95
and NT 4.0, and added a small number of patches that fix the build 
issues,

mostly by using the Windows CE fallback code.
- NASM is handled better: before, when NASM was already in the $PATH
instead of --with-nasm-path being passed to ./configure, building 
openssl

would break. It now works.
- Python needed a lot of patching to use OpenSSL 3, and the Win64 
build of

python is probably broken and will need further work.
- It takes really long to build. We could disable unit tests to 
speed it up

(by passing "no-tests" to Configure), but I am not sure I like skipping
tests. We should be testing more, not less.

macOS? Who knows. It looks like on macOS, our main/openssl module links
statically, and doesn't apply any patches, so it might already work.

-
LICENSING
-
Licensing has changed, as OpenSSL 3 is under the Apache Software 
License v2

like ourselves, and our LICENSE and NOTICE files have been greatly
simplified.

-
CODE CHANGES
-
Remarkably, no changes to our C/C++ code were required. Some code 
changes
were required in the past, eg. 
f884850fece86ece56c7194bb1e746641f77c0a0 to

deal with EVP_CIPHER_CTX_init() -> EVP_CIPHER_CTX_new() between OpenSSL
1.0.x and 1.1.x. However, nothing needed changing between 1.1.x and 
3.0.13,

OpenSSL was sufficiently backward compatible.

--
OTHER BRANCHES
--
While those 1.0.x -> 1.1.x code changes are in trunk, they may be 
absent
from other branches, so cherry picking this commit to other branches 
may

require more commits to be cherry picked.

-
FUTURE
-
OpenSSL 3.0.x is the LTS release series, and will be supported until
2026-09-07.

Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Next blog post

[Matthias Seidel]

Hi Arrigo,

Am 29.03.24 um 19:25 schrieb Arrigo Marchiori:

Dear All,

trunk has seen quite a lot of work recently, and because it's trunk,
it is proceeding in a somewhat hidden way.

Due to the fact that the last post on our blog is already 3 months
old, I suggest we make a new post to just tell what it is going on
behind the scenes.

The most relevant things that we I could list are the following:

  - OpenSSL upgrade (this is related to security, encryption
and digital signatures);

  - implementation of OOXML encryption (this helps compatibility with
other office suites);

  - fix of compilation errors under the latest Ubuntu (this helps
contributors build and test AOO on their systems)

  - allow pasting of vector graphics (this helps making prettier documents)

  - various fixes in documentation, help files and interface (this
makes the overall user experience smoother)

  - various spelling fixes in the source code and documentation (this
helps developers)

  - various code fixes and cleanups (this helps developers focus on
interesting things)

Some other commits look ``important'' but I cannot explain them and
need some help:

  * 00ab6c3f8bc46b7dee5058d1206cc64de18809de
Removing all High Contrast icons from 'Classic' icon set.


This is just a cleanup.

Preparation for the (planned) separation of icon sets.

Regards,

   Matthias



I prepared a draft on our wiki at [1], so anyone can contribute to the
text.  I am no native English speaker, nor marketing expert... feel
free to correct it!

Can we sort out something in this weekend? It would be great to
publish, say, on April 2nd!

Comments and suggestions welcome.

Best regards.

References:

  1: https://cwiki.apache.org/confluence/x/1gniEQ


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi Damjan, All,

Am 29.03.24 um 15:32 schrieb Matthias Seidel:

Hi Damjan,

Am 29.03.24 um 10:33 schrieb Damjan Jovanovic:

Hi

I've now pushed commit 4c5b548fb6ece87dd30bbf720aca0d994a749167 into 
trunk,

upgrading our OpenSSL version from 1.0.2u to 3.0.13.


Great!

I am just doing a build on Windows.


Builds fine for me!

But I am not sure how to test OpenSSL functionality?

Regards,

   Matthias



Regards,

   Matthias



Some issues to consider:

-
PLATFORMS
-
It works on FreeBSD 14, both with system OpenSSL linked dynamically and
internal OpenSSL linked statically.

Linux hasn't been tested but is so similar to FreeBSD that it really 
should

work.

It works on Windows, with the following changes:
- OpenSSL requires Perl to build, but doesn't like Cygwin's Perl.
Previously, OpenSSL 1.0.2u was patched to use Cygwin's Perl, but 
OpenSSL 3
completely changed the build system, and I couldn't port the old 
patches.
Now note how traditionally our build tools (eg. make, Apache Ant, 
awk, sed,

etc.) were all installed prior to building OpenOffice, detected by
./configure, and then used during the build. I've done something 
different:
during ./bootstrap it will now download the Win32 Strawberry Perl 
portable
binaries as a dependency, and while building OpenSSL, it will unzip 
these
and temporarily use them as the Perl for building OpenSSL. This 
works, and
should reliably continue to work, but is a bit unusual, uses close to 
800
MB extra disk space, and cannot use a system-wide Strawberry Perl 
instead

of the portable binaries, so it is something we may want to change going
forward. On the plus side, this new approach neither requires any
additional options to ./configure, nor babysitting any more build
dependencies, nor dragging around long patches to change OpenSSL to use
Cygwin's Perl. If anybody objects, speak up.
- Some defines were missing from MSVC's header files, for the ancient
version of the MSVC compiler we use, so I had to add them as command 
line

parameters to the compiler instead, eg.
"-DINT64_MAX=9223372036854775807i64".
- OpenSSL normally requires fairly recent versions of Windows, but also
supports the more minimal Windows CE, and so has fallback paths that 
can be
used for older versions of Windows. I've configured it to target 
Windows 95
and NT 4.0, and added a small number of patches that fix the build 
issues,

mostly by using the Windows CE fallback code.
- NASM is handled better: before, when NASM was already in the $PATH
instead of --with-nasm-path being passed to ./configure, building 
openssl

would break. It now works.
- Python needed a lot of patching to use OpenSSL 3, and the Win64 
build of

python is probably broken and will need further work.
- It takes really long to build. We could disable unit tests to speed 
it up

(by passing "no-tests" to Configure), but I am not sure I like skipping
tests. We should be testing more, not less.

macOS? Who knows. It looks like on macOS, our main/openssl module links
statically, and doesn't apply any patches, so it might already work.

-
LICENSING
-
Licensing has changed, as OpenSSL 3 is under the Apache Software 
License v2

like ourselves, and our LICENSE and NOTICE files have been greatly
simplified.

-
CODE CHANGES
-
Remarkably, no changes to our C/C++ code were required. Some code 
changes
were required in the past, eg. 
f884850fece86ece56c7194bb1e746641f77c0a0 to

deal with EVP_CIPHER_CTX_init() -> EVP_CIPHER_CTX_new() between OpenSSL
1.0.x and 1.1.x. However, nothing needed changing between 1.1.x and 
3.0.13,

OpenSSL was sufficiently backward compatible.

--
OTHER BRANCHES
--
While those 1.0.x -> 1.1.x code changes are in trunk, they may be absent
from other branches, so cherry picking this commit to other branches may
require more commits to be cherry picked.

-
FUTURE
-
OpenSSL 3.0.x is the LTS release series, and will be supported until
2026-09-07.

Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgraded to 3.0.13

[Matthias Seidel]

Hi Damjan,

Am 29.03.24 um 10:33 schrieb Damjan Jovanovic:

Hi

I've now pushed commit 4c5b548fb6ece87dd30bbf720aca0d994a749167 into trunk,
upgrading our OpenSSL version from 1.0.2u to 3.0.13.


Great!

I am just doing a build on Windows.

Regards,

   Matthias



Some issues to consider:

-
PLATFORMS
-
It works on FreeBSD 14, both with system OpenSSL linked dynamically and
internal OpenSSL linked statically.

Linux hasn't been tested but is so similar to FreeBSD that it really should
work.

It works on Windows, with the following changes:
- OpenSSL requires Perl to build, but doesn't like Cygwin's Perl.
Previously, OpenSSL 1.0.2u was patched to use Cygwin's Perl, but OpenSSL 3
completely changed the build system, and I couldn't port the old patches.
Now note how traditionally our build tools (eg. make, Apache Ant, awk, sed,
etc.) were all installed prior to building OpenOffice, detected by
./configure, and then used during the build. I've done something different:
during ./bootstrap it will now download the Win32 Strawberry Perl portable
binaries as a dependency, and while building OpenSSL, it will unzip these
and temporarily use them as the Perl for building OpenSSL. This works, and
should reliably continue to work, but is a bit unusual, uses close to 800
MB extra disk space, and cannot use a system-wide Strawberry Perl instead
of the portable binaries, so it is something we may want to change going
forward. On the plus side, this new approach neither requires any
additional options to ./configure, nor babysitting any more build
dependencies, nor dragging around long patches to change OpenSSL to use
Cygwin's Perl. If anybody objects, speak up.
- Some defines were missing from MSVC's header files, for the ancient
version of the MSVC compiler we use, so I had to add them as command line
parameters to the compiler instead, eg.
"-DINT64_MAX=9223372036854775807i64".
- OpenSSL normally requires fairly recent versions of Windows, but also
supports the more minimal Windows CE, and so has fallback paths that can be
used for older versions of Windows. I've configured it to target Windows 95
and NT 4.0, and added a small number of patches that fix the build issues,
mostly by using the Windows CE fallback code.
- NASM is handled better: before, when NASM was already in the $PATH
instead of --with-nasm-path being passed to ./configure, building openssl
would break. It now works.
- Python needed a lot of patching to use OpenSSL 3, and the Win64 build of
python is probably broken and will need further work.
- It takes really long to build. We could disable unit tests to speed it up
(by passing "no-tests" to Configure), but I am not sure I like skipping
tests. We should be testing more, not less.

macOS? Who knows. It looks like on macOS, our main/openssl module links
statically, and doesn't apply any patches, so it might already work.

-
LICENSING
-
Licensing has changed, as OpenSSL 3 is under the Apache Software License v2
like ourselves, and our LICENSE and NOTICE files have been greatly
simplified.

-
CODE CHANGES
-
Remarkably, no changes to our C/C++ code were required. Some code changes
were required in the past, eg. f884850fece86ece56c7194bb1e746641f77c0a0 to
deal with EVP_CIPHER_CTX_init() -> EVP_CIPHER_CTX_new() between OpenSSL
1.0.x and 1.1.x. However, nothing needed changing between 1.1.x and 3.0.13,
OpenSSL was sufficiently backward compatible.

--
OTHER BRANCHES
--
While those 1.0.x -> 1.1.x code changes are in trunk, they may be absent
from other branches, so cherry picking this commit to other branches may
require more commits to be cherry picked.

-
FUTURE
-
OpenSSL 3.0.x is the LTS release series, and will be supported until
2026-09-07.

Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan,

Am 29.03.24 um 11:17 schrieb Damjan Jovanovic:

On Sun, Mar 17, 2024 at 5:46 PM Matthias Seidel 
wrote:


Hi Dave,

Am 17.03.24 um 18:01 schrieb Dave Fisher:

Hi Damjan,

I know it “opens a big can of worms” and is another issue, but upgrading

to a newer OpenSSL for Trunk and maybe 4.2 would be a very good thing,

We need to update a lot of things, including openSSL and MSVC...

But we should first try to get a working build system for AOO42X, so we
are able to do a release after all these years.

My PRs are on hold until then. Even my work on the Help files has
stopped because of the old SDF files.



What is wrong with the build system for AOO42X?


"Build system" may be the wrong phrase... "Release system" may be better.

We are able to build en-US, but every commit that changes strings or 
adds new ones makes the translated versions more and more unusable due 
to the outdated SDF files. For AOO41X I began to patch the SDF files, 
but that is error prone and definitely not usable for AOO42X.


Pootle seems to be unmaintained and we still need to find a working 
alternative.


Regards,

   Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO will have a booth at Chemnitzer Linux-Tage 2024

[Matthias Seidel]

Hi Peter,

Am 17.02.24 um 13:12 schrieb Peter kovacs:

I forgot the posters on froscom. Sadly I am busy on 16th and 17th March.
Let me check if I can get into the Ruhr Gebiet before this date. I can 
hopefully clarify tomorrow.
If not I send it per post.


Did that work out?

CLT was last weekend, I think.

Regards,

   Matthias



All the best
Peter

Am 17. Februar 2024 12:23:59 MEZ schrieb Matthias Seidel 
:

Hi,

Am 09.02.24 um 12:48 schrieb Dr. Michael Stehmann:

Hello,

we will have a booth at Chemnitzer Linux-Tage 2024 again.

Date is the 16th and 17th of March 2024 and the place is Chemnitz in Germany.

Great!

Helpers are welcome.

I will not be able to attend.

But I have sent new AOO posters to Peter last year (for FROScon).

Did he hand over them to you? We should NOT use the old (totally outdated) 
posters anymore...

Regards,

    Matthias


You will find more about this great event at

https://chemnitzer.linux-tage.de/2024/en

Kind regards
Michael







smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: OpenSSL upgrade?

[Matthias Seidel]

Hi Damjan,

+1 for upgrading OpenSSL, at least for trunk/AOO42X.

That said, I can not estimate if this is an "easy" fix...

Regards,

   Matthias

Am 17.03.24 um 18:42 schrieb Damjan Jovanovic:

Hi

Is there some reason we are still using such an old version of OpenSSL?

>From what I see, these are the modules that depend on OpenSSL:
$ grep -l openssl */prj/build.lst
curl/prj/build.lst
oox/prj/build.lst
openssl/prj/build.lst
python/prj/build.lst
redland/prj/build.lst
ucb/prj/build.lst

curl: is a heavy user of OpenSSL and really should support new versions.
oox: only used by the Standard/Agile encryption, which I successfully
tested against OpenSSL 3 recently.
python: compiles and links against OpenSSL 3.
redland: unknown
ucb: used only by the WebDAV content provider, which I added it to, and
compiles and links against OpenSSL 3, probably already works too.

It seems like an upgrade will be easy?

Regards
Damjan

On Sun, Mar 17, 2024 at 5:03 PM Dave Fisher  wrote:


Hi Damjan,

I know it “opens a big can of worms” and is another issue, but upgrading
to a newer OpenSSL for Trunk and maybe 4.2 would be a very good thing,

Best,
Dave


On Mar 17, 2024, at 4:23 AM, Damjan Jovanovic  wrote:

Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free(). Finally
some template function was unhappy about parameter type ambiguity (even
though superior compilers like Clang are perfectly happy), and I had to

add

casts.




smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi All,

Am 19.03.24 um 13:41 schrieb Matthias Seidel:

Hi All,

Am 18.03.24 um 20:01 schrieb Matthias Seidel:

Hi Damjan,

I managed to get it cherry-picked to AOO42X (one older commit was 
missing) and do a build now.


Works great!

That said, it would be fantastic to have that fix in AOO41X but I 
don't dare to cherry-pick it...

AOO41X seems to use dmake in that module, while trunk/AOO42X use gbuild.


Anyone?


Obviously not?

Regards,

   Matthias



Regards,

   Matthias



Thanks again for this work!

Regards,

   Matthias

Am 18.03.24 um 07:10 schrieb Damjan Jovanovic:

That's great. Thank you for testing.

My own tests also show it no longer crashes, both the Standard and 
Agile

encryption are working now :).

On Sun, Mar 17, 2024 at 7:59 PM Matthias Seidel 


wrote:


Hi Damjan, All,

That seems to have fixed the crashes on Windows...

Regards,

 Matthias

Am 17.03.24 um 16:56 schrieb Matthias Seidel:

I am already doing a full build,but hopefully I could pull your last
commit soon enough.

Regards,

    Matthias

Am 17.03.24 um 15:20 schrieb Damjan Jovanovic:

If you haven't done "dmake clean" yet like me, try to "git pull" my
latest
commit, and then in main/instsetoo_native "build --from oox -P2 
-- -P2".


This commit fixes at least one more issue:

commit 244f2bcc921bc5dc45e6c1970e27ac2409c44e17 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Mar 17 15:56:38 2024 +0200

  Don't allow calls to OpenSSLCipher::blockSize() before the 
cipher

  is initialized.

On Sun, Mar 17, 2024 at 1:24 PM Matthias Seidel

wrote:


WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx,
docx) I now get the password dialog

But when I enter the correct password AOO crashes.

Regards,

 Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:
I've fixed this now and it seems to build on Windows too. The 
fixes

are in
these commits, and if they work, should be cherry-picked in 
the given

order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008
compiler
doesn't have the ::std::vector::data() method (even though it
should, it
was part of the C++98/03 standard), I had to use [0] 
instead.

Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free().
Finally
some template function was unhappy about parameter type ambiguity
(even
though superior compilers like Clang are perfectly happy), and 
I had

to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel

wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44)

:
error C3861: 'EVP_MD_CTX_new': identifier not found


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51)

:
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) 
: see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) 
: see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) 
: see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi All,

Am 18.03.24 um 20:01 schrieb Matthias Seidel:

Hi Damjan,

I managed to get it cherry-picked to AOO42X (one older commit was 
missing) and do a build now.


Works great!

That said, it would be fantastic to have that fix in AOO41X but I don't 
dare to cherry-pick it...


Anyone?

Regards,

   Matthias



Thanks again for this work!

Regards,

   Matthias

Am 18.03.24 um 07:10 schrieb Damjan Jovanovic:

That's great. Thank you for testing.

My own tests also show it no longer crashes, both the Standard and Agile
encryption are working now :).

On Sun, Mar 17, 2024 at 7:59 PM Matthias Seidel 


wrote:


Hi Damjan, All,

That seems to have fixed the crashes on Windows...

Regards,

 Matthias

Am 17.03.24 um 16:56 schrieb Matthias Seidel:

I am already doing a full build,but hopefully I could pull your last
commit soon enough.

Regards,

    Matthias

Am 17.03.24 um 15:20 schrieb Damjan Jovanovic:

If you haven't done "dmake clean" yet like me, try to "git pull" my
latest
commit, and then in main/instsetoo_native "build --from oox -P2 -- 
-P2".


This commit fixes at least one more issue:

commit 244f2bcc921bc5dc45e6c1970e27ac2409c44e17 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Mar 17 15:56:38 2024 +0200

  Don't allow calls to OpenSSLCipher::blockSize() before the 
cipher

  is initialized.

On Sun, Mar 17, 2024 at 1:24 PM Matthias Seidel

wrote:


WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx,
docx) I now get the password dialog

But when I enter the correct password AOO crashes.

Regards,

 Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:
I've fixed this now and it seems to build on Windows too. The 
fixes

are in
these commits, and if they work, should be cherry-picked in the 
given

order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008
compiler
doesn't have the ::std::vector::data() method (even though it
should, it
was part of the C++98/03 standard), I had to use [0] 
instead.

Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free().
Finally
some template function was unhappy about parameter type ambiguity
(even
though superior compilers like Clang are perfectly happy), and 
I had

to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel

wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44)

:
error C3861: 'EVP_MD_CTX_new': identifier not found


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51)

:
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : 
see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : 
see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 
'Type' is

ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : 
see

declaration of 'oox::getFlag'
    could be 'unsigned int'
    or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.c

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan,

I managed to get it cherry-picked to AOO42X (one older commit was 
missing) and do a build now.


Thanks again for this work!

Regards,

   Matthias

Am 18.03.24 um 07:10 schrieb Damjan Jovanovic:

That's great. Thank you for testing.

My own tests also show it no longer crashes, both the Standard and Agile
encryption are working now :).

On Sun, Mar 17, 2024 at 7:59 PM Matthias Seidel 
wrote:


Hi Damjan, All,

That seems to have fixed the crashes on Windows...

Regards,

 Matthias

Am 17.03.24 um 16:56 schrieb Matthias Seidel:

I am already doing a full build,but hopefully I could pull your last
commit soon enough.

Regards,

Matthias

Am 17.03.24 um 15:20 schrieb Damjan Jovanovic:

If you haven't done "dmake clean" yet like me, try to "git pull" my
latest
commit, and then in main/instsetoo_native "build --from oox -P2 -- -P2".

This commit fixes at least one more issue:

commit 244f2bcc921bc5dc45e6c1970e27ac2409c44e17 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Mar 17 15:56:38 2024 +0200

  Don't allow calls to OpenSSLCipher::blockSize() before the cipher
  is initialized.

On Sun, Mar 17, 2024 at 1:24 PM Matthias Seidel

wrote:


WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx,
docx) I now get the password dialog

But when I enter the correct password AOO crashes.

Regards,

 Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:

I've fixed this now and it seems to build on Windows too. The fixes
are in
these commits, and if they work, should be cherry-picked in the given
order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008
compiler
doesn't have the ::std::vector::data() method (even though it
should, it
was part of the C++98/03 standard), I had to use [0] instead.
Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free().
Finally
some template function was unhappy about parameter type ambiguity
(even
though superior compilers like Clang are perfectly happy), and I had
to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel

wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44)

:
error C3861: 'EVP_MD_CTX_new': identifier not found


c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51)

:
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
could be 'unsigned int'
or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
could be 'unsigned int'
or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) :
error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
could be 'unsigned int'
or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
with
[
_Ty=sal_uInt8
]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
with
[
_Ty=sal_uInt8
]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
with
[
_Ty=sal_uInt8
]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(299) :
error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
with
[
_Ty=sal_uInt8
]
c:/Source/openoffice/main/oox/source/core/encryp

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan, All,

That seems to have fixed the crashes on Windows...

Regards,

   Matthias

Am 17.03.24 um 16:56 schrieb Matthias Seidel:
I am already doing a full build,but hopefully I could pull your last 
commit soon enough.


Regards,

   Matthias

Am 17.03.24 um 15:20 schrieb Damjan Jovanovic:
If you haven't done "dmake clean" yet like me, try to "git pull" my 
latest

commit, and then in main/instsetoo_native "build --from oox -P2 -- -P2".

This commit fixes at least one more issue:

commit 244f2bcc921bc5dc45e6c1970e27ac2409c44e17 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Mar 17 15:56:38 2024 +0200

 Don't allow calls to OpenSSLCipher::blockSize() before the cipher
 is initialized.

On Sun, Mar 17, 2024 at 1:24 PM Matthias Seidel 


wrote:


WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx,
docx) I now get the password dialog

But when I enter the correct password AOO crashes.

Regards,

    Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:

I've fixed this now and it seems to build on Windows too. The fixes
are in
these commits, and if they work, should be cherry-picked in the given
order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008 
compiler
doesn't have the ::std::vector::data() method (even though it 
should, it

was part of the C++98/03 standard), I had to use [0] instead.
Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free().
Finally
some template function was unhappy about parameter type ambiguity 
(even

though superior compilers like Clang are perfectly happy), and I had
to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel

wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44) 
:

error C3861: 'EVP_MD_CTX_new': identifier not found
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51) 
:

error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) : 
error

C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) : 
error

C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) : 
error

C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(299) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(362) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(700) : 
error

C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(701) : 
error

C2039: 'data' : is not a m

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Dave,

Am 17.03.24 um 18:01 schrieb Dave Fisher:

Hi Damjan,

I know it “opens a big can of worms” and is another issue, but upgrading to a 
newer OpenSSL for Trunk and maybe 4.2 would be a very good thing,


We need to update a lot of things, including openSSL and MSVC...

But we should first try to get a working build system for AOO42X, so we 
are able to do a release after all these years.


My PRs are on hold until then. Even my work on the Help files has 
stopped because of the old SDF files.


Regards,

   Matthias


Best,
Dave


On Mar 17, 2024, at 4:23 AM, Damjan Jovanovic  wrote:

Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free(). Finally
some template function was unhappy about parameter type ambiguity (even
though superior compilers like Clang are perfectly happy), and I had to add
casts.


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

I am already doing a full build,but hopefully I could pull your last 
commit soon enough.


Regards,

   Matthias

Am 17.03.24 um 15:20 schrieb Damjan Jovanovic:

If you haven't done "dmake clean" yet like me, try to "git pull" my latest
commit, and then in main/instsetoo_native "build --from oox -P2 -- -P2".

This commit fixes at least one more issue:

commit 244f2bcc921bc5dc45e6c1970e27ac2409c44e17 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sun Mar 17 15:56:38 2024 +0200

 Don't allow calls to OpenSSLCipher::blockSize() before the cipher
 is initialized.

On Sun, Mar 17, 2024 at 1:24 PM Matthias Seidel 
wrote:


WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx,
docx) I now get the password dialog

But when I enter the correct password AOO crashes.

Regards,

Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:

I've fixed this now and it seems to build on Windows too. The fixes
are in
these commits, and if they work, should be cherry-picked in the given
order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008 compiler
doesn't have the ::std::vector::data() method (even though it should, it
was part of the C++98/03 standard), I had to use [0] instead.
Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free().
Finally
some template function was unhappy about parameter type ambiguity (even
though superior compilers like Clang are perfectly happy), and I had
to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel

wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44) :
error C3861: 'EVP_MD_CTX_new': identifier not found
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51) :
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
   could be 'unsigned int'
   or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(299) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(362) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(700) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(701) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
   with
   [
   _Ty=sal_uInt8
   ]
c:/Source/openoffice/main/oox/

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

WTH, shortly after I sent this mail I could open the files...

Matthias

Am 17.03.24 um 14:22 schrieb Matthias Seidel:

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx, 
docx) I now get the password dialog


But when I enter the correct password AOO crashes.

Regards,

   Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:
I've fixed this now and it seems to build on Windows too. The fixes 
are in
these commits, and if they work, should be cherry-picked in the given 
order:


f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008 compiler
doesn't have the ::std::vector::data() method (even though it should, it
was part of the C++98/03 standard), I had to use [0] instead. 
Also

that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free(). 
Finally

some template function was unhappy about parameter type ambiguity (even
though superior compilers like Clang are perfectly happy), and I had 
to add

casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel 


wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44) :
error C3861: 'EVP_MD_CTX_new': identifier not found
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51) :
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(299) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(362) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(700) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(701) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(702) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(710) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(711) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(753) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan,

That was fast! ;-)

I can confirm that it builds now on Windows.

When I try to open password protected MS Office 2020+ files (xlsx, docx) 
I now get the password dialog


But when I enter the correct password AOO crashes.

Regards,

   Matthias

P.S.: This was a partial build, I will try a complete build now.

Am 17.03.24 um 12:23 schrieb Damjan Jovanovic:

I've fixed this now and it seems to build on Windows too. The fixes are in
these commits, and if they work, should be cherry-picked in the given order:

f65b4e326d91bfe900dc1dd22ece69e3ddd8444a
f3025b08c40161265442c34e2b50bc05aa5388c6
42c0a318a970f6f7f43d26a8397448d5d5b8bd36

There were several problems on Windows. The Visual Studio 2008 compiler
doesn't have the ::std::vector::data() method (even though it should, it
was part of the C++98/03 standard), I had to use [0] instead. Also
that ancient OpenSSL version we use internally, 1.0.x, uses
EVP_MD_CTX_create()/destroy() instead of EVP_MD_CTX_new()/free(). Finally
some template function was unhappy about parameter type ambiguity (even
though superior compilers like Clang are perfectly happy), and I had to add
casts.


On Sun, Mar 17, 2024 at 11:15 AM Matthias Seidel 
wrote:


Hi Damjan,

You are right, the interesting part is at the beginning:

---

=
Building module oox
=

Entering /cygdrive/c/Source/openoffice/main/oox/prj

cd .. && make -s -r -j1   && make -s -r deliverlog
[ build CXX ] oox/source/core/encryption
encryption.cxx
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(44) :
error C3861: 'EVP_MD_CTX_new': identifier not found
c:/Source/openoffice/main/oox/inc\oox/helper/openssl_wrapper.hxx(51) :
error C3861: 'EVP_MD_CTX_free': identifier not found
c:/Source/openoffice/main/oox/source/core/encryption.cxx(100) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(133) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(134) : error
C2782: 'bool oox::getFlag(Type,Type)' : template parameter 'Type' is
ambiguous
c:/Source/openoffice/main/oox/inc\oox/helper/helper.hxx(141) : see
declaration of 'oox::getFlag'
  could be 'unsigned int'
  or   'sal_uInt32'
c:/Source/openoffice/main/oox/source/core/encryption.cxx(210) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(214) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(217) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(299) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(362) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(700) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(701) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(702) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(710) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(711) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(753) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'
  with
  [
  _Ty=sal_uInt8
  ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(754) : error
C2039: 'data' : is not a member of 'std::vector<_Ty>'

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(833) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(852) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(854) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(882) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(882) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(882) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(888) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(888) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(888) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(930) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(932) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(932) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(938) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
c:/Source/openoffice/main/oox/source/core/encryption.cxx(946) : error 
C2039: 'data' : is not a member of 'std::vector<_Ty>'

    with
    [
    _Ty=sal_uInt8
    ]
make: *** No rule to make target 
'/cygdrive/c/Source/openoffice/main/solver/450/wntmsci12.pro/workdir/CxxObject/oox/source/core/encryption.o', 
needed by 
'/cygdrive/c/Source/openoffice/main/solver/450/wntmsci12.pro/workdir/LinkTarget/Library/ioox.lib'. 
Stop.

dmake:  Error code 2, while making 'all'

1 module(s):
    oox
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making 
/cygdrive/c/Source/openoffice/main/oox/prj


When you have fixed the errors in that module you can resume the build 
by running:


    build --from oox

---

Regards,

   Matthias

Am 17.03.24 um 01:55 schrieb Damjan Jovanovic:

Please check further up in the log, or run "build" in main/oox again.

That "No rule to make target" happens after other errors break compilation.

On Sat, Mar 16, 2024 at 8:38 PM Matthias Seidel 
wrote:


Hi Damjan,

Tried to build trunk on Windows but it stops here:

make: *** No rule to make target
'/cygdrive/c/Source/openoffice/main/solver/450/
wntmsci12.pro/workdir/CxxObject/oox/source/core/encryption.o',
needed by
'/cygdrive/c/Source/openoffice/main/solver/450/
wntmsci12.pro/workdir/LinkTarget/Library/ioox.lib'.
Stop.
dmake:  Error code 2, while making 'all'

1 module(s):
  oox
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making
/cygdrive/c/Source/openoffice/main/oox/prj

When you have fixed the errors in that module you can resume the build
by running:

  build --from oox

Am 16.03.24 um 04:49 schrieb Damjan Jovanovic:

Hi

Bug 118236 with 7 votes, the inability to open password-protected
(encrypted) OOXML files from MS Office 2010+, is now fixed in trunk :-)

---snip---
commit 506fa58b1970084a0caacb50b3a805e469be4756 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sat Mar 2 18:47:05 2024 +0200

  Implement the (MS Office 2010+) OOXML "Agile encryption" support, so
that we
  can open such password-protected OOXML files.

  Adds all the Agile encryption XML tokens and namespaces, and parses

the

XML
  from EncryptionInfo stream, gets OpenOffice to recognize the file is
encrypted
  and ask for a password, and suc

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan,

Tried to build trunk on Windows but it stops here:

make: *** No rule to make target 
'/cygdrive/c/Source/openoffice/main/solver/450/wntmsci12.pro/workdir/CxxObject/oox/source/core/encryption.o', 
needed by 
'/cygdrive/c/Source/openoffice/main/solver/450/wntmsci12.pro/workdir/LinkTarget/Library/ioox.lib'. 
Stop.

dmake:  Error code 2, while making 'all'

1 module(s):
    oox
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making 
/cygdrive/c/Source/openoffice/main/oox/prj


When you have fixed the errors in that module you can resume the build 
by running:


    build --from oox

Am 16.03.24 um 04:49 schrieb Damjan Jovanovic:

Hi

Bug 118236 with 7 votes, the inability to open password-protected
(encrypted) OOXML files from MS Office 2010+, is now fixed in trunk :-)

---snip---
commit 506fa58b1970084a0caacb50b3a805e469be4756 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sat Mar 2 18:47:05 2024 +0200

 Implement the (MS Office 2010+) OOXML "Agile encryption" support, so
that we
 can open such password-protected OOXML files.

 Adds all the Agile encryption XML tokens and namespaces, and parses the
XML
 from EncryptionInfo stream, gets OpenOffice to recognize the file is
encrypted
 and ask for a password, and successfully decrypts the file if password
is
 correct.

 Also a number of other fixes and improvements:
 - Sorted main/oox/source/token/tokens.txt so it's in alphabetical order
   (wrong order might have broken certain tokens?).
 - Refactored how OOXML encryption is generally handled. It's now in its
   own file.
 - Added logging to the FilterDetect class. It logs to the office-wide
default
   logger.
 - Added a flush() method to the BinaryXOutputStream class.
 - Changed FilterDetect to use XMultiComponentFactory and
XComponentContext
   instead of the deprecated XMultiServiceFactory.
 - Error handling was generally improved.
 - Exception safety and some memory safety (::std::vector instead of
new[])
   in all the new code. Memory leaks should not be possible.

 Much of the code involved in the decryption was ported from the
excellent
 Apache POI project, so it's been credited in our NOTICE file.

 Patch by: me
---snip---


It took much longer than I expected:

The MS-OFFCRYPTO specification was unclear, and plain wrong in some parts,
eg. "SHA-1" in the spec but "SHA1" in actual OOXML documents; I've made our
code support both.

The "Standard" encryption from MS Office 2007 that we already supported was
itself a mess, and much work was needed to refactor and clean up that code
before the "Agile" encryption could also be added.

Then XML parsing had to be added, since Agile encryption specifies settings
in XML instead of binary like Standard encryption did. XML handling in
OpenOffice is pretty outdated, with no support for namespaces, but at least
the newer "FastParser" does support namespaces and is in fact very fast
because it converts strings to unique integers, and packs namespaces into
bit fields, for faster comparisons. I ended up updating the main/oox
FastParser to support the new Agile encryption namespaces and elements.

MS-OFFCRYPTO also only describes encryption, not decryption, and since we
can only read OOXML, only decryption matters.

Apache POI code was tremendously helpful in figuring out the decryption
process. Most of the decryption code I added was just ported directly from
theirs, and thus I've added Apache POI to our NOTICE file (please check
that I've done it correctly). Also several bugs were figured out by
simultaneously stepping through our code in gdb and their code in NetBeans,
and comparing respective values. A big thank you to the Apache POI
developers, whose OOXML support is still better than ours in many ways!

I used OpenSSL for all the message digest and encryption stuff, both
because our MD5 and SHA1 algorithms are broken (bug 127661), and because
Agile encryption requires many digests and ciphers that OpenSSL supports
but we don't.

Anyway, it works now. All encrypted OOXML files should work, eg. text
documents, spreadsheets, presentations, etc.

Other issues I am aware of:
- We only support password encrypted documents. Certificate encrypted
documents: not yet. ODF 1.3 also added certificate encryption, so maybe
that's something we should develop together.
- There are other variations of encryption we still don't support, eg. the
"Extensible" encryption, the "RC4 CryptoAPI" encryption, "XOR obfuscation",
etc. Apache POI would be a good source for those too. It's unclear to me
how widely those are used, and whether they are worth implementing.
- It may need to be rearchitected when we add OOXML writing.
- A lot of other required cleanups to our code were discovered, will
discuss those separately.

I've squashed all my work into a single commit, so it can be easily
cherry-picked to AOO42X and maybe even AOO41X 

Re: MS Office 2010+ "Agile" encrypted OOXML documents are working now!

[Matthias Seidel]

Hi Damjan,

That sounds great!

If nobody is faster than me I will cherry-pick your commit to AOO42X 
tomorrow.


Thank you for your massive work.

Regards,

   Matthias

Am 16.03.24 um 04:49 schrieb Damjan Jovanovic:

Hi

Bug 118236 with 7 votes, the inability to open password-protected
(encrypted) OOXML files from MS Office 2010+, is now fixed in trunk :-)

---snip---
commit 506fa58b1970084a0caacb50b3a805e469be4756 (HEAD -> trunk,
origin/trunk, origin/HEAD)
Author: Damjan Jovanovic 
Date:   Sat Mar 2 18:47:05 2024 +0200

 Implement the (MS Office 2010+) OOXML "Agile encryption" support, so
that we
 can open such password-protected OOXML files.

 Adds all the Agile encryption XML tokens and namespaces, and parses the
XML
 from EncryptionInfo stream, gets OpenOffice to recognize the file is
encrypted
 and ask for a password, and successfully decrypts the file if password
is
 correct.

 Also a number of other fixes and improvements:
 - Sorted main/oox/source/token/tokens.txt so it's in alphabetical order
   (wrong order might have broken certain tokens?).
 - Refactored how OOXML encryption is generally handled. It's now in its
   own file.
 - Added logging to the FilterDetect class. It logs to the office-wide
default
   logger.
 - Added a flush() method to the BinaryXOutputStream class.
 - Changed FilterDetect to use XMultiComponentFactory and
XComponentContext
   instead of the deprecated XMultiServiceFactory.
 - Error handling was generally improved.
 - Exception safety and some memory safety (::std::vector instead of
new[])
   in all the new code. Memory leaks should not be possible.

 Much of the code involved in the decryption was ported from the
excellent
 Apache POI project, so it's been credited in our NOTICE file.

 Patch by: me
---snip---


It took much longer than I expected:

The MS-OFFCRYPTO specification was unclear, and plain wrong in some parts,
eg. "SHA-1" in the spec but "SHA1" in actual OOXML documents; I've made our
code support both.

The "Standard" encryption from MS Office 2007 that we already supported was
itself a mess, and much work was needed to refactor and clean up that code
before the "Agile" encryption could also be added.

Then XML parsing had to be added, since Agile encryption specifies settings
in XML instead of binary like Standard encryption did. XML handling in
OpenOffice is pretty outdated, with no support for namespaces, but at least
the newer "FastParser" does support namespaces and is in fact very fast
because it converts strings to unique integers, and packs namespaces into
bit fields, for faster comparisons. I ended up updating the main/oox
FastParser to support the new Agile encryption namespaces and elements.

MS-OFFCRYPTO also only describes encryption, not decryption, and since we
can only read OOXML, only decryption matters.

Apache POI code was tremendously helpful in figuring out the decryption
process. Most of the decryption code I added was just ported directly from
theirs, and thus I've added Apache POI to our NOTICE file (please check
that I've done it correctly). Also several bugs were figured out by
simultaneously stepping through our code in gdb and their code in NetBeans,
and comparing respective values. A big thank you to the Apache POI
developers, whose OOXML support is still better than ours in many ways!

I used OpenSSL for all the message digest and encryption stuff, both
because our MD5 and SHA1 algorithms are broken (bug 127661), and because
Agile encryption requires many digests and ciphers that OpenSSL supports
but we don't.

Anyway, it works now. All encrypted OOXML files should work, eg. text
documents, spreadsheets, presentations, etc.

Other issues I am aware of:
- We only support password encrypted documents. Certificate encrypted
documents: not yet. ODF 1.3 also added certificate encryption, so maybe
that's something we should develop together.
- There are other variations of encryption we still don't support, eg. the
"Extensible" encryption, the "RC4 CryptoAPI" encryption, "XOR obfuscation",
etc. Apache POI would be a good source for those too. It's unclear to me
how widely those are used, and whether they are worth implementing.
- It may need to be rearchitected when we add OOXML writing.
- A lot of other required cleanups to our code were discovered, will
discuss those separately.

I've squashed all my work into a single commit, so it can be easily
cherry-picked to AOO42X and maybe even AOO41X when people are happy with it.

Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Latest English dictionary

[Matthias Seidel]

Hi Marco,

Am 02.03.24 um 11:31 schrieb Marco A.G. Pinto:

Ahhh…

I only tested the AOO + LO here, maybe I uploaded the wrong one.

Anyway, they are identical, only the words "LibreOffice 4.0+" and 
"OpenOffice 4.0+" are different and also the repository URL.

Ah, OK. I thought there were technical differences.


Next month I will be more careful, sorry.


No problem, I will do my builds now and update the dictionary for all 
branches next month...


Regards,

   Matthias



On 02/03/2024 10:25, Matthias Seidel wrote:

Hi All,

The latest English dictionary on our extension site [1] seems to be 
the version for LO.


I think this is only a mistake. I would like to update to the new 
version and do my Test builds with it.


Regards,

   Matthias

[1] https://sourceforge.net/projects/aoo-extensions/files/17102/100/



--

smime.p7s
Description: Kryptografische S/MIME-Signatur

Latest English dictionary

[Matthias Seidel]

Hi All,

The latest English dictionary on our extension site [1] seems to be the 
version for LO.


I think this is only a mistake. I would like to update to the new 
version and do my Test builds with it.


Regards,

   Matthias

[1] https://sourceforge.net/projects/aoo-extensions/files/17102/100/



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO will have a booth at Chemnitzer Linux-Tage 2024

[Matthias Seidel]

Hi,

Am 09.02.24 um 12:48 schrieb Dr. Michael Stehmann:

Hello,

we will have a booth at Chemnitzer Linux-Tage 2024 again.

Date is the 16th and 17th of March 2024 and the place is Chemnitz in 
Germany.

Great!


Helpers are welcome.


I will not be able to attend.

But I have sent new AOO posters to Peter last year (for FROScon).

Did he hand over them to you? We should NOT use the old (totally 
outdated) posters anymore...


Regards,

   Matthias



You will find more about this great event at

https://chemnitzer.linux-tage.de/2024/en

Kind regards
Michael







smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

Hi All,

Any news on this one? What is the status of the translation process?

Without a working translation we are unable to do a new release. I think 
we should start NOW if we ever want to do release AOO 4.2.0 (I still 
assume that we want to do that).


Regards,

   Matthias

Am 01.11.23 um 19:37 schrieb Dave Fisher:

The OpenOffice project wishes to update the Pootle server 
(translate.Apache.org) that we share to translation software that is 
maintained. Pootle development stopped over four years ago.

Please let OpenOffice know if you still use the service and if you do would you 
like to cooperate on the upgrade?

For OpenOffice,
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: Kryptografische S/MIME-Signatur

Re: [Issue 101010] Direct svg or eps export from calc

[Matthias Seidel]

Hi Dave, All,

Am 14.02.24 um 16:48 schrieb Dave Fisher:

CC to dev@ for exposure.

I think that this fix is absolutely cool!


Definitely!

I am now building for Windows to test...

Regards,

   Matthias



Best,
Dave


On Feb 13, 2024, at 8:46 PM, bugzi...@apache.org wrote:

https://bz.apache.org/ooo/show_bug.cgi?id=101010

dam...@apache.org changed:

   What|Removed |Added

 CC||dam...@apache.org

--- Comment #2 from dam...@apache.org ---
With bug 112829 fixed, you can directly copy charts from Calc in SVG format,
but you still need to paste and save them somewhere else.

Is that an acceptable solution?

--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Problem With Open Office and Windows 11 /11 Pro.

[Matthias Seidel]

Funny fact:

I have two machines with Windows 11 (22H2 and 23H2 Insider Preview) and 
both do not have the option for "Suggested Actions".


I only have "Clipboard History" and see no problems with AOO 4.1.15, 
when enabled.


Matthias

Am 13.02.24 um 18:40 schrieb Matthias Seidel:

Hi Damjan,

Am 13.02.24 um 16:56 schrieb Damjan Jovanovic:
On Tue, Feb 13, 2024 at 3:12 PM Matthias Seidel 


wrote:


Hi Francis, All,

Am 12.02.24 um 17:00 schrieb F Campos Costero:

Hi Don,
There are several posts on the user forum about similar problems. For
example

https://forum.openoffice.org/en/forum/viewtopic.php?p=536089#p536089

The suggested solution is:
" Windows 11 has a new Clipboard Manager - go to Start > Settings, 
Click

Clipboard on the System tab and turn off *Suggested Actions*; if that
doesn't help, try turning off *Clipboard History"*
Please let us know if that works.

Yes, this seems to be a common problem on Windows, we have a lot of
complaints in the Microsoft Store about Calc being unstable.

@All: Anyone who has an idea how to fix this problem?



I think Firefox was also experiencing this and they fixed it:
https://support.mozilla.org/en-US/kb/firefox-hangs-when-copying-suggested-actions-windows-11 



Unfortunately their bug report is very long:
https://bugzilla.mozilla.org/show_bug.cgi?id=1774285

Possibly this was the fix, which calls OleFlushClipboard() after setting
the clipboard contents:
https://phabricator.services.mozilla.com/D160646


Thank you (again) for your valuable expertise!

Interesting that we are not alone with that problem... ;-)

I think it would be great to fix it, as the majority of our users are 
on Windows and the number of Windows 11 users is increasing.


Regards,

   Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Problem With Open Office and Windows 11 /11 Pro.

[Matthias Seidel]

Hi Damjan,

Am 13.02.24 um 16:56 schrieb Damjan Jovanovic:

On Tue, Feb 13, 2024 at 3:12 PM Matthias Seidel 
wrote:


Hi Francis, All,

Am 12.02.24 um 17:00 schrieb F Campos Costero:

Hi Don,
There are several posts on the user forum about similar problems. For
example

https://forum.openoffice.org/en/forum/viewtopic.php?p=536089#p536089

The suggested solution is:
" Windows 11 has a new Clipboard Manager - go to Start > Settings, Click
Clipboard on the System tab and turn off *Suggested Actions*; if that
doesn't help, try turning off *Clipboard History"*
Please let us know if that works.

Yes, this seems to be a common problem on Windows, we have a lot of
complaints in the Microsoft Store about Calc being unstable.

@All: Anyone who has an idea how to fix this problem?



I think Firefox was also experiencing this and they fixed it:
https://support.mozilla.org/en-US/kb/firefox-hangs-when-copying-suggested-actions-windows-11

Unfortunately their bug report is very long:
https://bugzilla.mozilla.org/show_bug.cgi?id=1774285

Possibly this was the fix, which calls OleFlushClipboard() after setting
the clipboard contents:
https://phabricator.services.mozilla.com/D160646


Thank you (again) for your valuable expertise!

Interesting that we are not alone with that problem... ;-)

I think it would be great to fix it, as the majority of our users are on 
Windows and the number of Windows 11 users is increasing.


Regards,

   Matthias



Regards
Damjan



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Problem With Open Office and Windows 11 /11 Pro.

[Matthias Seidel]

Hi Francis, All,

Am 12.02.24 um 17:00 schrieb F Campos Costero:

Hi Don,
There are several posts on the user forum about similar problems. For
example https://forum.openoffice.org/en/forum/viewtopic.php?p=536089#p536089
The suggested solution is:
" Windows 11 has a new Clipboard Manager - go to Start > Settings, Click
Clipboard on the System tab and turn off *Suggested Actions*; if that
doesn't help, try turning off *Clipboard History"*
Please let us know if that works.


Yes, this seems to be a common problem on Windows, we have a lot of 
complaints in the Microsoft Store about Calc being unstable.


@All: Anyone who has an idea how to fix this problem?

Regards,

   Matthias


Regards,
Francis

On Mon, Feb 12, 2024 at 8:22 AM sau...@optimum.net sau...@optimum.net <
sau...@optimum.net> wrote:


Hi,  My name is Donald Sauer. I have been working with Open Office with
Windows products from XP.   I am not sure where the problem starts. With
a speadsheets, Windows 11 or 11 Pro, when try to copy a line, cell,
sheet, from a current spreadsheet the product freezes and I can do any
other function with that spreadsheet. I must kill Open Office and
restart it. This is with both older spreeadsheets created with an older
Windows products, it continues to work with out any problems? I am not
sure if you are aware of this problem? I would more than happy to work
with folks, if you would require any further info or details of this
problem. Of course any fixes or updates that may be availble. My level
of Open Office is the latest from your site, Apache Open Office 4,
4.1.15 Date 2023-11-20 17:44.
Thank you for any Help, or info on this concern.
Don



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Article in "The Register" on CUA

[Matthias Seidel]

Hi Czesław,

Am 29.01.24 um 19:29 schrieb Czesław Wolański:

Hi Matthias,

I join Arrigo in thanking you for sharing. Very informative indeed.
Also, some of the comments on the said article are brilliant.


Il giorno ven 26 gen 2024 alle ore 20:57 Matthias Seidel <

matthias.sei...@hamburg.de> ha scritto:

Today I saw the new design of Microsoft Office 365.

I wonder how many people will now be busy to imitate that look. ;-)

Only that look? What about the "feel"? ;-)


So how does this "look and feel"? ;-)

https://support.microsoft.com/en-us/office/the-new-look-of-office-a6cdf19a-b2bd-4be1-9515-d74a37aa59bf

Regards,

   Matthias


Regards,
   Czesław

"Look and feel"
https://en.wikipedia.org/wiki/Look_and_feel



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Hi All,

Am 30.01.24 um 17:42 schrieb Jim Jagielski:



On Jan 30, 2024, at 7:53 AM, Jim Jagielski  wrote:




On Jan 30, 2024, at 5:23 AM, Matthias Seidel  wrote:

Hi Jim,

Am 30.01.24 um 11:11 schrieb Jim Jagielski:

macOS and Linux64 have also been uploaded.

Great!

I'll start on Linux32 bit builds today.



Those are now uploaded!


Great!

So what do we do with Dev5 now? Announce it?

Basically it is just a snapshot...

I would have liked to have more features, bugfixes and updated 
translations included, but maybe we are able to add that for Dev6?


Regarding translation, I worked hard on the Help files and some parts of 
the UI and the exported en-US.sdf is *much* cleaner now:


https://nightlies.apache.org/openoffice/install/linsnap-42x/?C=M;O=D

Additionally I put together the Help Authoring Tool (based on our 
current code):


https://home.apache.org/~mseidel/HelpAuthoring.oxt

I was able to tweak AOO on Linux to open existing XHP files, but this 
tool still needs a lot of attention from developers...


Regards,

   Matthias


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Aufnahme Referenzkundenliste

[Matthias Seidel]

Hi Damjan, All,

Am 31.01.24 um 17:45 schrieb Damjan Jovanovic:

Do they want this page updated:
http://www.openoffice.org/bizdev/consultants.html


That is a list of consultants.

But looking at it it seems very outdated, so we should work on that one, 
too.


Seems to be a generated from XML:

https://github.com/apache/openoffice-org/tree/main/assets/bizdev/consultants



How do we do that?

And let's keep it please.


Most likely he wants to be added to the German OpenOffice.org(!) 
customer list:


https://www.openoffice.org/de/marketing/referenzkunden.html

Regards,

   Matthias



Regards
Damjan

On Wed, Jan 31, 2024 at 4:26 PM Matthias Seidel 
wrote:


Has anyone worked on this?

Or should we remove this list at all?

Regards,

Matthias
Am 14.11.23 um 19:16 schrieb Florian Dederichs:

Hallo Apache Team,



Wir würden gerne in die Referenzkundenliste aufgenommen werden



Kunde: Operations & Consulting Munich GmbH

Adresse: Baaderstrasse 27a, 80469 München

Kontakt: Florian Dederichs

Bemerkung: Wir benutzen seit unserer Gründung 2017 OpenOffice und sind
extrem zufrieden was den Support und die Leistungen angeht. OpenOffice
beweist dass Open Source Projekte Sinn haben. Homepage:
https://www.ocmconsulting.de/



Herzlichen Dank und weiter so!



Florian Dederichs



*[image: OCM_Logo_FD small]*
<http://www.ocmconsulting.de/?utm_source=ocmlogo_medium=emailsignature_campaign=none>

FLORIAN DEDERICHS

GESCHÄFTSFÜHRER

*M.*   +49 160 93882573

*T.*   +49 89 23711368

*E. *florian.dederi...@ocmconsulting.de
*W.*   www.ocmconsulting.de
<http://www.ocmconsulting.de/?utm_source=websiteadress_medium=emailsignature_campaign=none>





Operations & Consulting Munich GmbH | HRB 235494 Amtsgericht München |
Sitz: München | Geschäftsführer: Florian Dederichs | USt-IdNr: DE313665900





Diese Nachricht und alle Anlagen sind vertraulich und ausschließlich für
den im Adressfeld genannten Adressaten bestimmt. Bitte informieren Sie uns,
wenn Sie nicht der vorgesehene Empfänger sein sollten und löschen Sie diese
Nachricht und alle Anlagen in Ihrem System. Jede unbefugte Nutzung,
Weiterleitung, Veränderung, Offenlegung gegenüber Dritten oder Fertigung
einer Kopie ist unzulässig. Da wir nicht die Echtheit oder Vollständigkeit
der in dieser Nachricht enthaltenen Informationen garantieren können,
schließen wir jede rechtliche Verbindlichkeit der vorstehenden Erklärungen
und Äußerungen aus.

This message and any attachment are confidential and may be privileged or
otherwise protected from disclosure. It is intended solely for the
mentioned person in the address field. Please inform us, if you are not the
intended recipient and delete the message and any attachment from your
system. Any use, modification, unauthorised dissemination, distribution or
copying hereof is prohibited. As we cannot guarantee the genuineness or
completeness of the information in the message, the statements set forth
above are not legally binding.






smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Aufnahme Referenzkundenliste

[Matthias Seidel]

Has anyone worked on this?

Or should we remove this list at all?

Regards,

   Matthias

Am 14.11.23 um 19:16 schrieb Florian Dederichs:


Hallo Apache Team,

Wir würden gerne in die Referenzkundenliste aufgenommen werden

Kunde: Operations & Consulting Munich GmbH

Adresse: Baaderstrasse 27a, 80469 München

Kontakt: Florian Dederichs

Bemerkung: Wir benutzen seit unserer Gründung 2017 OpenOffice und sind 
extrem zufrieden was den Support und die Leistungen angeht. OpenOffice 
beweist dass Open Source Projekte Sinn haben. Homepage: 
https://www.ocmconsulting.de/


Herzlichen Dank und weiter so!

Florian Dederichs

*OCM_Logo_FD 
small*




FLORIAN DEDERICHS

GESCHÄFTSFÜHRER

*M.***+49 160 93882573

*T.***+49 89 23711368

*E. 
***florian.dederi...@ocmconsulting.de

*W.***www.ocmconsulting.de

Operations & Consulting Munich GmbH | HRB 235494 Amtsgericht München | 
Sitz: München | Geschäftsführer: Florian Dederichs | USt-IdNr: DE313665900


Diese Nachricht und alle Anlagen sind vertraulich und ausschließlich 
für den im Adressfeld genannten Adressaten bestimmt. Bitte informieren 
Sie uns, wenn Sie nicht der vorgesehene Empfänger sein sollten und 
löschen Sie diese Nachricht und alle Anlagen in Ihrem System. Jede 
unbefugte Nutzung, Weiterleitung, Veränderung, Offenlegung gegenüber 
Dritten oder Fertigung einer Kopie ist unzulässig. Da wir nicht die 
Echtheit oder Vollständigkeit der in dieser Nachricht enthaltenen 
Informationen garantieren können, schließen wir jede rechtliche 
Verbindlichkeit der vorstehenden Erklärungen und Äußerungen aus.


This message and any attachment are confidential and may be privileged 
or otherwise protected from disclosure. It is intended solely for the 
mentioned person in the address field. Please inform us, if you are 
not the intended recipient and delete the message and any attachment 
from your system. Any use, modification, unauthorised dissemination, 
distribution or copying hereof is prohibited. As we cannot guarantee 
the genuineness or completeness of the information in the message, the 
statements set forth above are not legally binding.


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: FOSDEM 24

[Matthias Seidel]

Hi Michael,

Am 31.01.24 um 07:52 schrieb Dr. Michael Stehmann:

Hello,

Mechtilde and I plan to be there on Saturday (only).


Have fun! ;-)

Unfortunately I have canceled all travel plans at the moment...

Regards,

   Matthias



Regards
Michael

Am 14.01.24 um 12:12 schrieb Matthias Seidel:

Hi All,

Does anyone plan to go to FOSDEM [1] in Brussels this year?

I am still undecided, but it is always nice to meet persons in real 
life!


Regards,

    Matthias

[1] https://fosdem.org/2024/



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Hi Jim,

Am 30.01.24 um 11:11 schrieb Jim Jagielski:

macOS and Linux64 have also been uploaded.

Great!


Since these are developer builds and not intended to be release candidates, do 
we still need to bump? I guess we should anyway since these are now out in the 
wild.
I am not sure, but we did that with all dev builds before. And we tagged 
them. They are kind of official somehow.


In fact I have already committed the changes... ;-)

Regards,

   Matthias




On Jan 27, 2024, at 4:38 AM, Matthias Seidel  wrote:

All Windows builds are uploaded.

@Jim: We need to bump up the version number number, don't we?

Am 26.01.24 um 19:05 schrieb Matthias Seidel:

My AOO4.2.0-Dev5 Windows builds of #c51e9806e6 were successful and I will 
upload then (incl. hashes, etc.) soon to:

https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev5/

Regards,

Matthias

Am 24.01.24 um 18:32 schrieb Matthias Seidel:

Am 24.01.24 um 13:05 schrieb Jim Jagielski:

Are we ready for a Dev5 in any case?

I am ready as soon as we decide on a Git hash to build.

On Jan 15, 2024, at 10:02 AM, Matthias Seidel  
wrote:

Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1

On Jan 9, 2024, at 6:18 AM, Matthias Seidel  wrote:

Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all


On 01/09/2024 10:37 AM WET Matthias Seidel  wrote:
Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Is this a Linux fix only? What does boost do? Improve calculation speed?

I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

  Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
   Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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


-
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



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

All Windows builds are uploaded.

@Jim: We need to bump up the version number number, don't we?

Am 26.01.24 um 19:05 schrieb Matthias Seidel:
My AOO4.2.0-Dev5 Windows builds of #c51e9806e6 were successful and I 
will upload then (incl. hashes, etc.) soon to:


https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev5/

Regards,

   Matthias

Am 24.01.24 um 18:32 schrieb Matthias Seidel:

Am 24.01.24 um 13:05 schrieb Jim Jagielski:

Are we ready for a Dev5 in any case?

I am ready as soon as we decide on a Git hash to build.


On Jan 15, 2024, at 10:02 AM, Matthias Seidel 
 wrote:


Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1
On Jan 9, 2024, at 6:18 AM, Matthias Seidel 
 wrote:


Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all

On 01/09/2024 10:37 AM WET Matthias Seidel 
 wrote:

   Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194
Is this a Linux fix only? What does boost do? Improve 
calculation speed?
I already did a build for Windows, boost is part of our build 
system.


We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

 Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS

On Jan 7, 2024, at 5:55 PM, Keith N. McKenna 
 wrote:


Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we 
should now work towards a renewed Developer Edition 5 for 
AOO 4.2.0.
I am still in the massive process to clean up our Help 
files, so the whole translation process may be postponed to 
Dev 6.

Opinions?
Regards,
  Matthias
I think concentrating on a dev 5 would be a very good thing. 
We need to see movement on 4.2.0.


Regards
Keith



- 


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

- 


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Article in "The Register" on CUA

[Matthias Seidel]

Hi Arrigo,

Am 26.01.24 um 20:41 schrieb Arrigo Marchiori:

Hello,

On Thu, Jan 25, 2024 at 01:17:13PM +0100, Matthias Seidel wrote:


Hi All,

interesting article on CUA:

https://www.theregister.com/2024/01/24/rise_and_fall_of_cua/

Very informative IMHO. Thank you for sharing!

Another important, related concept is the Principle of Least
Astonishment:
https://en.wikipedia.org/wiki/Principle_of_least_astonishment


Today I saw the new design of Microsoft Office 365.

I wonder how many people will now be busy to imitate that look. ;-)

Regards,

   Matthias



Best regarsd,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

My AOO4.2.0-Dev5 Windows builds of #c51e9806e6 were successful and I 
will upload then (incl. hashes, etc.) soon to:


https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev5/

Regards,

   Matthias

Am 24.01.24 um 18:32 schrieb Matthias Seidel:

Am 24.01.24 um 13:05 schrieb Jim Jagielski:

Are we ready for a Dev5 in any case?

I am ready as soon as we decide on a Git hash to build.


On Jan 15, 2024, at 10:02 AM, Matthias Seidel 
 wrote:


Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1
On Jan 9, 2024, at 6:18 AM, Matthias Seidel 
 wrote:


Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all

On 01/09/2024 10:37 AM WET Matthias Seidel 
 wrote:

   Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194
Is this a Linux fix only? What does boost do? Improve 
calculation speed?
I already did a build for Windows, boost is part of our build 
system.


We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

 Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS

On Jan 7, 2024, at 5:55 PM, Keith N. McKenna 
 wrote:


Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we 
should now work towards a renewed Developer Edition 5 for 
AOO 4.2.0.
I am still in the massive process to clean up our Help 
files, so the whole translation process may be postponed to 
Dev 6.

Opinions?
Regards,
  Matthias
I think concentrating on a dev 5 would be a very good thing. 
We need to see movement on 4.2.0.


Regards
Keith



- 


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

- 


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Am 26.01.24 um 00:29 schrieb Jim Jagielski:

Current on AOO42X is c51e9806. Should we start there?

I would say so... ;-)



On Jan 24, 2024, at 12:32 PM, Matthias Seidel  
wrote:

Am 24.01.24 um 13:05 schrieb Jim Jagielski:

Are we ready for a Dev5 in any case?

I am ready as soon as we decide on a Git hash to build.

On Jan 15, 2024, at 10:02 AM, Matthias Seidel  
wrote:

Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1

On Jan 9, 2024, at 6:18 AM, Matthias Seidel  wrote:

Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all


On 01/09/2024 10:37 AM WET Matthias Seidel  wrote:
   Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Is this a Linux fix only? What does boost do? Improve calculation speed?

I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

 Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
  Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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


-
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



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Article in "The Register" on CUA

[Matthias Seidel]

Hi All,

interesting article on CUA:

https://www.theregister.com/2024/01/24/rise_and_fall_of_cua/

Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Am 24.01.24 um 13:05 schrieb Jim Jagielski:

Are we ready for a Dev5 in any case?

I am ready as soon as we decide on a Git hash to build.



On Jan 15, 2024, at 10:02 AM, Matthias Seidel  
wrote:

Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1

On Jan 9, 2024, at 6:18 AM, Matthias Seidel  wrote:

Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all


On 01/09/2024 10:37 AM WET Matthias Seidel  wrote:
   Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Is this a Linux fix only? What does boost do? Improve calculation speed?

I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

 Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
  Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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


-
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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: odf-1.3 branch pushed, progress update

[Matthias Seidel]

Hi Marcus, All,

Am 16.01.24 um 20:09 schrieb Marcus:

Am 16.01.24 um 17:50 schrieb Damjan Jovanovic:

I've now pushed my "odf-1.3" branch upstream, which has some initial ODF
1.3 compatibility patches, a patch adding a new constraint for the 
RECEIVED
function, and another to only make the upgrade dialog appear when 
version >

1.3.

There are 3 useful parts to the ODF 1.3 specification, part 2 dealing 
with

packaging, part 3 with the OpenDocument schema, and part 4 with
OpenFormula. So far I've mostly been developing part 4. Of the 34 issues
under part 4, 20 are now complete, which means part 4 development is
already 59% complete.


from zero to 59% in a few days. That's great.! :-)


So far only 1 issue needed a code change, and at least 1 more also will,
but the impression I get is that the vast majority of changes were 
made not
because ODF 1.3 is hugely different from ODF 1.2, but because parts 
of ODF

1.2 were wrong or ambiguous and they wanted to fix the specification for
the sake of better interoperability with other implementations (probably
Microsoft Office). A lot of the design decisions seem to have been 
made in

favour of AOO/LO, standardizing on how we already work, leaving us with
little or nothing to change :-).


That's interesting. So, when we want to support ODF 1.3 we just need 
to change / implement little code. That means also that no bigger or 
many problems should occur. At least this is my hope.

Even better.


Confluence has been working surprisingly well.


:-)


Would anyone like to help?


If you mean coding, then you have to teach me C++ first. ;-P
Honestly, here I won't be of any help. Other things depend.

Before we bring this into a release, we should discuss and define how 
we want or should offer the ODF 1.3 support.


My suggestion:

Instead of putting this as a selectable option in the Save dialog, we 
should add this to the other ODF version parts (see menu "Tools - 
Options - Load/Save - General - Default file format and ODF settings").


That is the right place, I think...

But before we can releasing anything, we must be able to translate new 
strings in changed dialogs and to modify our Help files accordingly.


There is still enough to do but I think we are on the right track.

Matthias



I don't know how loading is working. But I would expect that the 
header data is read and the ODF version is recognized with some magic 
numbers.


Marcus


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO crashes at start if Sitka*.ttc font

[Matthias Seidel]

Hi Arrigo,

Am 14.01.24 um 17:42 schrieb Arrigo Marchiori:

Hello Matthias, All,

On Sat, Jan 13, 2024 at 09:46:57PM +0100, Matthias Seidel wrote:


Hi Arrigo,

Am 13.01.24 um 21:36 schrieb Arrigo Marchiori:

Hello All,

Bug 128583 opened [1].

On Sat, Jan 13, 2024 at 11:58:59AM +0100, Matthias Seidel wrote:


Am 13.01.24 um 11:55 schrieb Dick Groskamp:

Works for me on Windows 11. AOO 4.1.15 (Dutch)

Yes, that ttc is distributed with Windows...

Seems to be Linux only? We might cross-check on macOS.

That would be a good idea.

I verified my last config.log on macOS. It says that fontconfig is not
used by that build. This means that the macOS builds are not affected
by this bug.

Good to know!



However, we are blatantly not following the suggestions from the
Fontconfig documentation [2], and we should fix that nevertheless.

The fix seems as easy as adding a single line:
FcDefaultSubstitute( pTestPattern );
after the instantiation of pTestPattern.

That seems to fix the crash. But then, the "Sitka" font does not seem
to show up in the selectors.

A ttc is not a single font but a font collection.

Maybe we have to add logic for that...

Fontconfig is used to _find_ installed fonts.  If the font does not
show up in the list, it is either not found (that would be
Fontconfig's problem) or not supported (and that's another library's
problem).


Let's fix this crash first.

Great!

It should be fixed in trunk, AOO41X and AOO42X now.


A good candidate for AOO 4.1.16 I guess... ;-)

Heh, sure!

According to Murphy's law, important bugs are found shortly _after_
release, not before... ;-)


After a release is always before a release...

That's why we have AOO41X (AOO4116-dev) open for commits! ;-)

Regards,

   Matthias



Best regards,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Am 10.01.24 um 19:14 schrieb Matthias Seidel:

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed


Committed it, didn't build on Linux Buildbot, reverted it.

I am out! If someone else is interested, please take over.

Matthias


+1


On Jan 9, 2024, at 6:18 AM, Matthias Seidel 
 wrote:


Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all

On 01/09/2024 10:37 AM WET Matthias Seidel 
 wrote:

  Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194
Is this a Linux fix only? What does boost do? Improve calculation 
speed?

I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

    Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS

On Jan 7, 2024, at 5:55 PM, Keith N. McKenna 
 wrote:


Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should 
now work towards a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, 
so the whole translation process may be postponed to Dev 6.

Opinions?
Regards,
 Matthias
I think concentrating on a dev 5 would be a very good thing. We 
need to see movement on 4.2.0.


Regards
Keith



- 


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


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




smime.p7s
Description: Kryptografische S/MIME-Signatur

FOSDEM 24

[Matthias Seidel]

Hi All,

Does anyone plan to go to FOSDEM [1] in Brussels this year?

I am still undecided, but it is always nice to meet persons in real life!

Regards,

   Matthias

[1] https://fosdem.org/2024/



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO crashes at start if Sitka*.ttc font

[Matthias Seidel]

Hi Arrigo,

Am 13.01.24 um 21:36 schrieb Arrigo Marchiori:

Hello All,

Bug 128583 opened [1].

On Sat, Jan 13, 2024 at 11:58:59AM +0100, Matthias Seidel wrote:


Am 13.01.24 um 11:55 schrieb Dick Groskamp:

Works for me on Windows 11. AOO 4.1.15 (Dutch)

Yes, that ttc is distributed with Windows...

Seems to be Linux only? We might cross-check on macOS.

That would be a good idea.

However, we are blatantly not following the suggestions from the
Fontconfig documentation [2], and we should fix that nevertheless.

The fix seems as easy as adding a single line:
   FcDefaultSubstitute( pTestPattern );
after the instantiation of pTestPattern.

That seems to fix the crash. But then, the "Sitka" font does not seem
to show up in the selectors.


A ttc is not a single font but a font collection.

Maybe we have to add logic for that...



Let's fix this crash first.


Great!

A good candidate for AOO 4.1.16 I guess... ;-)

Regards,

   Matthias



References:
  1: https://bz.apache.org/ooo/show_bug.cgi?id=128583
  2: 
https://www.freedesktop.org/software/fontconfig/fontconfig-devel/fcfontmatch.html

Best regards,


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO crashes at start if Sitka*.ttc font

[Matthias Seidel]

Am 13.01.24 um 11:55 schrieb Dick Groskamp:

Works for me on Windows 11. AOO 4.1.15 (Dutch)


Yes, that ttc is distributed with Windows...

Seems to be Linux only? We might cross-check on macOS.

Matthias



On 2024/01/13 08:07:58 "Paweł (Tomasz)" wrote:

Hello

If there is any Sitka.ttc font in .fonts folder AOO crashes at start.

guest@me:~$ openoffice4
Application Error

Fatal exception: Signal 6
Stack:
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37c3a)[0x7f1409e37c3a]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37d6c)[0x7f1409e37d6c]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37e09)[0x7f1409e37e09]
/lib64/libc.so.6(+0x40f10)[0x7f1409612f10]
/lib64/libc.so.6(pthread_kill+0xfc)[0x7f1409663e3c]
/lib64/libc.so.6(raise+0x12)[0x7f1409612e72]
/lib64/libc.so.6(abort+0xc1)[0x7f14095fa49b]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x1557dd)[0x7f14051557dd]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libsofficeapp.so(+0x2354b)[0x7f1409a2354b]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x17ff2e)[0x7f140517ff2e]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x36a02)[0x7f1409e36a02]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37dea)[0x7f1409e37dea]
/lib64/libc.so.6(+0x40f10)[0x7f1409612f10]
/lib64/libc.so.6(pthread_kill+0xfc)[0x7f1409663e3c]
/lib64/libc.so.6(raise+0x12)[0x7f1409612e72]
/lib64/libc.so.6(abort+0xc1)[0x7f14095fa49b]
/usr/lib64/libfontconfig.so.1(+0x875c)[0x7f14033bf75c]
/usr/lib64/libfontconfig.so.1(+0x1df55)[0x7f14033d4f55]
/usr/lib64/libfontconfig.so.1(+0x1e2d7)[0x7f14033d52d7]
/usr/lib64/libfontconfig.so.1(+0x1e3d7)[0x7f14033d53d7]
/usr/lib64/libfontconfig.so.1(FcFontMatch+0x68)[0x7f14033d6178]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x137375)[0x7f1405137375]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x137406)[0x7f1405137406]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager20countFontconfigFontsERSt8hash_mapIN3rtl7OStringEiNS2_11OStringHashESt8equal_toIS3_EE+0x35)[0x7f1405138c3b]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager10initializeEv+0x247)[0x7f1405144243]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN3psp16PrintFontManager3getEv+0x49)[0x7f1405145107]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvclplug_gen.so(_ZN14X11SalGraphics14GetDevFontListEP15ImplDevFontList+0x2c)[0x7f13fbc70156]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x25ab4c)[0x7f140525ab4c]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x261682)[0x7f1405261682]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZNK12OutputDevice14GetFontCharMapER11FontCharMap+0x33)[0x7f140526172d]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZNK12OutputDevice9HasGlyphsERK4FontRK6Stringtt+0x82)[0x7f1405261804]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3857de)[0x7f14053857de]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3858c4)[0x7f14053858c4]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x392017)[0x7f1405392017]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3153df)[0x7f14053153df]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x3154e3)[0x7f14053154e3]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x39ca26)[0x7f140539ca26]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(_ZN10WorkWindowC1EP6Windowl+0x3e)[0x7f140539cc3e]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bac78)[0x7f14065bac78]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bb191)[0x7f14065bb191]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libootk.so(+0x1bb3c3)[0x7f14065bb3c3]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x121de2)[0x7f13ff321de2]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x12291a)[0x7f13ff32291a]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x920de)[0x7f13ff2920de]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libfwk.so(+0x10484f)[0x7f13ff30484f]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libsofficeapp.so(+0x2e0e6)[0x7f1409a2e0e6]
/mnt/sda2/porteux/x86_64-apps/openoffice/opt/openoffice4/program/libvcl.so(+0x180813)[0x7f1405180813]

Re: ODF 1.3 development

[Matthias Seidel]

Hi Marcus,

Am 12.01.24 um 20:23 schrieb Marcus:

Am 12.01.24 um 19:19 schrieb Marcus:

Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:

[...]

Can someone please create such a Wiki page, or give me access to do so?

[...]


that's a good idea. I'll create a new page in our Confluence Wiki.


please have look here:

https://cwiki.apache.org/confluence/display/OOOUSERS/ODF+1.3+Changes


That looks great!

Matthias



You should have access to the page, so you can finish the first items 
yourself.


Marcus


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Para site

[Matthias Seidel]

Hi,

I don't see a problem with that site...

It promotes OpenOffice to French users. It claims to be non-official 
"Open-office.fr est un site non officiel dédié à la communauté francophone."


It has a link to our official website, all download links point to our 
official download page.


The only "problem" I see is that it seems outdated in parts and some 
links are dead.


Maybe you could try to contact them to help updating the page?

Regards,

   Matthias

Am 12.01.24 um 17:41 schrieb Bidouille:

Hello,

Fake site with
https://open-office.fr/

Did we have a process to fight this?

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Calc Page Preview Broken by Column

[Matthias Seidel]

Hi All,

I really don't see a broken page preview.

However, it takes *much* longer to display it.

Resetting the Print Ranges (Format - Print Ranges - Remove) brings it 
back to normal.


Of course this must be investigated further...

Regards,

   Matthias

Am 10.01.24 um 23:22 schrieb Pedro Lino:

Hi Dean
  
Thank you for reporting this issue. I can confirm that it occurs both in the Linux and the Windows version of AOO 4.1.15
  
Did you report the bug at

https://bz.apache.org/ooo/ ? If not I can do that for you if you wish
  
All the best,

Pedro


On 01/10/2024 1:40 AM WET Dean W  wrote:
  
  
Dear Friends,
  
I have found a strange bug within a Calc document. I added column A, to a working document, and this broke the page preview.
  
Broken file - https://filebin.net/4g8yy55dvm9y85xl

Fixed file - https://filebin.net/t1t4isno5tww76tn
  
If you open the broken file, try to page preview. It will not load well, or quickly. To fix, delete column A, and it should fix the issue.
  
Reported from AOO4111m1(Build:9808)  -  Rev. bdb20b2a64 (Linux x86_64)
  
Attached and linked are the files in question
  


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Can't create pages in the Wiki

[Matthias Seidel]

Am 11.01.24 um 09:39 schrieb Matthias Seidel:

Hi Damjan,

Maybe it would be easier to create (and maintain) a page on our MWiki?


I meant of course our CWiki (Confluence).

Matthias



Regards,

   Matthias

Am 09.01.24 um 17:02 schrieb Damjan Jovanovic:

Hi

I don't seem to have permission to create new pages in the Wiki (
wiki.openoffice.org).

Can someone please give me access?

Thank you
Damjan (also my Wiki username)



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Can't create pages in the Wiki

[Matthias Seidel]

Hi Damjan,

Maybe it would be easier to create (and maintain) a page on our MWiki?

Regards,

   Matthias

Am 09.01.24 um 17:02 schrieb Damjan Jovanovic:

Hi

I don't seem to have permission to create new pages in the Wiki (
wiki.openoffice.org).

Can someone please give me access?

Thank you
Damjan (also my Wiki username)



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Am 10.01.24 um 15:01 schrieb Jim Jagielski:

Lets fold this in and build -Dev5 after it's committed

+1



On Jan 9, 2024, at 6:18 AM, Matthias Seidel  wrote:

Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all


On 01/09/2024 10:37 AM WET Matthias Seidel  wrote:
  Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Is this a Linux fix only? What does boost do? Improve calculation speed?

I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.


In any case, +1 to updating libraries

That is the intention.

Regards,

Matthias


Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
 Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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


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




smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Hi Pedro,

Am 09.01.24 um 12:08 schrieb Pedro Lino:

Hi Matthias, all


On 01/09/2024 10:37 AM WET Matthias Seidel  wrote:
  
Unless someone else volunteers, I can do the Windows builds.

Please do ;)


Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Is this a Linux fix only? What does boost do? Improve calculation speed?


I already did a build for Windows, boost is part of our build system.

We need to check for macOS/Linux now.



In any case, +1 to updating libraries


That is the intention.

Regards,

   Matthias



Best,
Pedro


Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
 Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Unless someone else volunteers, I can do the Windows builds.

Something we want to integrate?

How about this PR:

https://github.com/apache/openoffice/pull/194

Regards,

   Matthias

Am 08.01.24 um 14:06 schrieb Jim Jagielski:

I'm up for doing the dev tarballs for Linux and macOS


On Jan 7, 2024, at 5:55 PM, Keith N. McKenna  wrote:

Matthias Seidel wrote:

Hi All,
and a happy new year!
After successfully releasing AOO 4.1.15 in December we should now work towards 
a renewed Developer Edition 5 for AOO 4.2.0.
I am still in the massive process to clean up our Help files, so the whole 
translation process may be postponed to Dev 6.
Opinions?
Regards,
Matthias

I think concentrating on a dev 5 would be a very good thing. We need to see 
movement on 4.2.0.

Regards
Keith



-
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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Keyboard mappings to macros became unavailable when AOO is started from C++

[Matthias Seidel]

Hi and welcome,

Am 07.01.24 um 14:26 schrieb SET:

Hi,

This issue is observed on Linux in 4.1.15 and 4.5.0. It is not observed in
4.1.7.

A C++ application starts AOO using bootstrap() and text documents are created
from *.ott templates containing basic macros. Some macros have bindings to
keyboard combinations, all defined in the UI.

In 4.1.7, the keyboard bindings work as expected in unsaved new documents.

In 4.1.15 and 4.5.0, the macros are not called by the keyboard shortcuts when
a new file is generated from a template. Executing the macros directly using
the UI dialogs succeeds.

The bindings will work in 2 circumstances:

  - the newly generated document is saved and reloaded via the File menu,
  - the newly generated document is saved, closed and opened again.
  
If AOO is started from bash, without being started by the controlling

application, the bindings just work.

Thank you for any input, help and eventual resolution.


@All:

This refers to a Bugzilla issue:

https://bz.apache.org/ooo/show_bug.cgi?id=128582

It seems to occur since AOO 4.1.12. Any idea what we changed in that 
version?


Regards,

   Matthias



Regards.



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

AOO 4.2.0-Dev5 ?

[Matthias Seidel]

Hi All,

and a happy new year!

After successfully releasing AOO 4.1.15 in December we should now work 
towards a renewed Developer Edition 5 for AOO 4.2.0.


I am still in the massive process to clean up our Help files, so the 
whole translation process may be postponed to Dev 6.


Opinions?

Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [PR] Attempt to update Boost to version 1.79 [openoffice]

[Matthias Seidel]

Hi Pedro,

I will try to build this PR on Windows, when time permits...

Regards,

   Matthias

Am 19.12.23 um 20:31 schrieb pgiffuni (via GitHub):

pgiffuni opened a new pull request, #192:
URL: https://github.com/apache/openoffice/pull/192

Newer versions of boost will require a C++14 enabled compiler to build. 
Older versions are really painful to patch to work with newer compilers. This 
version includes pretty much all the patches required from the previous 
versions so are expected to build without much trouble with most compilers.

While here also bring some really nice headers and libraries we sloppily never really cared to install, but could be really useful to extend AOO's functionality.

Mostly tested on FreeBSD, which still fails due to unrelated compiler pickiness.  Mileage may vary on Windows and OS/2: there is no TR1 support any more..





smime.p7s
Description: Kryptografische S/MIME-Signatur

AOO 4.1.15 Release Schedule

[Matthias Seidel]

Hi All,

I have now signed and re-uploaded all Windows binaries.

The Release Schedule was updated as far as I was involved:

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15

Regards,

   Matthias



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC2 as GA

[Matthias Seidel]

Hi All,

I don't think we can expect any more votes... Thanks to those who did 
take the time to test!


Quick reminder:

I am only available until December 23.

If we want to release 4.1.15 this year we need to do it soon. Otherwise 
we must postpone it to 2024.


Regards,

   Matthias

Am 07.12.23 um 17:17 schrieb Matthias Seidel:

Hi Czesław,

Am 07.12.23 um 17:13 schrieb Czesław Wolański:

Hi All,

The Release Candidate is good for production/GA:
    [X] yes / +1
    [ ] no / -1

My vote is based on:
    [X] binding (member of PMC)
    [X] I have built and tested the RC from source on Windows 10 64-bit
 en-US (full)
    [X] I have tested the binary RC on Windows 7 and 11 (both 64-bit) 
with

two configurations:
 1. pl (full) + de, en-US, fr (langpack)
 2. en-US (full) + de, fr, pl (langpack).

Regards,
Czesław


Can you please post that also in the [VOTE] thread?

I don't think it gets lost here, but "sicher ist sicher"! ;-)

Regards,

   Matthias



Le jeu. 7 déc. 2023 à 12:04, Matthias Seidel 
 a

écrit :


Hi Marcus,

Am 06.12.23 um 19:12 schrieb Marcus:

To push this topic:

I'll find time for testing on Friday or Saturday.

What about others?

And we still have open tasks (even for the easiest things) in our
Release Schedule:

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15

Is there really no big interest in a release here?

Matthias


Marcus



Am 28.11.23 um 16:45 schrieb Jim Jagielski:

I am calling a VOTE on releasing the source and complimentary
community builds of Apache OpenOffice 4.1.15-RC2 as GA.

These artifacts can be found at:

https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/

Please cast your vote:

The Release Candidate is good for production/GA:
 [ ] yes / +1
 [ ] no / -1

My vote is based on:
 [ ] binding (member of PMC)
 [ ] I have built and tested the RC from source on platform [ ]
 [ ] I have tested the binary RC on platform [ ]


This vote will be open for 14 days to allow for sufficient time for
testing, review, and voting.


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Open letter to TDF

[Matthias Seidel]

Hi All,

Am 11.12.23 um 13:14 schrieb Pedro Lino:

+1
More important than which Office people prefer, it would be really good if the 
ODF file format is more widely adopted instead of the increasingly proprietary 
MS Office XML.
In that sense, implementation of ODF 1.3 in OpenOffice would be a real progress!


A real progress would be to release a new version (AOO42X) where we 
would be able to integrate such changes in the future.


At the "moment" we are stuck with 4.1.x.

We have our own problems to solve...

Matthias


Best,
Pedro


On 12/11/2023 11:02 AM WET Jim Jagielski  wrote:

  
Maybe new leadership at TDF will encourage cooperation between LO and AOO instead of still harboring ill-will between the 2 efforts.



On Dec 11, 2023, at 2:28 AM, Bidouille  wrote:


For some months now, the libreoffice community has been in turmoil.
A new committee is set to oust the existing members[1].
Perhaps it would be a good idea to write an open letter urging everyone to join 
OpenOffice.


:-)


[1]https://nextcloud.documentfoundation.org/s/Kx4ttBtdJET9tPF

-
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

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC2 as GA

[Matthias Seidel]

Hi Czesław,

Am 07.12.23 um 17:13 schrieb Czesław Wolański:

Hi All,

The Release Candidate is good for production/GA:
[X] yes / +1
[ ] no / -1

My vote is based on:
[X] binding (member of PMC)
[X] I have built and tested the RC from source on Windows 10 64-bit
 en-US (full)
[X] I have tested the binary RC on Windows 7 and 11 (both 64-bit) with
two configurations:
 1. pl (full) + de, en-US, fr (langpack)
 2. en-US (full) + de, fr, pl (langpack).

Regards,
Czesław


Can you please post that also in the [VOTE] thread?

I don't think it gets lost here, but "sicher ist sicher"! ;-)

Regards,

   Matthias



Le jeu. 7 déc. 2023 à 12:04, Matthias Seidel  a
écrit :


Hi Marcus,

Am 06.12.23 um 19:12 schrieb Marcus:

To push this topic:

I'll find time for testing on Friday or Saturday.

What about others?

And we still have open tasks (even for the easiest things) in our
Release Schedule:

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15

Is there really no big interest in a release here?

Matthias


Marcus



Am 28.11.23 um 16:45 schrieb Jim Jagielski:

I am calling a VOTE on releasing the source and complimentary
community builds of Apache OpenOffice 4.1.15-RC2 as GA.

These artifacts can be found at:

https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/

Please cast your vote:

The Release Candidate is good for production/GA:
 [ ] yes / +1
 [ ] no / -1

My vote is based on:
 [ ] binding (member of PMC)
 [ ] I have built and tested the RC from source on platform [ ]
 [ ] I have tested the binary RC on platform [ ]


This vote will be open for 14 days to allow for sufficient time for
testing, review, and voting.


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

FYI:

I disabled CouchDB now...

Regards,

   Matthias

Am 26.11.23 um 18:25 schrieb Matthias Seidel:

Hi Dave, All,

Did you get any (offline) reaction from JMeter or CouchDB?

I see that Subversion is interested in some translated strings, so we 
should keep it for the moment.


Regards,

   Matthias

Am 26.11.23 um 04:48 schrieb Keith N. McKenna:

Matthias Seidel wrote:

Hi All,

No reaction on the CouchDB and JMeter dev-lists for 3 weeks...

Should we disable these projects on our Pootle server? It is just 
one click for me... ;-)


Opinions?

Regards,

    Matthias

Am 01.11.23 um 19:37 schrieb Dave Fisher:
The OpenOffice project wishes to update the Pootle server 
(translate.Apache.org) that we share to translation software that 
is maintained. Pootle development stopped over four years ago.


Please let OpenOffice know if you still use the service and if you 
do would you like to cooperate on the upgrade?


For OpenOffice,
Dave

Sent from my iPhone

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


+1 for me. Have't seen activity in some time

Regards
Keith


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC2 as GA

[Matthias Seidel]

Hi Marcus,

Am 06.12.23 um 19:12 schrieb Marcus:

To push this topic:

I'll find time for testing on Friday or Saturday.

What about others?


And we still have open tasks (even for the easiest things) in our 
Release Schedule:


https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15

Is there really no big interest in a release here?

Matthias



Marcus



Am 28.11.23 um 16:45 schrieb Jim Jagielski:
I am calling a VOTE on releasing the source and complimentary 
community builds of Apache OpenOffice 4.1.15-RC2 as GA.


These artifacts can be found at:

https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/

Please cast your vote:

The Release Candidate is good for production/GA:
    [ ] yes / +1
    [ ] no / -1

My vote is based on:
    [ ] binding (member of PMC)
    [ ] I have built and tested the RC from source on platform [ ]
    [ ] I have tested the binary RC on platform [ ]


This vote will be open for 14 days to allow for sufficient time for 
testing, review, and voting.



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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Extension and publish

[Matthias Seidel]

Hi,

Am 07.12.23 um 10:39 schrieb Bidouille:

FYI unable to upload an OXT hosting on SF
I got an error
The website encountered an unexpected error. Please try again later.


Sorry, I cannot help you here, please contact the SourceForge Help Desk.

BTW: Did you test AOO 4.1.15-RC2?

Some people might not be aware of it, but everyone is allowed to 
download, test AND vote on a Release Client.


Although that vote is not binding it helps those who invested a lot of 
private time in a release to get feedback.


Regards,

   Matthias



- Mail original -

De: "Matthias Seidel" 
À: dev@openoffice.apache.org
Envoyé: Mercredi 6 Décembre 2023 17:04:45
Objet: Re: Extension and publish

Done!

Am 06.12.23 um 15:20 schrieb Bidouille:

Another one:
https://extensions.openoffice.org/en/project/wizard-split-hsql-embedded-database
Thanks

- Mail original -----

De: "Matthias Seidel" 
À: dev@openoffice.apache.org
Envoyé: Dimanche 29 Octobre 2023 19:14:10
Objet: Re: Extension and publish

Done!

Am 29.10.23 um 19:08 schrieb Bidouille:

Hello,
Who has suffisient karma to publish my extension?

- Mail transféré -
De: "Bidouille" 
À: nore...@extensions.openoffice.org
Envoyé: Lundi 9 Octobre 2023 21:09:02
Objet: Thanks to publish

https://extensions.openoffice.org/en/project/odb-cleaner

-
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


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: is it possible to build trunk with system OpenSSL?

[Matthias Seidel]

Hi Yury,

Unfortunately I am no developer, but I know that the OS/2-port builds 
with system-openssl.


https://github.com/apache/openoffice/blob/trunk/main/configure.cmd

I assume you want to build on some kind of Linux?

Regards,

   Matthias

Am 04.12.23 um 16:48 schrieb Yury Tarasievich:

Hi all,

I'm trying to build the trunk codebase with maximum use of system libs 
and specifically with --with-system-openssl=yes, to get rid of the 
update routine crashing.


The build seems to complete okay, but in the instsetoo_native stage it 
breaks, telling me:


ERROR: File not found: libcrypto.so
ERROR: File not found: libssl.so

I couldn't understand the problem well enough, but these files 
(present in-system) SEEM to be always required to be in the AOO build 
tree, in order to be copied, regardless of what configure option was 
used.


Any advice, please?

-Yury

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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Extension and publish

[Matthias Seidel]

Done!

Am 06.12.23 um 15:20 schrieb Bidouille:

Another one:
https://extensions.openoffice.org/en/project/wizard-split-hsql-embedded-database
Thanks

- Mail original -

De: "Matthias Seidel" 
À: dev@openoffice.apache.org
Envoyé: Dimanche 29 Octobre 2023 19:14:10
Objet: Re: Extension and publish

Done!

Am 29.10.23 um 19:08 schrieb Bidouille:

Hello,
Who has suffisient karma to publish my extension?

- Mail transféré -
De: "Bidouille" 
À: nore...@extensions.openoffice.org
Envoyé: Lundi 9 Octobre 2023 21:09:02
Objet: Thanks to publish

https://extensions.openoffice.org/en/project/odb-cleaner

-
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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Fwd: Input Needed: Software for the Public Good Stories

[Matthias Seidel]

Hi All,

FYI

Matthias



 Weitergeleitete Nachricht 
Betreff:Re: Input Needed: Software for the Public Good Stories
Datum:  Tue, 28 Nov 2023 10:57:35 -0800
Von:Whitney True 
Antwort an: d...@community.apache.org
An: d...@community.apache.org
Kopie (CC): mark...@apache.org



Hello ASF Community,

The ASF M team is hoping to showcase how the ASF Community has helped
provide software for the public good in celebration of the ASF's 25th
anniversary. We hope you will be willing to share a story for the ASF blog
and social media channels. Please fill out this short form.


Here is a reminder of the types of stories we are looking for:

- Case studies that showcase how your project’s technology is being used;
- Details surrounding an important forthcoming project milestone; or
- Any other ways your project embodies the ASF mission and way? Please
use this form anytime you have an exciting milestone to share.


*And please note you can submit more than once!*
Many thanks for your time and input,
Whitney
On Behalf of the ASF M team

On Tue, Nov 7, 2023 at 9:30 AM Whitney True  wrote:


Hello ASF Community,

As the ASF nears its 25th anniversary, we want to showcase how the ASF
community has helped realize the Foundation's mission of providing software
for the public good.

The ASF Marketing & Publicity (M) team will be showcasing major
milestones and public good stories across the ASF’s blog and social media
channels. We hope you'll be willing to share a story by filling out this
short form.

What are we looking for?

- Case studies that showcase how your project’s technology is being
used;
- Details surrounding an important forthcoming project milestone; or
- Any other ways your project embodies the ASF mission and way? Please
use this form anytime you have an exciting milestone to share.

***Please note you can submit more than once!** *

Many thanks for your time and input,
Whitney
On Behalf of the ASF M team








smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [VOTE] Release AOO 4.1.15-RC2 as GA

[Matthias Seidel]

Hi All,

The Release Candidate is good for production/GA:
    [x] yes / +1
    [ ] no / -1

 My vote is based on:
    [x] binding (member of PMC)
    [x] I have built and tested the RC from source on platform [Windows 
10 - 64bit]
    [x] I have tested the binary RC on platform [Windows 10 - 64bit, 
Windows 11 - 64bit, Windows 7 - 32bit, Ubuntu 22.04 - 64bit, Ubuntu 
16.04 - 64bit, macOS 14.1.1 (M1 processor)]


I did test German Full Installations. Additionally I tested en-US and pl 
Language Packs.


Regards,
   Matthias

Am 28.11.23 um 16:45 schrieb Jim Jagielski:

I am calling a VOTE on releasing the source and complimentary community builds 
of Apache OpenOffice 4.1.15-RC2 as GA.

These artifacts can be found at:

https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/

Please cast your vote:

The Release Candidate is good for production/GA:
[ ] yes / +1
[ ] no / -1

My vote is based on:
[ ] binding (member of PMC)
[ ] I have built and tested the RC from source on platform [ ]
[ ] I have tested the binary RC on platform [ ]


This vote will be open for 14 days to allow for sufficient time for testing, 
review, and voting.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

Hi Dave, All,

Did you get any (offline) reaction from JMeter or CouchDB?

I see that Subversion is interested in some translated strings, so we 
should keep it for the moment.


Regards,

   Matthias

Am 26.11.23 um 04:48 schrieb Keith N. McKenna:

Matthias Seidel wrote:

Hi All,

No reaction on the CouchDB and JMeter dev-lists for 3 weeks...

Should we disable these projects on our Pootle server? It is just one 
click for me... ;-)


Opinions?

Regards,

    Matthias

Am 01.11.23 um 19:37 schrieb Dave Fisher:
The OpenOffice project wishes to update the Pootle server 
(translate.Apache.org) that we share to translation software that is 
maintained. Pootle development stopped over four years ago.


Please let OpenOffice know if you still use the service and if you 
do would you like to cooperate on the upgrade?


For OpenOffice,
Dave

Sent from my iPhone

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


+1 for me. Have't seen activity in some time

Regards
Keith


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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

Hi,

Am 23.11.23 um 19:44 schrieb Czesław Wolański:

Hi All,

Le jeu. 23 nov. 2023 à 19:12, Matthias Seidel a écrit :

No reaction on the CouchDB and JMeter dev-lists for 3 weeks...

Long enough to make an informed decision...


Should we disable these projects on our Pootle server? It is just one
click for me... ;-)

"That’s one small step for (a) man. One giant leap for mankind."  ;-)

Just in case: is it reversible?


Yes, it would be reversible.

But I have not seen real activity for these two projects on our Pootle 
server for years.


Regards,

   Matthias



Regards,
Czesław



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: Pootle Server Update

[Matthias Seidel]

Hi All,

No reaction on the CouchDB and JMeter dev-lists for 3 weeks...

Should we disable these projects on our Pootle server? It is just one 
click for me... ;-)


Opinions?

Regards,

   Matthias

Am 01.11.23 um 19:37 schrieb Dave Fisher:

The OpenOffice project wishes to update the Pootle server 
(translate.Apache.org) that we share to translation software that is 
maintained. Pootle development stopped over four years ago.

Please let OpenOffice know if you still use the service and if you do would you 
like to cooperate on the upgrade?

For OpenOffice,
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: Kryptografische S/MIME-Signatur

Re: RECALLED (Re: [VOTE] Release AOO 4.1.15-RC1 as GA)

[Matthias Seidel]

Hi All,

I have now built and uploaded the Windows binaries for AOO 4.1.15-RC2 
based on Git #5f13fa0070:


https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC2/binaries/

Regards,

   Matthias

Am 20.11.23 um 14:08 schrieb Jim Jagielski:

I am recalling and closing this VOTE as we work on getting a RC2 release out.

Thanks to all who tested and voted!!


On Nov 1, 2023, at 10:54 AM, Jim Jagielski  wrote:

I am calling a VOTE on releasing the source and complimentary community builds 
of Apache OpenOffice 4.1.15-RC1 as GA.

These artifacts can be found at:

https://dist.apache.org/repos/dist/dev/openoffice/4.1.15-RC1/

Please cast your vote:

The Release Candidate is good for production/GA:
[ ] yes / +1
[ ] no / -1

My vote is based on:
[ ] binding (member of PMC)
[ ] I have built and tested the RC from source on platform [ ]
[ ] I have tested the binary RC on platform [ ]


This vote will be open for 14 days to allow for sufficient time for testing, 
review, and voting.
-
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



smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC1 as GA

[Matthias Seidel]

+1

Regards,

   Matthias

Am 19.11.23 um 22:16 schrieb Arrigo Marchiori:

Hello Jim, All,

On Sun, Nov 19, 2023 at 08:59:46AM -0500, Jim Jagielski wrote:


Are there any patches or additions anyone thinks would be
appropriate to add in for a RC2 or is RC1 "good enough"?

I suggest we build a -RC2 from the current head of AOO41X.

We would include the solution for bug 126680 [1], a long-standing
problem involving builds for non-latin Alphabets.

Best regards.

1: https://bz.apache.org/ooo/show_bug.cgi?id=126680


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [DISCUSS][VOTE] Release AOO 4.1.15-RC1 as GA

[Matthias Seidel]

Hi Marcus,

Am 10.11.23 um 23:21 schrieb Marcus:

At the moment I'm very busy with my daily job and private things.
I hope to have the time on Sunday or Monday.

Sorry for exhaust the vote this time.


Take your time! ;-)

@All: There are still a lot of tasks open in our Release Schedule:

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.15

If you want to participate, please volunteer!

Regards,

   Matthias



Marcus



Am 01.11.23 um 15:54 schrieb Jim Jagielski:

[...]
  This vote will be open for 14 days to allow for sufficient time for 
testing, review, and voting.

[...]


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



smime.p7s
Description: Kryptografische S/MIME-Signatur