c4a3b15031
They seem to be designed with multi-dimensional flexibility in mind; it is stored as an array of lists, each having a name and a module. The name may mean a filter. It may have a special name "_user" with unclear meaning. But it only ever used a single item in the array, named "_default", in a single module (swriter). Everything else was only read into a hidden listbox in Compatibility dialog, and never shown nor used. Make ir much simpler. Just use the "_default" item. It is possible to expand it later, if needed; but the previous complexity was bad for maintenance and adding new options. Translatable descriptions of the options were moved from UI file to sw/inc/strings.hrc, and used in a structure that clearly maps them to respective identifiers, to avoid fragile hidden dependency on order of different lists. Change-Id: I78ac5add8a872613e1fb388e4b8cc4fbf4362adf Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162651 Tested-by: Mike Kaganski <mike.kaganski@collabora.com> Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> |
||
---|---|---|
.. | ||
inc/pch | ||
qa | ||
source | ||
util | ||
CppunitTest_unotools_configpaths.mk | ||
CppunitTest_unotools_fontcvt.mk | ||
CppunitTest_unotools_fontdefs.mk | ||
IwyuFilter_unotools.yaml | ||
JunitTest_unotools_complex.mk | ||
Library_utl.mk | ||
Makefile | ||
Module_unotools.mk | ||
PythonTest_unotools_python.mk | ||
README.md |
UNO C++ Helpers
Helpers for C++ use of UNO.