Since there are now 2 forks of OpenOffice.org, we cannot rely on a
simple total ordering of versions any more; add a new function
SvXMLImport::isGeneratorVersionOlderThan(), taking 2 reference versions.
Also extract the LibreOffice version number from the generator string,
and extend the BuildId property to store this as a third number.
This also allows removal of the "fake LibreOffice3 as OpenOffice.org
3.3 release" hack, which is not future-proof.
Change-Id: I44d8105eb537ac43fb9529a8b1b661ae0f2bba30
SvXMLMetaDocumentContext::setBuildId: check only the prefix of the
generator string, not all of it.
(regression from 17ff7b41d1)
Change-Id: I0cdd958d67cd13fd2368cc6958893ce3528a9e94
I actually find the warning to be obsolete nonsense (the manpage talks
about cfront), but at least for now.
Change-Id: I4390b1779f6f8de062afd441f6855cb760adf93d
Without populating the clip document, copying a chart (or charts) into
clipboard makes the charts lose all their referenced data, which causes
the pasted chart to appear empty.
Change-Id: I3675f76baed19b48cec403964c19df00725a044b
Else, if the n^{th} (with n>2) table also appears in a (non-NATURAL) INNER JOIN, it is repeated later, leading to an error from the database engine
Change-Id: I03e0f0ef51f45be9d7ddfa63a9dbe09dc500f8dd
API CHANGE: Adds new methods (several overloads)
OString::number()
OUString::number()
and marks all of the existing fromValue() methods as deprecated.
The purpose of this change is to clean up call sites
by hiding the necessary casts.
The casts are necessary because of overload resolution rules which are
somewhat vague about which methods to choose when using integer types.
See mailing list discussion here:
http://nabble.documentfoundation.org/replacing-OUString-valueOf-static-cast-lt-sal-Int32-gt-td4027989.html
Subject: "replacing OUString::valueOf(static_cast<sal_Int32>) ??"
Change-Id: Id3d150a6525eb0334e41e2ec6640bb06cd790b43
Reviewed-on: https://gerrit.libreoffice.org/1625
Reviewed-by: Luboš Luňák <l.lunak@suse.cz>
Tested-by: Luboš Luňák <l.lunak@suse.cz>
...to make it easier in the future to replace the binary rdb format with
something else, but also keep support for the old format for backwards
compatibility (extensions).
This should have no performance impact, as the type description manager (a)
caches information about requested type descriptions, and (b) has been changed
to process the bootstrap rdbs en bloc without doing costly consistency checks
(which are useful though when inserting an rdb when installing an extension, but
which would exhaustively read all type descriptions from the inserted rdb, so
would negate any benefit of constructing any type descriptions on demand only).
Change-Id: I80b22770bd9a5e0ab686f04d9c70295f2e3d0bf6
I don't know what's wrong with it or why the problem shows only for
me on openSUSE12.2, but it's been broken for several days now
and there's not much point in keeping it that way given that it
didn't work from the beginning.
Change-Id: I608bc01e4ee914629db1aa75ce8463044fe20ca6
This adds glyphs for prime (U+2032), double prime (U+2033)
and triple prime (U+2034).
Change-Id: I73297209f0410db607c1ae4787ba15c3ac08133f
Reviewed-on: https://gerrit.libreoffice.org/1679
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
Having it explicitly disabled was already handled, but apparently
01d059c13e turned on shadows by default.
Fix this.
Change-Id: I1401a28b36a9b5aea302f9a19a6d02a29e6b358d
I've being putting this one off for a while as its a complicated
set of hidden pieces shows for different background types
format->frame->background shows transparency option
table->properties->background shows "for cell/table/row" options
flipping as graphic/color should show different contents
Change-Id: I4a63d3bbe8898ad2421d6ddef011da9ae67b5a4f
If all paragraph margins are 100% on import, ignore that as being the implicit
default. That avoids explicit 100% being set onto the awesome [UL|LR]Space
which takes a relative propsize of 100% as a flag that its value field is
absolute and so rejected by SwTxtFmtColl::Modify as a candidate for getting its
true value initialized relative to its parent, so it ends up as an absolute 0
Always elide the property on export because writing individual
margin-foos provides better backward compatibility with older versions
anyway.
Trigged by 3c5facfce4
Change-Id: I55f6ceeae287b7d8e99befa4bd3cc06738a21299
These 2 lines (from initial CVS import) appear unnecessary since the
only valid SvxPageUsage value with 0x04 set is 0x07.
Change-Id: I4fe92e100955ff00831e0ef7bdad21e7105193ed
There is at least one call in SwDoc::ChgPageDesc() checks if the result
equals PD_MIRROR.
(regression from fa0f42bafb)
Change-Id: Id37ca46eec5885f7f5230337d8a8a594845f7842
This also removes an English text in the Master page: "Click here to edit..." and replaces it with a placeholder
It would be nice to have this in 4.0 branch also.
Change-Id: I1aadc20aa9916e40bbaf1b6f66ec58dfd02a35bb
Reviewed-on: https://gerrit.libreoffice.org/1725
Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>
So far I am using the same color that is used for the workspace; should it be
a problem, we can use a different color.
Change-Id: I06fde7f31a9d37d2e387a7e3fd0b6d3d33f8d6e6
