Age | Commit message (Collapse) | Author | Files | Lines |
|
Consolidated changes for fdo#56278 fdo#54074 fdo#53364 fdo#55059 (and
earlier i#99844 and i#101869). The replacement cell for the broadcaster
to inform listeners, if any, is transferred the broadcaster and owns it,
the remembered formula cell never does. When broadcasting the change use
the replacement cell instead of the remembered formula cell. Don't
fiddle around with ReleaseBroadcaster() at the remembered cell, we don't
delete twice and now also don't leak.
(cherry picked from commit 8165bfa2afbe828caf37df57b83cb31bef2559cb)
Change-Id: Ia11b6d3d751c784af64aaed05f8508887f869a80
Reviewed-on: https://gerrit.libreoffice.org/1069
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
|
|
Accept fraction input without integer portion if the format was preset
as fraction, e.g. 1/5 instead of 0 1/5 and don't force to date.
(cherry picked from commit 5391bd1e54157457abe1098b29f067d6e0059113)
Change-Id: I326ec85b163962425efa074119405ec1395af481
Reviewed-on: https://gerrit.libreoffice.org/1045
Reviewed-by: Petr Mladek <pmladek@suse.cz>
Tested-by: Petr Mladek <pmladek@suse.cz>
|
|
In general, DOCX tables provide a grid for the table, then use spans in
case different number of cells are used in different rows. In this case,
the cell width is ignored, as the wished width can be counted from the
grid and span values.
However, it's also valid to simply provide more cells then the amount
defined by the grid, and in this case the cell width should decide the
final width of the cells. This commit adds support for this later case.
(cherry picked from commit ad913681c0e0cdaaa706329f518f59ee54b86d43)
Conflicts:
writerfilter/source/dmapper/DomainMapperTableManager.cxx
Change-Id: I0dd6c1f0c06f81c2afa00489b7ad1f33ff300a7c
|
|
Change-Id: I93d623b62e9357a71bfca3403cc98092ef58c7e4
|
|
Any rotated text in an emf image (image size != original size),
has thicker fonts.
This is kind of a regression caused by commit
8c2902ecbf135fae070ea032fa10a59bb76ec1b0
So, partially reverted it.
The code was kind of a workaround/copy-paste, so I am assuming
it is safe to revert.
Side-effects: The dotted borders (in calc) look a
little lighter and not so very visible in the page-preview.
|
|
Change-Id: I26837290d1416637032d2dfcfa45b4003c874309
|
|
(cherry picked from commit eac3e6e746300df379226941ba75c4e0ce1feb7a)
Conflicts:
sw/source/filter/ww8/docxattributeoutput.cxx
Change-Id: If204523d7da544b11b2d809993ada180476104ef
|
|
I suppose it is the same misconception as in fdo#55931 - I am convinced that
the font metrics should not be used here.
Looks to me as if in the past, the font width computation was broken somewhere
deep inside OOo, and everyone instead of fixing the root cause was just
working that around by using the FontMetric; and then one day the root cause
was fixed, and all the workarounds broke ;-) - but that is just a theory.
Change-Id: I741bf8f4eaea4f7d8bc698dc9a8124109dfb8c20
|
|
The "faux bold" make the bold font in Asian ugly & unacceptable,
Adjust & improve the "faux bold" to make the bold font better.
Change-Id: I2e02156ffc30629476b80134ffb0b50e793f7ead
Signed-off-by: Jan Holesovsky <kendy@suse.cz>
|
|
Change-Id: Ia55ff9b54202dad6c0df46a69235543d88f43e61
|
|
Change-Id: I1ec9b5d9fed86c44dc0a412c2323033ea67985c9
|
|
The build is based in the upstream 3.6.3 and will be called SUSE 3.6-rc2
Change-Id: I04337c2d4001eec123cfb1fe1043b4955a5bba2d
|
|
For some reason that escapes me now, the old code double-expanded URLs in
CONFIGURATION_LAYERS and in extension layer's configmgr.ini SCHEMA/DATA. That
produced wrong results when the pathnames represented by those URLs contain
any "$" characters, as apparently routinely happens on Windows with roaming
profiles.
Change-Id: Iff149e7d8736cbcda579376cdc89e24cf99ccc97
(cherry picked from commit 8246bdb500a6d83ea9b61f58fb74e051432e32d7)
Reviewed-on: https://gerrit.libreoffice.org/994
Reviewed-by: Michael Meeks <michael.meeks@suse.com>
Tested-by: Michael Meeks <michael.meeks@suse.com>
|
|
Change-Id: I56653d99e1fac5e1b7cd2a69b4b160df4b75bb5d
(cherry picked from commit a7d38322d6211863024456602da1dff23a8316dd)
Signed-off-by: Caolán McNamara <caolanm@redhat.com>
|
|
See commit 66fa759b for rationale, this fix just does the same for JPEG
files as well.
(cherry picked from commit ebc61e11cdb02f5cc33aeabead3d191eaf0d23d3)
Conflicts:
sw/qa/extras/rtfimport/rtfimport.cxx
Change-Id: I6a9ead5f4b4b9c4661cae99501bd7c14a2a79409
Reviewed-on: https://gerrit.libreoffice.org/991
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
We used to send nothing when we got nothing, but this is not correct:
\pvmrg and \phmrg is the default in RTF, but not in Writer.
(cherry picked from commit 7b7bee4ed5722ce59ffd3394a0330d71d69d66b3)
Conflicts:
sw/qa/extras/rtfimport/rtfimport.cxx
Change-Id: I9f69e282e68f0828c8b5ba98657cad1dd0715eb3
Reviewed-on: https://gerrit.libreoffice.org/993
Tested-by: Caolán McNamara <caolanm@redhat.com>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|
|
Pushed in master as c954e6e1317f82e06fac66556674bc066b429469
Change-Id: I98f246b2bafcf2669a8f6c3ec4c86ccee56519bf
Reviewed-on: https://gerrit.libreoffice.org/984
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
Reviewed-on: https://gerrit.libreoffice.org/985
Tested-by: Miklos Vajna <vmiklos@suse.cz>
Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
|
|
Change-Id: I4b94883f594e13e9923bdd05593447a152fa8b0a
Signed-off-by: Kohei Yoshida <kohei.yoshida@gmail.com>
|
|
Change-Id: I2ab31904169adad4f173d4655d0511855de77464
Signed-off-by: Kohei Yoshida <kohei.yoshida@gmail.com>
|
|
And Calc's header footer currently don't distinguish between time and
extended time. Time fields in the header / footer are always dynamic
and never static.
Change-Id: If628d179968c270a63d38cdc3bf6018c01241ac1
Reviewed-on: https://gerrit.libreoffice.org/992
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Change-Id: I2d53c88ab121edeec2bf53f7fd177a0edcc05a25
Reviewed-on: https://gerrit.libreoffice.org/958
Reviewed-by: Kohei Yoshida <kohei.yoshida@gmail.com>
Tested-by: Kohei Yoshida <kohei.yoshida@gmail.com>
|
|
Change-Id: I1e31fe05e00ed7e298642da9c0e35ae834dfa74f
Signed-off-by: Kohei Yoshida <kohei.yoshida@gmail.com>
|
|
Change-Id: If9859b5021c532daacccfaf386e0489c134e4afb
Signed-off-by: Kohei Yoshida <kohei.yoshida@gmail.com>
|
|
it was mistake created by porting mono stuff for LO-3.6
Change-Id: I498f7cb7f6317dabd94798dc94db57adf304e5f1
|
|
Change-Id: Ieee849e3e3b8bda5674027af9c6c2993b045d71a
|
|
Change-Id: I9c717b067e067338160a38c88d935187db8cc04d
|
|
Currently, having a note e.g. at D5, and deleting cell D4 and shifting
the cells below upward will remove the note at D5. But the correct behavior
is to shift that note up to D4. This change fixes it.
Change-Id: Ia37f1ce67a003deab424f2b805a2ce333fc10ed4
(cherry picked from commit d3344dd85ee31b195a3709d16e734245e1d0a4b6)
Signed-off-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Steps to reproduce:
1) Insert a comment at D5.
2) Move cursor to C4.
3) Right-click and select Insert.
4) Choose shift cells down.
5) The comment gets shifted down but it shouldn't.
The same thing happens when deleting a cell and shifting content.
Change-Id: I5a71845cca6abde6b7c940e152e155da26343cef
Signed-off-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Change-Id: I80fd050e1bbdc0386c13e0afbeeb404e14b2694b
Reviewed-on: https://gerrit.libreoffice.org/849
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
Reviewed-on: https://gerrit.libreoffice.org/855
|
|
Change-Id: I347672a2175cf7a0304cf5d6c0f8f3f6afa92cd4
(cherry picked from commit 8bd3bf0ff20fc18a0a6358e36b3f8a7e3b34a2bb)
Reviewed-on: https://gerrit.libreoffice.org/919
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
This reverts commit dd6c4f4db1d62268d73e09ae52d23f760a967dcc "fdo#46102: Load
Java scripts with class loaders that actually find them." That commit broke
support for macros embedded in documents (as
new java.net.URL("vnd.sun.star.tdoc:...") throws a MalformedURLExcetpion), and
it looks like that commit was not necessary after all -- or rather that what it
tried to work around must have been some other problem that has been fixed
meanwhile. "It is unclear to me how the Java script provider shall ever have
found the script jars in the past" indicates that something must have been
fishy, and what I failed to notice back then is that createURL creates
java.net.URL instances with a UCBStreamHandler that does allow to obtain content
from weird-looking URLs.
Anyway, with that reverted, all three following scenarios work on both current
master (towards LO 3.7) and libreoffice-3-6 (towards LO 3.6.4); I haven't yet
come around to test on libreoffice-3-5:
1 Stock macros, "Tools - Macros - Run Macro... - LibreOffice Macros -
HelloWorld", running all of the four "helloworld.bsh", "helloworld.js",
"HelloWorldPyhton", and
"org.libreoffice.example.java_scripts.HelloWorld.printHW".
2 Per-document macros, loading test.odt attached to fdo#49517, then "Tools -
Macros - Run Macro... - test.odt - HelloWorld", running
"org.libreoffice.example.java_scripts.HelloWorld.printHW".
3 Extension macros, installing ScriptDispatch.oxt attached to fdo#46012 as
shared extension, then loading StartScriptDispatch.odt attached to fdo#46012 and
pressing the "Start Java via ScriptProvider" button.
Change-Id: I31cd16b3720ffeb1058722d4d1fdffb773f8a067
(cherry picked from commit 7ea7fb009ddcfb0723e88ba0c5778b5fdbe2b553)
Reviewed-on: https://gerrit.libreoffice.org/922
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Due to an insane amount of ridiculous "user-defined" number formats the
internal table may overflow during import, stave off and increase the
number of available slots to another arbitrary limit.
(cherry picked from commit 075e9ca0b96f37b3561824c23af60872d6a9d80a)
Conflicts:
svl/inc/svl/zforlist.hxx
Change-Id: I2fb85c83a65d6c5b3183aeb3a3bda88828473a3c
Reviewed-on: https://gerrit.libreoffice.org/951
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
nStopPos is non-inclusive, and STL's erase() method also expects a
non-inclusive end position (like any other STL methods do). It's wrong
to -1 here which would end up not erasing the last element containing
a pointer to the deleted cell instance.
Change-Id: Ic09ab4a6bb03d0f56bb854a91bf93a99be867116
|
|
so duden extension doesn't blow us up
Change-Id: Ie6b26670a6809fc07b344660111be44cb3e6a011
Reviewed-on: https://gerrit.libreoffice.org/939
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
|
Change-Id: I1f98a6a1e5ede6fcd9a3570788969edcb251384b
(cherry picked from commit 63f00d37a20169743d9709977b382c379560ef9e)
Reviewed-on: https://gerrit.libreoffice.org/918
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>
|
|
regression from f6a34255af1339cd7132b7527dc0c10c10d38249
Change-Id: Iabfaf92629cd4d53ab7af5f3e3013eb81bb8104d
(cherry picked from commit 2536fae7b8565b5dd9f09bb3dc015576fafe4031)
Signed-off-by: Michael Stahl <mstahl@redhat.com>
|
|
Its a nice idea to merge properties of the same type and value if one starts
and the same place the last one ended. But character styles are properties as
well, so if we have character-style+superscript on range a, and
character-style+superscript on range b and merge these so that we end up as...
character-style on range a, superscript on range a+b, and character-style on
range b then that clearly gives the wrong result if applied in that order.
So its only safe to merge if there are no intermediate properties that can
affect the merge candidates.
A regression from b3cee382f449aa69213dc21f7b1ba6a5356d2865
Change-Id: I541563d11265426736b840de068922eef8d45573
(cherry picked from commit 08ffb7bc5ec4472126762f4cb9677349b61122f6)
Signed-off-by: Michael Stahl <mstahl@redhat.com>
|
|
Conflicts:
configure.ac
Change-Id: I655e8e15c7f7a8c292b3a1820ee48c29e847d05a
Signed-off-by: Tomas Chvatal <tchvatal@suse.cz>
Signed-off-by: Luboš Luňák <l.lunak@suse.cz>
|
|
Change-Id: I6caa48a428ac7fef23f7c3e6fc7896b7e3a8d0fc
Signed-off-by: Luboš Luňák <l.lunak@suse.cz>
|
|
The image was special in that the resulting Graphic's
GetPrefMapMode().GetMapUnit() wasn't MAP_PIXEL.
(cherry picked from commit 5ef0f1dc9a70c20fe6879832b782a0c34724353f)
Conflicts:
writerfilter/source/rtftok/rtfdocumentimpl.cxx
Change-Id: I681e344a042721b99f6cb2e599f9c65156d219a4
Reviewed-on: https://gerrit.libreoffice.org/860
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>
|
|
Regression from d4069372484f18b242a42a1996767f57b031fff6.
Conflicts:
sw/qa/extras/rtfexport/rtfexport.cxx
Change-Id: I58e8d48ac3222b795f7edfd0e74ecd86ea36f380
Reviewed-on: https://gerrit.libreoffice.org/913
Tested-by: Caolán McNamara <caolanm@redhat.com>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I43b0065e56b234a5aa748ac1593c29a44fdb1647
Reviewed-on: https://gerrit.libreoffice.org/886
Reviewed-by: Petr Mladek <pmladek@suse.cz>
Tested-by: Petr Mladek <pmladek@suse.cz>
|
|
Through that different initialization pIUnknown
got random address. The consequence was that
if (pIUnknown)
pIUnknown->Release();
ends with access viloation in
WpBase& WpBase::operator=(const WpBase& rhs)
Change-Id: I8b3c5de233d0868fea052c990cc83aed917117ae
(cherry picked from commit ac2cfed553b8c9303f86758e9fe8b70911db00cd)
Signed-off-by: Michael Stahl <mstahl@redhat.com>
|
|
Else you'll get the wrong answer in isRowActive(), which always search
flag via tree.
Change-Id: I3fa92d06f7ba3040eca061d5424afefe362703de
Signed-off-by: David Tardon <dtardon@redhat.com>
|
|
Especially since the rest of the function is prepared to handle
no/empty (Catalog|Schema|Table)Name.
Change-Id: Ic0bb59ead5789e671c90887ef850588f4924f5e7
Reviewed-on: https://gerrit.libreoffice.org/968
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Regression from commit 1fdd61db155cf63d5dd55cc2bfb45af33796e131,
continuous section break does make sense at the end of the doc, if the
previous type was a non-continuous.
(cherry picked from commit abd4ffadf30e02284290ea35e8f45d9ffd8eb5ee)
Change-Id: I6d82c67e068d8dc3ce1edb1a5fe6ad293afd805d
Reviewed-on: https://gerrit.libreoffice.org/877
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>
|
|
\n\nAll of the code for the constant defining greek upper case page numbering is correct, but the UI dialog that represents that constant displayed lower case greek letters, and vice versa. So, the dialog should display the proper characters.
Change-Id: Ib8d0a41928796fbed5f36162c35d6e1db2463e07
Reviewed-on: https://gerrit.libreoffice.org/904
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
(cherry picked from commit e89c99a8ce264173a9d9cbb6df09d7811d6b34cc)
Signed-off-by: Eike Rathke <erack@redhat.com>
|
|
Change-Id: Id2e8ad5b6bed1c184de6dccf7fa43254099fb958
Reviewed-on: https://gerrit.libreoffice.org/923
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
we're currently deferring to the end of the text node to export
the contents of frames. If its anchored as character then the
sw::Frame (which is allocated on stack) has gone out of scope
so this pointer points to junk. Copy it instead.
Sill need to export frames property at some stage.
Change-Id: Ib9f8c6857ce1afe6acba84986b692139e44a7aad
(cherry picked from commit 60a93729c95d31edab50a905236faa9e38a81556)
Signed-off-by: Eike Rathke <erack@redhat.com>
|
|
Change-Id: I56d5a716795b7303a77194964a612c550f25eeec
|