Change-Id: I764a88f110f5528cabc1e223ffc63079954c534f

Change-Id: I4f9dd7b273e52fa97a7f79bf77a76ae5412c5e10

Change-Id: I3af5f97e77240a0f0a3c96cffc03c8a005e8f0aa

Change-Id: Idf6831ef21cf94926667ca532d9df2a18926e452

Change-Id: I31f1941daf158676518fcf259ef8a9e84863473e

Change-Id: I6f53cd0ee1e7acd724186ab914bde43026ef6708

Change-Id: I7dfb69ff45ddba07255cb0000efea9f87c13cd2b

Change-Id: Ic91c65fc1f74fbde86c2448d1c394a5e30452a75

Change-Id: If535bbe07df95f93d052705cb665d1b4cae5af01

Change-Id: Id565602f4cb488176451cfcc1d2aa05e7acab964

Change-Id: Iba538bb51635e6cae1e033d14e8da3dabfb36634

...to cater for forthcoming loplugin:implicitboolconversion improvements

Change-Id: I801b6b73648715448198d582a087cc834f6e20c8

Change-Id: I48d63276ae0aaeba169e1e783c44b428a58314ac

Change-Id: I7cd697d944dc0efbd35b852fc553ba85bc88c15e

Change-Id: Ia41276033c1f656217bc3ae929faab001db36ca4

Change-Id: If6c836c7e155c958a56fb69a06730c4e5a9ee1b5

Some versions of gcc clobber one of the registries that are used to pass
arguments in the function's prologue, like:

Dump of assembler code for function (anonymous namespace)::privateSnippetExecutor():
510     {
   0x00003fffaffe8454 <+0>:     mflr    r0
   0x00003fffaffe8458 <+4>:     std     r0,16(r1)
   0x00003fffaffe845c <+8>:     std     r29,-24(r1)
   0x00003fffaffe8460 <+12>:    std     r30,-16(r1)
   0x00003fffaffe8464 <+16>:    std     r31,-8(r1)
   0x00003fffaffe8468 <+20>:    stdu    r1,-352(r1)
   0x00003fffaffe846c <+24>:    mr      r31,r1
=> 0x00003fffaffe8470 <+28>:    ld      r8,-28688(r13)
   0x00003fffaffe8474 <+32>:    std     r8,312(r31)
   0x00003fffaffe8478 <+36>:    li      r8,0

Reading the registries through variables makes gcc aware that they are
used, so it does not touch them. It has got no negative effect on
performance, as it produces the same object code as the current asm
block.

Change-Id: I3b99b0aa9944f9f33de9a42508e9d4dd23cec5e0

Variable decimal is only saved in ODF for number, and do not consider
partial variable decimal: 0.0## is saved as 0.000
This patch extend ODF with loext:min-decimal-digit for number format and
scientific format

Change-Id: I5022458da47bbd33c3e195c280e75c43faca5f8d
Reviewed-on: https://gerrit.libreoffice.org/15135Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Scientific Format without sign in exponent, such as 0.00E0,
are managed by LibO, and can be saved in XLS format
This commit allows to save in ODF

Change-Id: Ia0c4589e2af942543ea296f970d163bc1d1d6f05
Reviewed-on: https://gerrit.libreoffice.org/14955Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Change-Id: I615a9ed50141327d672e12db1da500d372ff5232

... which leads to swapped decimal and group separators in this case,
which were wrong before and generated wrong format codes.

Change-Id: I08a74262f7e1d8453957895beeffa34116cb4577

... which leads to identical separators in this case.

Change-Id: I061c9f47d052e6e30e3b01d1697dc814e104559d

... which leads to identical separators in this case.

Change-Id: I85ea0004344532221c9a03b29b2f1ba2e0100ac8

... which leads to identical separators in this case.

Change-Id: Id886917de66df046481f957ec467e74942d7ba6b

... and the only difference to es_GT was '-' vs '/' date separator,
which according to
https://ssl.icu-project.org/icu-bin/locexp?d_=en&_=es_NI
should be '/'

Change-Id: I10aeb0849132b3502e73163261060d2e6eaa1c39

Change-Id: I7236d79877e6761cc97cbc093b83033deb84b417

For all l10n, add format for engineering format ##0.00E+00
 decimal separator adapted
 msgid: ScientificFormatskey3 or ScientificFormatskey4 if previous one was
already used
 formatindex: 78 (free in most l10n, and near 77 which used as
scientific format for many l10n)
   exceptions: ko_KR formatindex=91; th_TH formatindex=88; zh_TW
formatindex=80 (next free value)

Change-Id: I703c1503bdac85386e9994fdd67b00aa6006d992
Reviewed-on: https://gerrit.libreoffice.org/15527Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>

Change-Id: Iea949e5936f58317e64e60a407613bb99ae113ff
Reviewed-on: https://gerrit.libreoffice.org/15489Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>

Adjustments to character positions less than one pixel are ignored.
These adjustments are probably introduced by lossy conversions between
integer based and float based coordinates. 

Change-Id: Ie4506658aba7bb3e2b211817568676b099afef03
Reviewed-on: https://gerrit.libreoffice.org/15539Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>

Change-Id: I9ad2a52434329acc961db2e5a3e28816af7cda7c

+ unify terminology image vs. graphics

In an ideal world, those strings wouldn't be duplicated in both sw
and cui and change like this would be done in a single place. But
there's currently no straightforward way how to share strings between
those two ...

Change-Id: I5311aca3e7b4070c82cf4f84f96ab1b6eff473c6

Change-Id: Ib0d04c00ff4689d53317dedbf67091596cc59fb0

Change-Id: I6c4e5291b24015087b3ac56e2e178dbf42bf193f

Change-Id: Ic7e2c3a76abf658cc4e639772e05c83851c1da71

as in the ctor

Change-Id: Ib95768397dc99d09154af03846f001d647437b69

and can end up with a font size entry in the toolbar
of a different height to the other elements, because
the other ones only call it on DataChange, while
font size calls it all the time.

Change-Id: I495e28dd0d33a093869fd731538e43513a7b8b85

Change-Id: I22fb833b59b7e2d749f8111d897f81899019e2d5

Change-Id: I38d5582e36fda2471a53e48f0611011bef30f5fe

Change-Id: I0890a7d8c50b8646782bfc4358aa7c2f106dc22d

So until somebody has the time to figure out what is really going on, just
don't assert when being used from LOKit.

Change-Id: I5c4a87b94e7bd7ffdbf90973387b61407b8e6c8d