[PATCH] Make LibreOffice waterproof

[Jesús Corrius]

Hi all,

The rise of portable computers and electronic devices such as laptops,
tablets and smart phones also means that software has to operate in
more extreme weather conditions than it used to. This patch [1] is a
small step in the right direction as it adds water resistant
characteristics to LibreOffice.

The patch introduces a new constant defined as:

#define SAL_WATER_RESISTANCE_DEGREE 100

You can modify this value by manually editing the new added file
sal/inc/sal/waterproofing.h. For your convenience it can also be
defined at compile time using the configure script option:

$ ./configure --with-water-resistance-degree=100

The valid values are defined as follows:

* SAL_WATER_RESISTANCE_DEGREE = 30

- Suitable for everyday use, including Writer and Calc. Splash/rain
resistant. NOT suitable for swimming, snorkeling, water related work
and fishing. NOT suitable for diving.

* SAL_WATER_RESISTANCE_DEGREE = 50

- Now you can also use Impress and Draw. It's suitable for swimming,
white water rafting, non-snorkeling water related work, and fishing.
NOT suitable for diving.

* SAL_WATER_RESISTANCE_DEGREE = 100

- Suitable for recreational surfing, swimming, snorkeling, sailing and
water sports. NOT suitable for diving. This is the default. You can
use all the LibreOffice characteristics with a minium tradeoff between
water resistance and power consumption.

* SAL_WATER_RESISTANCE_DEGREE = 150

- Minimum ISO standard (ISO 6425) for scuba diving at depths NOT
suitable for saturation diving.

* SAL_WATER_RESISTANCE_DEGREE = 200

- Suitable for professional marine activity and serious surface water
sports. NOT suitable for saturation diving. If you are using it for
professional marine activity, you should disable Java first.

* SAL_WATER_RESISTANCE_DEGREE = 300

- Suitable for scuba diving at depths NOT suitable for saturation
diving. High power consumption. At this level, Valgrind will start
complaining about memory leaks.

* SAL_WATER_RESISTANCE_DEGREE = 500

- Suitable for saturation diving (helium enriched environment).
LibreOffice versions compiled with this setting should be marked as
PROFESSIONAL DIVER’S LIBREOFFICE L M FOR MIXED-GAS DIVING to point
this out. You need a valid certificate issued by The Document
Foundation to distribute it.


After applying this patch, it should be carefully tested by our QA
community. This is the proposed set of tests:

* Resistance when immersed in water at a depth of 10 cm. Immersion in
10 cm of water for 1 hour.

* Resistance of operative parts. Immersion in 10 cm of water with a
force of 5 N perpendicular to the About Box for 10 minutes.

* Condensation test. It shall be placed on a heated plate at a
temperature between 40 °C and 45 °C until it has reached the
temperature of the heated plate (in practice, a heating time of 10
minutes to 20 minutes, depending on the programming language
component, will be sufficient). A drop of water, at a temperature
between 18 °C and 25 °C shall be placed on the screen. After about 1
minute, the glass shall be wiped with a dry rag.

* Resistance to different temperatures. Immersion of 10 cm of water at
the following temperatures for 5 minutes each, 40 °C, 20 °C and 40 °C
again, with the transition between temperatures not to exceed 1
minute. No evidence of water intrusion or condensation is allowed.

* Resistance to water overpressure. Immersion in a suitable pressure
vessel and subjecting it within 1 minute to the rated pressure for 10
minutes, or to 2 bar in case where no additional indication is given.
Then the overpressure is reduced to the ambient pressure within 1
minute. No evidence of water intrusion or condensation is allowed.

* Resistance to air overpressure. Exposing the software to an
overpressure of 2 bar. The modified Word Count Dialog shall show no
air-flow exceeding 50 μg/min.


As it is a very big patch, I had to compress it and upload it here:


[1] http://dl.dropbox.com/u/193133/libreoffce-water-resistant-patch.zip


Please, also apply this patch to the LibreOffice-3-5 branch. We don't
want to leave the users of the stable version unprotected. Do we?

-- 
Jesús Corrius <jesus at softcatala.org>