Age | Commit message (Collapse) | Author | Files | Lines |
|
they are largely unnecessary these days, since our OUString infrastructure
gained optimised handling for static char constants.
Change-Id: I07f73484f82d0582252cb4324d4107c998432c37
|
|
Change-Id: I5362d997bfa086c9fb1726efcb15132a966684f6
Reviewed-on: https://gerrit.libreoffice.org/12160
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I3e9a302a7513eebfeff07402f71fc3dde22e4cc2
|
|
Change-Id: I626e3a36426958d7ba1fd320cf8e1a3bf2f3595f
Reviewed-on: https://gerrit.libreoffice.org/11980
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Regression from e8bdd38882522591723097c028ca7a6927ee70c4
(fdo#83751-FILESAVE:Custom Properties dropped while exporting to .pptx,
2014-09-11), there were two problems here:
1) Using the wrong filter when the output is expected to be suitable for
validation.
2) Writing empty custom property values, which is not valid.
Change-Id: Ic18c789c53bd40cc8aa07385cb5fd0d5c7ada6ab
|
|
Change-Id: I0f2821c87c03f8d3df2e60bab9e09ce6545e2b2c
|
|
...in 47c5454ea67632278d69a1ddfe97d74f5cc4449f "fdo#83428: Custom Properties
dropped while exporting to docx," not just ones of UNO type double. At least,
that fixes CppunitTest_sc_subsequent_export_test's
testPivotTableTwoDataFieldsXLSX to not write a "DocSecurity" <property> without
content (and thus fail validation).
Change-Id: I2d764e65ec2af61139c6564f644d27aa9a00bd7d
|
|
Change-Id: I6caec8c11fab5fc8f1318be676e4bdf5f9cdbac5
|
|
Change-Id: I73274d0226999f0f6d8bd681a522ba81d14ebe3e
|
|
Change-Id: Ic289fc446e49fb096cbfad789299736318019e91
Reviewed-on: https://gerrit.libreoffice.org/11265
Reviewed-by: Muthu Subramanian K <muthusuba@gmail.com>
Tested-by: Muthu Subramanian K <muthusuba@gmail.com>
|
|
Change-Id: Idc7f16dc4c81857d7a3f508ed830904d90a762b0
|
|
Change-Id: I5e4dc99c86b696d2c00392fdb47c4d9ebb7f14ff
|
|
Change-Id: I8474b8ec7415b4d8e067343295ea985319c34834
|
|
Otherwise a crash ensues when the threaded XML parsing kicks in.
Change-Id: Ic41e5a29bbb860d7b63b70f2f0d8896264d9d53e
|
|
Change-Id: Ie14ba3dcb97f20479a04538748ef2c1c9e6c5dac
|
|
Change-Id: I8cf274902bb5fda9fa70ab2af9e399db82d85d1d
|
|
This time we did preserve this info, and we should not.
Change-Id: If2ddd7a266cd7da5642dc234411ce34e94bd3384
|
|
Implement a clang plugin to find them, and clean up existing code
to pass them by reference.
Change-Id: If642d87407c73346d9c0164b9fc77c5c3c4354b8
Reviewed-on: https://gerrit.libreoffice.org/9351
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
|
|
Change-Id: Ied05627a0b5fdb8e5fd4a1b071ce32d901f07961
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
writeAppProperties() already uses this data as necessary.
Change-Id: I5eea399ae2cfa37dc3a7c80114f5265fb4a0c648
|
|
Change-Id: Ie98dc14b743983e68f126ed4b7a7f00b637957d3
|
|
Change-Id: Ie2fd4af3340c48c915eada74760cb414848f8a8b
|
|
Change-Id: Ied8283e17ec4379f218dc60912e1c41ca28a8ac9
|
|
Change-Id: I75094f95001dab18436100375a8ec6564e8d0f8f
|
|
Change-Id: I277d76aeec28e173d913ccc1506464afe4d09c6d
|
|
Change-Id: I90b3182e10dbbfc8993010dd885509537d2fe537
|
|
Change-Id: Ie25838f20f00dc32d9d22959308c118cef688e94
Reviewed-on: https://gerrit.libreoffice.org/8288
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
to not let it use an already destroyed RelationsMap instance
(cherry picked from commit 190444f7fd3fa9cfcd1955b3f5dcd916184d02f4)
Conflicts:
oox/source/core/xmlfilterbase.cxx
Change-Id: Ibd09ff9fcba8f919df0704c8e3a64423518b932f
|
|
Change-Id: I939160ae72fecbe3d4a60ce755730bd4c38497fb
Reviewed-on: https://gerrit.libreoffice.org/8182
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Useful when we just need to check if the stream has a certain namespace
defined. Calling getNamespaceURL() may throw SAXException in such case.
Change-Id: Ib2b7b202492390158270d87bab95d1793c9d8a70
|
|
To prevent deadlock during threaded sheet stream parsing. It now
deadlocks at a different place.
Change-Id: I0ba0f2c9a257e71b0a340ab14e369b06d5fd8829
|
|
Change-Id: I576a184ebc8422d760800c670f8d9070f66e9e78
|
|
Change-Id: I2639a51c2faa19373a335c28b160862435cd6dbe
|
|
...so it will be able to use SvtSecurityOptions internally.
Change-Id: Id7433247e8fc53651935578510bedbcca5aa2ac9
|
|
Currently Agile encryption is not supported, so all documents
loaded with "agile" encryption will be encrypted with "standard"
encryption when they are saved afterwards.
Change-Id: Id0477f43c00ed70032ca6b3390eebb1105d5ffa7
|
|
Additionally encryption and decryption has been refactored.
2 engines have been added: AgileEngine and Standard2007Engine,
which contain core functions for encryption and decryption.
Standard2007Engine refers to encryption and decryption as used
in Office 2007 and AgileEngine refers to encryption and decryption
as used in Office 2010 and 2013. AgileEngine does not yet support
encryption.
Change-Id: Ica1d4d5a109fb204012b92a0c39325fe0b99b793
|
|
Compiler plugin to replace with matching number(), boolean() or OUString ctor,
ran it, few manual tweaks, mark as really deprecated.
Change-Id: I4a79bdbcf4c460d21e73b635d2bd3725c22876b2
|
|
Change-Id: I1fcd578955a1f65921c8891916e239bc6f0b9748
|
|
This enables saving of MS 2007 spreadsheet documents with a password.
The encryption used is the same as used in Office 2007 (however
different than in Office 2010 and 2013 which use "agile" encryption).
Change-Id: I3539e811d95b6f9178246ab269d13bb385a48bd2
|
|
Change-Id: I859eaaba3c852127422bd0d0e0db0f9bd62e0d55
|
|
This reverts commit 40aceaae06a354958d6ecf88292bb0fd483f158b.
It's dc:language ...
|
|
Change-Id: I682b35f0793f5fc61daa255bb68a60e164133d97
|
|
Change-Id: Ief663d886b08fc141dfb7563674504fe70f444b3
|
|
FILESAVE, FILEOPEN: ampersand in document title causes corrupt docx when saving; truncates title when loading
|
|
.. and associated methods
Change-Id: Iec01b4615decc1616e405166088d7d1d844ac0ae
|
|
Yes, a simple test would have answered the question in the comment and
made clear that nanoseconds are not accepted by MSO.
Let's go with normal seconds as MSO does. It seems it also accepts
1/100s but who really needs that for a file timestamp.
Change-Id: Iaec6f9c08dc94d5086b83cb4bf520d0053b71b28
|
|
Change-Id: I70f6a46b2195aa28c1a6dcd8c8d7e52fccb22cc3
|
|
- nanosecond precision
- signed (allowed negative) year
Also: assorted improvements / bugfixes in date/time handling code.
Some factorisation of copy/pasted code.
Change-Id: I761a1b0b8731c82f19a0c37acbcf43d3c06d6cd6
|
|
Modules sal, salhelper, cppu, cppuhelper, codemaker (selectively) and odk
have kept them, in order not to break external API (the automatic using declaration
is LO-internal).
Change-Id: I588fc9e0c45b914f824f91c0376980621d730f09
|
|
Change-Id: I8e409ba63d32dca9a1c7f09d143165d1d702d642
|