Sorry for the silence - I'll explain later. We currently have two high
priority items:
1. Testing a release candidate, 4.1.4 RC2. This subdivides into either
doing your own builds by checking out the source code or downloading and
testing ready built versions. Testing pre-built versions is important,
and does not require the ability to build OpenOffice.
2. Hunting the current most-wanted bug. This requires C++ debug skill
and building OpenOffice. Sometimes, during OpenOffice close or crash or
removing a drive or closing the lid on a laptop, OpenOffice leaves a
file corrupted - it appears to only contain "#" symbols. I am in the
process of learning my way around the file save code, and would welcome
any help.
See https://bz.apache.org/ooo/show_bug.cgi?id=107558 for a typical bug
report.
In the longer term, I have proposed a refactoring project. Some past
bugs have been due to accessing outside the bounds of an array. The
refactoring would replace fixed sized arrays with STL objects, and use
range-checked accesses.
On 8/12/2017 11:52 PM, Chien Chien Frank wrote:
Hi Sandeep,
Nice to receive your email. But, there must be something wrong. I am
also looking to volunteer to contribute to the OpenOffice project, but no
body replied me.
I don't know what is going on for their system...
If you know, would you please let me know.
Thank,
Chien
2017-08-12 22:55 GMT-07:00 Sandeep Khurana <sandeep_khur...@live.com>:
Hello Sir,
I would like to contribute to the OpenOffice development. I have good
hands on Experience of 10+ Years in C/C++ and Java.
Please include me in the subscription mailing list. I have attached my
updated Resume here.
Let me know if any other details are required.
Best
SAndeep Khurana
+91-97175-28742 <+91%2097175%2028742>
