* added com::sun:⭐:table::TableBorder2 with
com::sun:⭐:table::BorderLine2 members
* added optional com::sun:⭐:table::BorderLine2 properties to
com::sun:⭐:table::CellProperties service
* changes in Calc
* support TableBorder2, additionally to TableBorder
* reverted change that made all BorderLine properties operate with
BorderLine2 structs
* instead support both, BorderLine and BorderLine2
The update check protocol uses the webdav ucp, which uses neon,
which in turn defaults to keeping the connection alive. this is nice
for webdav, but disastrous for millions of clients phoning home to
the same server.
Using neon directly in updatefeed.cxx is not an option, due to the
thread safety problems around that (see e.g. rhbz#544619) - so we
had to extend it to accept connection options, and reuse the
existing webdav provider.
Doing it this way avoids having to re-generate the data ranges in
Calc A1 before passing it to the chart backend in Calc. We need this
in order to remove the silly restriction that forces us to always pass
data range strings in Calc A1 format, which is error-prone.
This is also necessary in order to fix the bug that prevents editing
data ranges of an existing chart when the formula syntax is something
other than Calc A1.
* New offapi com.sun.star.configuration entities to access the complete
configuration read-only or read/write...
* ...configmgr adapted to support those new services/singletons...
* ...new unotools/configuration.hxx is the type-safe C++ plumbing on top of
that...
* ...officecfg now generates C++ headers to access all the properties and sets
given in the .xcs files...
* ...and svl's asiancfg.cxx exemplarily makes use of the new
officecfg/Office/Common.hxx to access the configuration.
* There is still TODOs: For one, see those listed in
officecfg/registry/cppheader.xsl. For another, at least a notification
mechanism for the new read-only configuration access and the C++ wrapper is
missing.
* Locale data:
* nominative (nouns) month names always given in <MonthsOfYear>
element
* optional genitive case month names in <GenitiveMonths> element,
following the <MonthsOfYear> element; if not given take nominative
names
* optional partitive case month names in <PartitiveMonths> element,
following the <GenitiveMonths> element, or following the
<MonthsOfYear> element if the <GenitiveMonths> element is not
present; if not given take genitive case names, or nominative if
genitive names aren't defined
* currently known partitive case matters in Finnish locales
* Rules for use of nominative / genitive / partitive case month names in
number formatter:
* no day of month (D or DD) present in format code => MMM or MMMM
display nominative month name (noun)
* day of month (D or DD) after MMM or MMMM => genitive name
* no genitive names defined => nominative names
* day of month (D or DD) before MMM or MMMM => partitive name
* no partitive names defined => genitive names
* no genitive names defined => nominative names
This updates the keys for the following intentional changes:
ENUM: /UCR/com/sun/star/drawing/TextFitToSizeType
Field 3: Name1 = RESIZEATTR != Name2 = AUTOFIT
SERVICE: /UCR/com/sun/star/sheet/SpreadsheetViewSettings
SERVICE1 contains 1 more properties as SERVICE2
incompatible change: Field 14 ('SolidHandles') of r1 is not longer a property of this SERVICE in r2
SERVICE: /UCR/com/sun/star/text/ViewSettings
SERVICE1 contains 1 more properties as SERVICE2
incompatible change: Field 24 ('SolidMarkHandles') of r1 is not longer a property of this SERVICE in r2
