Age | Commit message (Collapse) | Author |
|
Change-Id: Icdda77d0fda4faf071566a44c2b93285a6437d38
|
|
Change-Id: I83c6bd1bfb44e74b9f659a970b5c32d7475addfb
|
|
Change-Id: I4a2bc7307e40ddb8a9a039c1d1b738338dcc5122
|
|
Change-Id: I78f7f7ae7373e00e0750abc4566c71a8b9c1640a
Reviewed-on: https://gerrit.libreoffice.org/1019
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
|
|
Change-Id: I5d09e297294439fafad94177d8e87ccdf829b18d
|
|
I wanted to add one, based on OUString one, and Stephan on IRC agreed
it's a good idea. Then it turned out we already had it in sal unit
tests, sdext and unodevtools as well. Get rid of all these, and have a
single implementation in string.hxx, so it can be used everywhere.
Change-Id: Ibb820f20a138d055fd87036253c627fb862a31fe
|
|
Change-Id: Iee3fa02bde03ced462460e4ba3e17200f47a27e5
|
|
Change-Id: I81fa1217feda5b4faf73add5304e8a191bbfbdc3
|
|
Change-Id: Iec1e114fd6803624ad5ef6812ab50c8e8a4695fa
|
|
Change-Id: Ib9956bd2671434fc15905e7c4fd56bd8f7162b60
|
|
Change-Id: Iea8388c16de3399853dc384e7df6bfcc92170ea2
Signed-off-by: jailletc36 <christophe.jaillet@wanadoo.fr>
Reviewed-on: https://gerrit.libreoffice.org/1018
Reviewed-by: Ivan Timofeev <timofeev.i.s@gmail.com>
Tested-by: Ivan Timofeev <timofeev.i.s@gmail.com>
|
|
Change-Id: Idb8c0587fd180416af2079d94fcc3e1fb5c734b4
|
|
Change-Id: I9cb276963155004361be86ec7a05c3597ff4ba4b
|
|
Change-Id: I633892a6d611e6481e49f9bd2739d3886563a24a
|
|
old code used to use XCell->setString, new code uses rDoc.SetString which by default tries to detect number formats. The ScColumn::SetString that eventually
gets called seems to do lots of additional checks ( and apparently even if
an ScSetStringParam instance with mbDetectNumberFormat ( false ) was passed
it seems that it will still try to detect decimal number formats. With that
in mind I restore and un-unoified version of what XCell->setString used do
Change-Id: Ifaef74c78b198f492a390a3d5dc1721622a01ea4
|
|
Change-Id: Ia563ee1e100bc86e9b7196bdce6311e24bc36f9c
|
|
Change-Id: If026dd160e2abe51470273115cbdd8b556ee9356
|
|
Also MSVC does not like libraries that do not have any objects.
Change-Id: I172fe0b61db9de6c7c4975a7b7c7fa63624b1865
|
|
... which i've also managed to break, unaware of its existence.
Consolidate 2 different ways to use VALGRIND_CFLAGS.
Change-Id: I245c7a9a2b6bc904a227a15063cf5d8a2f64313c
|
|
Change-Id: I151aa45838edbaa713b40716e45a75e812b7c782
|
|
Also unbreaks the build because VALGRIND_CFLAGS is now never
empty with cedd9ebdd260e99e74ad54391c0d0b1d1ebd9891.
Change-Id: Ide5ca799b3656ccaff483ca05dbc18682136345f
|
|
Change-Id: If693e440327331ea007722ff575b8015d727e5bc
|
|
Prepared private methods to force compiler errors during conversion to
LanguageTag. Commented current usage on some methods.
Change-Id: If365e24c7cf06bdf33ecd0bc15ddbfe33cd347c0
|
|
old code used to use XCell->setString, new code uses rDoc.SetString which by default tries to detect number formats. The ScColumn::SetString that eventually
gets called seems to do lots of additional checks ( and apparently even if
an ScSetStringParam instance with mbDetectNumberFormat ( false ) was passed
it seems that it will still try to detect decimal number formats. With that
in mind I restore and un-unoified version of what XCell->setString used do
Change-Id: Ifaef74c78b198f492a390a3d5dc1721622a01ea4
|
|
Apparently some people still try to source it from shell (scripts).
Change-Id: If26a5c5eb83739d3ccce043afd095000d355a543
|
|
Change-Id: Icba39756a54d1225514048c55ddad0f31ce31699
|
|
Change-Id: I50f4396e6a8abf32d1a0f63cbfa93d2c59375326
|
|
This allows us to simply pass the already exported variables to invoked
configures, where the non-empty values will override the detection logic
there.
Change-Id: I7353a313814c58922e34843aeae380e5afa442ca
|
|
Change-Id: I05df8435874eb65f3acedaaea50b4910e9fc9111
|
|
- partial implementation of the SessionInstaller interfaces
- accessable via service:
org.freedesktop.PackageKit.SyncDbusSessionHelper
Change-Id: Ica91f481d041a066215fba3e808bf587e1271f1b
|
|
Change-Id: I9acf8198ac19c3e448bb7d65116e408ac179993e
|
|
Change-Id: Id80013cbab8f1633db59d2d4492c7363224871bd
Signed-off-by: jailletc36 <christophe.jaillet@wanadoo.fr>
Reviewed-on: https://gerrit.libreoffice.org/1016
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
Change-Id: I581fb38e3f3d24987dcf92e73caf736203fa9385
|
|
Change-Id: I0f458caa1bda23882c76cbae414b738a5d04ab32
|
|
Change-Id: If2477b9a391d75672a349ba240ceb61e0b06611a
|
|
Change-Id: I0ab5a25cafdd246828ba09db8d01bb498e7012ab
|
|
Change-Id: Ida7914d7301c16ed1771be3d874c716c8fbaf8b4
|
|
Change-Id: Ie648ce55fdc11f907f5f5b3b958c13c695f392c5
|
|
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
|
|
it is fairly common when converting String to OUString
to find code that search for thing and replace/delete
these things... the later need OUStringBuffer, the former
OUString.
This add the search feature provided by the indexOf family
of function found in OUString, into OUStringBuffer
Change-Id: I2de818e6317a94ed520f338ebc9ed08d5f17765c
|
|
This is still not complete, but having the replacement graphic only is
far better than having nothing.
Change-Id: I141a3de1a449f4261c7086e10f2c141b3f6cdb10
|
|
LCMS2_CFLAGS must be non-empty for it to override pkg-config.
|
|
Use it in the cases where I yesterday changed SAL_DLLPUBLIC_EXPORT to
JNIEXPORT. It turns out that on Linux JNIEXPORT does not enforce
"default" visibility, but expands to empty.
Change-Id: I033b3cf538715fb596e965e17f3da12fb987df63
|
|
Change-Id: I376b03d12f8ae59fcf75046c42bcd6ba5d29af2c
|
|
|
|
Now with DISABLE_DYNLOADING, SAL_DLLPUBLIC_EXPORT actually means
hidden visibilty. Which is OK in general as with a single DSO (or a
single executable, for iOS), none of our "normal" entry points need to
be visible froom the outside.
So for the JNI entry points use JNIEXPORT. On "normal" platforms it
should be equivalent to SAL_DLLPUBLIC_EXPORT.
Change-Id: Iad634950e635ac03a0e90cae6d00afd9fb4eeb64
|
|
Change-Id: Iae8f93d096178532e2384a13b36e1385269aa14f
|
|
Change-Id: Ib766a4ed49d089488fc4ec67b941be2f38ba3ac3
|
|
Change-Id: I0261d30f20c88fc324194f687ebba3afd980117d
|
|
Change-Id: Ia3c103e4343d309b997ed37e33a382ffdfbddac3
Reviewed-on: https://gerrit.libreoffice.org/1014
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|