...as f6281ec4 "#i110273# caption order changed
for locale hu" added a special value for xml:lang="hu", but failed to take into
account that the property is not localized.

Until now, every installation that had the hu localization installed (but
regardless of whether or not it was actually using it) would always have
reported the special hu value (true), while any other installation would always
have reported the default value (nil, mapped to false in the else branch at the
end of SwInsertConfig::Load, sw/source/uibase/config/modcfg.cxx).

Unless the value was overwritten in registrymodifications.xcu (by changing the
Options dialog "LibreOffice Writer - AutoCaption - Caption Order" setting).  In
which case the hu localization will now start to use its default again (true),
while all other localizations will continue to use whatever value had been
stored (without an xml:lang attribute) in registrymodifications.xcu.  This is a
bit unfortunate for the hu-localization case.  It should probably be mentioned
in the release notes.

(Strictly speaking, changing a property from non-localized to localized, as is
done here as well as in e.g. ffd8369b
"rhbz#1541486: Fix localized'ness of ooSetupFactoryUIName props" is an
incompatible change which 3rd-party code can observe through the
css.configuration UNO API.  But chances are extremely low that this will have
any impact, as access to any property's value is normally done in a way that
makes it transparent whether or not the property is localizied.)

Change-Id: Ia840e28e10d0fa388bff6eaf8aadf0e8e6b25a19
Reviewed-on: https://gerrit.libreoffice.org/49414Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>