Age | Commit message (Collapse) | Author |
|
Change-Id: I5424a148c7173409e6e56f9483fcc769696707bc
|
|
Change-Id: Idf2b6ca6873860a9bb3d2dae646b0383435e58c9
|
|
And store them at appropriate locations.
Change-Id: Iaf38c0cd01e9b3dc9dc98f7ccc1951d572a422e9
|
|
There are still tons of problems to fix.
Change-Id: Icae6e3d2c9b8b2266724d8d068abbab8acae96da
|
|
Change-Id: I6db7b9e86ea6d17b5ba0a883136e0e4dbdd9e0b3
|
|
Change-Id: Ic93c6306cc90a8c7ed77c0aa7d5a898ee911b75f
|
|
The constructor of SvxNumRule initializes aFmts[i] with a format but
always sets aFmtsSet[i] to false, so SvxNumRule::Store()
and SvxNumRule::SvxNumRule(SvStream &rStream) need to be able
to round-trip that combination to prevent spurious numberings.
It is unlikely that this class is serialized in the table auto-format
files but i haven't checked; this change does not change the size of the
serialization so shouldn't cause trouble anyway.
(regression from a95cce27295f9cd255fa72eaded00972e3efb69b)
Change-Id: I589ea108ac069624aaa7b26cdc3bfe8182b15851
|
|
Change-Id: I04c87c5299559932733c88a317808241fd1755d4
|
|
Change-Id: If5c203844d245f370ac6fdb52c779561fb5f165f
|
|
Change-Id: I1a1e38dd36b2144a3e6b96886a56a11a023c47fe
|
|
It fits better this way.
Change-Id: I139de7858e999a6dd26633a548c47634dfad8a65
|
|
Change-Id: I35ac8e9480a7540e049dc251a1470a27f0c2eafd
|
|
Change-Id: Ib5177530b7af15a5574245f53acfecd0ccce4b50
|
|
Change-Id: I3eef26d4ad07a93e044bf8dddddf2d922849435d
|
|
And a new test case to catch it.
Change-Id: Ie51ddf185f70c656e7d838fc7016b5726efbdf3f
|
|
Change-Id: Iaf9295e33e4771f39a085f6ee3cb88ebbf662ff0
|
|
Change-Id: Ie6515c6025c3f199797850cc0941f1efa729cdca
|
|
Change-Id: Ic2c6f574632092073eb30c1a52d43a1524b12aaf
|
|
Change-Id: I71acebdb9c55fdd71d2e611f2ba436f734e949a8
|
|
Change-Id: I1df4bdaa5f13ede9e04972a02948eb072dca2bec
|
|
Change-Id: I7b76026012af2b57861ec8d3dfd285d9e871d74c
|
|
We try and copy the shared one to the user location the first time we create a
customized user file. If the dir doesn't exist then that migration doesn't
happen. The new autocorr file is then written, creating the dir, and any
further operations will reattempt the skipped share copy, and this time succeed
because the dir now exists. Which overwrites the previously written customized
content.
This is similar to fdo#65501 "ensure configured backup dir exists before using
it", so reuse that code and move it into unotools.
Change-Id: I38fa621b8d7295d70b09172a028569ea95404120
|
|
Change-Id: I47d4f60daec82d2b6a4b5e8f20b8cb6484c55057
|
|
Change-Id: Id3486cf7faf0c03f2ce9c72f31d564d5149e5b48
|
|
Change-Id: I431b7ff79cffd5c9a7ff06f41a2fdd56bf2f968c
|
|
Change-Id: I9c906c9ab91f604537769db6820aa820d5f637fd
|
|
drawinglayer has a separate property for the shadow transparency, too.
One more step towards Writer frames have the same UNO API as
drawinglayer shapes.
Change-Id: I84617502e9beb9e077c783ee8eb771d79c6ee666
|
|
Change-Id: If59e9a3956074557842ebc5b178266e9be95a867
|
|
Also adjust SwFrm::PaintShadow(), seems that can't deal with
transparency ATM (always paints white in case of even minimal
transparency).
Change-Id: I88baea732d6ef01b2e516af562bc424775c38f84
|
|
Change-Id: I13682f3886451838e522b259dbb2d686bff1437b
|
|
Change-Id: I2f50ef1dabe2f152f2e18025edc88734158dbea2
|
|
Change-Id: Ibe06bb5c62ac0d8fae17c8a9ffcc4b1bc2768bcc
|
|
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: Id65e819fd1172a28b2cb0bafbd7763313c5fcf50
|
|
Change-Id: I4a996c51e6e7115e90bf15254b26025aae1f9a6c
|
|
Change-Id: Id04dffc135fad6bb66ea157cd280dd481cb80117
|
|
Change-Id: I41b73e0af6841247a0403974b1c66e5a66123420
Reviewed-on: https://gerrit.libreoffice.org/5483
Reviewed-by: Matteo Casalin <matteo.casalin@yahoo.com>
Tested-by: Matteo Casalin <matteo.casalin@yahoo.com>
|
|
Change-Id: I8d65f43b95944583b50874adb90db38eee7623de
|
|
Change-Id: I20adfc9148b8afa7a59245349f233604bd9a1d2e
|
|
Change-Id: I4d6196a9a96ad1dd236f8622a523b4702e92d76f
|
|
Change-Id: I9ccb06134dfadd9bf1ecb8e5edcd24c02980b754
|
|
Change-Id: I178f9eb702afb6143c583d5fd54003a427d895fa
|
|
Thanks to dougmencken for noticing.
Change-Id: If9b18b7686981b523e8422cecef0930fded10c91
|
|
Using a literal string that includes non-ASCII character(s) to initialise an
OUString causes a warning "sal/rtl/strtmpl.cxx:1338:
rtl_uString_newFromLiteral - Found char > 127".
I doubt the '\xFF' in the aWordDelimiters initialiser makes sense. The
initialiser contained "\0xFF" since the beginning of time, which (as said in
e7a958441a19a4e14bf12aac09fa566de0f263ee) means a zero byte '\0' followed by
"xFF".
So '\xFF' was not included in the initialiser during all that time
either. Whatever the '\xFF' means in the set of "word delimiters", quite
possibly it is handled explicitly in the code anyway (grep for
CH_FEATURE_OLD).
Change-Id: I2998a13e6e573f85c92e66ff6edbb6354ba11b5b
|
|
Change-Id: Idf191ab3dfa7f6fde190c55d4d1d228a49ecf771
|
|
Change-Id: I9d93d6aa26b2c9d20f7be8d201051a51e8e4ce7a
|
|
Change-Id: Ib574cc7130f49c7a6be23566377313906c52abb8
|
|
Change-Id: I04c7da143425a9d8cc4fae155ad45a469df953c1
|
|
d08a76cf72e1d1db9add8b01f4e93c4b4ba4dd15 revealed that "\0xFF" was
always inserted as a delimator but presumably the intent was a single
delimator of "\xFF" and not four delimators of '\0', 'x', 'F', 'F'
Change-Id: I6b34c1bcd90086fd5d6fe7043fa98ef89bcb8553
|
|
Change-Id: I49e0e589c4bad3706882c9e30fe4f6bf8bdd7f1d
|