writerfilter: DocProtect_enforcement defaults to false

If enforcement is not specified, then it defaults to off.
"If this attribute is omitted, then document protection settings
shall not be enforced by applications."

Since we cannot guarantee that NS_ooxml::LN_CT_DocProtect_enforcement
will be called, handle checking the various protection statuses after
the import has finished.

The unit test previously had an explicit enforcement="0".
Removing that was the only change I made.

This patch was inspired by a code-review of LO 6.4's tdf#106843 and
preparation for tdf#120852.

Change-Id: I702f5173fd796eb8bda1ea610411f8297d8889b1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/90302
Tested-by: Jenkins
Reviewed-by: Justin Luth <justin_luth@sil.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>

0 files changed, 0 insertions, 0 deletions