Age | Commit message (Collapse) | Author |
|
Change-Id: Ia51394a701a06b6d6bc2cf6e9628cca9ce274821
|
|
Change-Id: I24e1bab96e9890bbe32a7e2f3edf8ed1ec15ef92
|
|
Change-Id: Ib61897ff2f5b459f5f6c75726be22ed99d383ec3
|
|
Change-Id: I78dc0afed58ad7dc51c64cac8c89abcda601f8b5
|
|
Change-Id: I43816cbb345fa141f845da208a06ed9eb9a5303a
|
|
The attribute is only exported for ODF versions > 1.2; use the new
loext (LO_EXT) namespace.
Change-Id: Ie44e4b851c4adf52d8cc4fc2cbe37d6c3a9941d8
Reviewed-on: https://gerrit.libreoffice.org/4830
Reviewed-by: Thorsten Behrens <tbehrens@suse.com>
Tested-by: Thorsten Behrens <tbehrens@suse.com>
|
|
XML_NAMESPACE_LO_EXT can be used for elements and attributes that are
not yet specified by OpenDocument.
Change-Id: Id29392533d46f6592d964ce79c05ffefa4d69ebc
Reviewed-on: https://gerrit.libreoffice.org/5419
Tested-by: Thorsten Behrens <tbehrens@suse.com>
Reviewed-by: Thorsten Behrens <tbehrens@suse.com>
|
|
Change-Id: I387ef3c2c8345bb5be75909596f59af80b966443
|
|
that overflow their signed counterpart type
Change-Id: I7d446a5fdddb9d5ef313c1bd022fd959b11dec28
|
|
Change-Id: I5df60d69431c67e3b8a2d76677d82e8eb1bd398a
|
|
Change-Id: If31845aa575b3f9459507deefb1b469ac3715e35
|
|
Change-Id: I09453c73303076318b7105a778ff98695b0a3839
|
|
In Word, just like normal tables, floating tables should be positioned
in a way that the start of the cell text has the same horizontal
position as normal paragraph text.
To emulate this, first the table should be moved left by the table
border distance, then also by the border with / 2; as done for
non-floating tables already.
Change-Id: I581311fbb08009e6c1839106e8f615d078a4a705
|
|
m_nMaxFixedWidth wasn't reset across tables, so the counted width for
the first table in the bugdoc affected the second as well.
Regression from 74c5ed19f430327988194cdcd6bdff09591a93fa.
Change-Id: I69a5fa402f2e0170a1ea0269fd73e4ad8f7fede1
|
|
Project: help eb245191261167b8de5ec3c941402240e4dab133
|
|
Change-Id: I0f473ebfc7bd6a8bd5aa1b8749fc3afa7a51bb70
|
|
Change-Id: I9ccb06134dfadd9bf1ecb8e5edcd24c02980b754
|
|
fdo#60805"
This reverts commit 46d122d4cc405c4070eb4945abd20cdf3a5fac33.
Unfortunately this re-introduces the previous problem of the cell borders
drawn too thick when anti-aliasing is enabled. Also, even with this reverted
the problem will still persist if the user manually disables anti-aliasing
in the Options dialog. So, we *do* need to find a way to draw the
double-borders etc correctly without anti-aliasing.
|
|
Change-Id: I06a8158b7f503976b19383014a7c8a867c0184ea
|
|
Unfortunately this patch creates a very weird ( and took me forever to find
) bug ( fdo#60805 ). Basically certain double line borders seems to
dissappear at certain zoom levels. I guess maybe its possible to tweak
the create2DDecomposition to process the line as hairline at those problematic
zoom levels ( but I suspect that actually would look worse ) Best maybe
would be to tweak the rendering/painting ( but isn't that processor specific
maybe ? ) as is maybe this problem. I admit this is outside my comfort zone :/
This reverts commit a551cad4e35b6b664167d65dfc25e5a0f6990687.
Change-Id: Idb25493ffb038cb1f8ae9b364a29052abafd940d
|
|
Change-Id: Ia3c452f21328e2d5773f245e729905a70d14c29e
Reviewed-on: https://gerrit.libreoffice.org/5312
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
Otherwise global w:spacing will be used even if overriden locally.
Change-Id: I01f0a3a323566f6e29faf73bf9d2ba874565eb42
|
|
Change-Id: I821a51c65e4596516081e5f4b96283616056b60d
|
|
...since gb_LinkTarget_NOEXCEPTIONFLAGS became unused with
e81b1f23c49e35c1cde1faa44281812e97be60f5 "remove
gb_LinkTarget_add_noexception_object."
Change-Id: I4a7275b5b26a9d4b6ded66efb52e6866e6e09cc3
|
|
Change-Id: I2b3eb7a8e3d47b646eb8d4a8ca396a7c9de9545f
|
|
In other words, SAL_DEBUG(any) works now. Structured any types
(e.g. struct, array) not implemented yet.
Change-Id: I6460e72bbeff86da17711cab5d2018508468290c
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Avoid a (presumably bogus) warning produced by gcc 4.7 and 4.8, at least those
in the Android NDK, in an optimising compilation. As such the code probably
was OK, even if a bit ugly and suboptimal, as it doesn't seem to be sure
whether various buffer lengths should be hardcoded or can be variable, etc.
Change-Id: I29790cb7a9cb65735e4ebb9a1a198f8575282ecf
|
|
Change-Id: I1bb65ee0ff3059ee47f83d54814f3a228994d960
|
|
(list see in task itself) and a regression/crash
Patch by: regina
Review by: ALG
(cherry picked from commit 8a9164f5f853db66b4453fc6fb798acf0a88a238)
Conflicts:
svgio/source/svgreader/svgsvgnode.cxx
Change-Id: I1c29073a3a18d2e645378e64a9fb28e73fc7e9ab
|
|
Change-Id: I0216d11ade872af889fc805e4c2a9241f7f230c5
|
|
Change-Id: I4cc2d199ed94444a056134359cbe2674a2885555
|
|
do not use them where not needed
(cherry picked from commit 4ccb1eb7d58005ab3b501b7c6ff128fadbcd5066)
Conflicts:
basegfx/inc/basegfx/matrix/b2dhommatrixtools.hxx
basegfx/inc/basegfx/polygon/b2dpolygontools.hxx
basegfx/inc/basegfx/polygon/b2dpolypolygontools.hxx
basegfx/inc/basegfx/tuple/b2dtuple.hxx
basegfx/inc/basegfx/tuple/b3dtuple.hxx
sc/source/ui/inc/output.hxx
sc/source/ui/view/gridwin.cxx
sc/source/ui/view/output.cxx
vcl/win/source/gdi/salgdi.cxx
Change-Id: Ie265814a51180bffe3c821a3f2148cb3bb54ecad
|
|
Project: help 981ce916ffcb9ef4a0707d0e10905e55059fb635
|
|
Not sure if it solves a real problem, but seems sensible.
Change-Id: I3a75da924aaffb452da158a6e5c0b3465fe5687b
|
|
Change-Id: I77726f009338ae49877c5f58fe6c14d386089bbe
|
|
Change-Id: Ibeed303ca4b8812cf7deafa1d1ad06f59a73cf8d
|
|
ICE101 ERROR The feature gm_o_Extensions_Script_Provider_For_Javascript
is greater than 38 characters in length.
Features are limited to 38 characters and must follow this convention
for APIs like MsiEnumFeatures
ICE101 ERROR The feature gm_o_Extensions_Script_Provider_For_Beanshell
is greater than 38 characters in length.
Features are limited to 38 characters and must follow this convention
for APIs like MsiEnumFeatures
Change-Id: I298a0dafa7babd1af69c7754fe89efcfe5902970
Reviewed-on: https://gerrit.libreoffice.org/5401
Reviewed-by: Fridrich Strba <fridrich@documentfoundation.org>
Tested-by: Fridrich Strba <fridrich@documentfoundation.org>
|
|
Change-Id: Ie4f8ea605098b19e921f4e0d76211b5f2435de35
|
|
Change-Id: I275013be9e3587a73bd9bd6b20a2d42f850a83ef
|
|
Change-Id: I0d57f816abd05d8bb190fe47804b5a8db07ca6b5
|
|
Change-Id: I178f9eb702afb6143c583d5fd54003a427d895fa
|
|
Change-Id: I9b893906df5707f84c45cf5a8dc017873452aeab
Reviewed-on: https://gerrit.libreoffice.org/5403
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
|
Now it works this way:
* Auto close in end of current line of formula
* Auto close when we have "<?>" selected
* Auto close when we're in the beginning of current line.
We're adding a space between the brakets, like this: "[ ]" and putting the
cursor in the center of these brackets.
Change-Id: I8d77bfd7c33f875e7f4070343e634c2b6c45d33c
Reviewed-on: https://gerrit.libreoffice.org/5388
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
|
Change-Id: Ib185c067c52bb8c65441c30d4c61be24b0950afd
Reviewed-on: https://gerrit.libreoffice.org/5394
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
|
Fixed flip label (format -> flip) in writer - previously flip horizontally listed twice instead of flip vertically and flip horizontally
modified: officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
Change-Id: I0ceced973891699606ea6faa3ed3d8863a11c705
Reviewed-on: https://gerrit.libreoffice.org/5373
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
|
Change-Id: I5c98b96b77b1366884bdc593cf29d32d4e60de7b
|
|
Change-Id: Ib1deab33a8771e196d0520bae872eb0d492c913e
|
|
Change-Id: I4dd6ade18e72d8f57583180463f9dda3603be4c2
|
|
Change-Id: I8e5c4e240e64a1d70e599c4a8791133dddc0b75b
|
|
This currently (rightfully) fails.
Change-Id: I254dc7042e93b257765c8ed8cdb9904966afd77e
|