Change-Id: Ic62e3f26b2cda28e823c465efb78a397fe781d51

Change-Id: I3b20ef70dac4dc9905a169245e0b48b98a20c697

Change-Id: I71fa1bf82b879a1da69ca78d53bcf8072bdfa9ae

Change-Id: Ia6083c423bf8286a0b562d490283f8e1328a0124

Change-Id: I3cb23461718c5713c1e76d0b37d92b3e7849d13b

Change-Id: I72ba74164e660bfbe496cc63b98e397ee1e2425c

Change-Id: I2a33095f7dceb564911478a30aed1137ddacd531

Don't even think about using the new skip flag for your shiny new test.
If you itnroduce tests that show validation errors fix them!!

Change-Id: I21bf61a113a35ca204a54d18246848a5788ae559

Change-Id: I28c735478142bcb438ac24482612d5fb52a65f6e

Change-Id: Ic174dee2b0c3005b15b30348bf6aebf20ce50fb8

Change-Id: I1a613899d18a004149d3e637d796bc2f6687e6c4

Change-Id: I24d63386d158e130aeb340235d71eb05cbd679f4

Change-Id: I5820bde974a42f32c404aa2b14b410534f10db29

Change-Id: Id1466f7a95470a7c90a7752971e126d3f4b45766

Change-Id: I1ec67a8697148d650f56650c6320964ac39dfedf

Change-Id: Icd728e03ac605a05fc9a1f001e2becaf1536ce7d

Change-Id: I029c77aac896cefacd685705881a3259affee921

Let's remove this since the future is MariaDB

Change-Id: I39641f81c59e7d024aaf48e8e3cc9fc9a7c3127c

Change-Id: I35170712b8f0c83ab35cb5ef7115a6dc434a7a4f

Change-Id: I7e56762a7097dd7369f9d8d71b499888ee5c081d

Somewhat related to 10b4da63 , a similar
doc has negative value inside w:tblCellMar, which MSO seems to ignore
(altering the value has no visible effect), so ignore it as well.

Change-Id: I846e9b55fea0d4e66f03ce615584516360b8b7dd

It appears that this was just a workaround that incidentally worked.
Making the negative value even larger (in abs value) doesn't seem to make
a difference for MSO, but LO fails again. A proper fix (better workaround?)
will follow.

This reverts commit 76aa23c5.

Change-Id: If736316402c49153d4c8552672c90552548f90b8

Change-Id: Icd3b09f098c19268ac888dd6195fb535979557ed

Change-Id: I6e099911afec9c4086f620b45656880135decff0

In neon version, we use xml::crypto::SEInitializer in
NeonSession_CertificationNotify which I see called only once.
For some reason in serf, Serf_ConnectSetup is called every time
we send a command to the server. But that leads to not working
verifySerfCertificateChain in __run_exit_handlers because
xml::crypto::SEInitializer is not available anymore.

Change-Id: I15685256790375dd86eb1b7614da25838d5ce244

Change-Id: I189e7168562db2ca03fd64745eb1f826b6c9adc2

Change-Id: Ib2412d5bd3e3db42b972783bb8d17bc6559c9c21

Change-Id: Ia4a1c7b929dac473dfb5a5fa233c7f0c662a95c6

Change-Id: I12c092fa7034702273182ef07431ed00f38df8ef

Change-Id: If2667e9374917dd1e4c4361378783729761e7dda

Change-Id: Ib17de602e2c51eb29b0495ce7411836ceeccf9d4

The implementation is not perfect but good enough as a start.

Change-Id: I6f006ae7a16ee73de20448e1228d9acfd69becb4

Change-Id: If8549893a686c7a665adde0436d377d6d695e5bf

...mostly done with a rewriting Clang plugin, with just some manual tweaking
necessary to fix poor macro usage.

Change-Id: I71fa20213e86be10de332ece0aa273239df7b61a

Reading the spec, it seems that we have two cases here:

- if lKeyProtDoc is set and fProtEnabled is 1, then editing forms is
  allowed
- if lKeyProtDoc is set, but fProtEnabled is 0, then the document is
  totally read-only

So in the first case avoid the SetModifyPasswordHash() call to allow
form field editing.

Change-Id: Id0c48e8eb4bde75c5520a7b108fcfada51148faf

Change-Id: I725d89c5c36ce898f7340b270a40d875a13a839c

Change-Id: Ia68249242850ef3d82cc56ceae7e5ef84dd08b5b

Change-Id: I98eb64ee6ebad72b534bac8a467a9a334876c2e6
Reviewed-on: https://gerrit.libreoffice.org/8758Tested-by: Chris Sherlock <chris.sherlock79@gmail.com>
Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>

Forgot to commit... oops!

Change-Id: If73bdb2acb3fdba7e155d6f4ed2b6a249829db0e
Reviewed-on: https://gerrit.libreoffice.org/8757Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>
Tested-by: Chris Sherlock <chris.sherlock79@gmail.com>