tdf#153526 writerfilter: catch exception from no NumberingRules
commitbf9e8ce3a810e2989fb0b486b3398d523f69da97
authorJustin Luth <jluth@mail.com>
Wed, 22 Feb 2023 16:19:40 +0000 (22 11:19 -0500)
committerMiklos Vajna <vmiklos@collabora.com>
Thu, 23 Feb 2023 07:35:15 +0000 (23 07:35 +0000)
tree5687e43f37c81e3a509db4ee667a31375889defa
parentc6db0c2bc445a32097cdf48c6e391e1d0d43c917
tdf#153526 writerfilter: catch exception from no NumberingRules

This fixes a LO 7.5 regression (well, exposed some other flaws) from
commit cf02b94bc513ee1b742b4c5d7174632b568e8b72.

I first tried testing if hasPropertyByName,
but that returns true(????), even though this is an editeng component.

Well, ignoring the fundamental issues at play here
(and there are many - like having a comment
take over m_xPreviousParagraph)
the issue is easily solved with a try/catch
instead of a redundant if clause.

Change-Id: I4f27fce3e2984235df19dc3ed4be558891b28a90
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147486
Tested-by: Jenkins
Reviewed-by: Justin Luth <jluth@mail.com>
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147494
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
sw/qa/extras/ooxmlexport/data/tdf153526_commentInNumbering.docx [new file with mode: 0644]
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
writerfilter/source/dmapper/DomainMapper_Impl.cxx