Or else it would crash when loading the doc from fdo#55174.

Change-Id: I21eb77f97dcab467c185dacaf9f00753bb4fc18c

Not sure what's wrong exactly, but on one tinderbox cl fails because
of "unknown" argument (unix path to the source file). Work it around
by explicitly converting the path to windows path.

This should fix the crash with gnome#627420.

Change-Id: Ibfff498282dc1c6fe9124ced645392107ef8829f

This should fix the crash with kde#245919

Change-Id: I7c3af01e27233d2f94d5585247c59e7d5b6ea8ca

Change-Id: I05c558b557cf083feb570f8ac14ecb75c1c21eb6

This should fix the crasher with the fdo#45266 document.

Change-Id: I41cf02f211e289b85c31b2d2d60e0c4d849b7e8e

Or else resizing and then putting empty elements may crash.  The flag
storage is used only for empty elements.

Change-Id: I1ada8f795a01336af185e6180bc03247c44472ba

The reported bug description was very concise and unit-testable.  We
should turn it into a real test.

Change-Id: I7383316e8fcf799a59b1c32a1722fd4b6b224d1c

Change-Id: I090a51c112c960b8cc9b208bc7378a5aa3754552

It uses QuickTime and Carbon.

Re-enable build with ICU 4.6 and 4.8
ICU versions prior to 49 don't know Conditional_Japanese_Starter and
Hebrew_Letter

Also, the change in i18npool/CustomTarget_breakiterator.mk

- -e "s#\[:LineBreak = Close_Punctuation:\]#\[& \[:LineBreak = Close_Parenthesis:\]\]#" \

with i18npool/source/breakiterator/data/line.txt

-$CL = [:LineBreak = Close_Punctuation:] ;
+$CL = [:LineBreak = Close_Parenthesis:];

did not produce equivalent results. Instead use

$CP = [:LineBreak =  Close_Parenthesis:];
$CL = [[:LineBreak =  Close_Punctuation:] $CP];

Change-Id: I14fc14319ea34f23393264560452a79bb49fc3a7

Also make the --with-android-ndk-toolchain-version option mandatory. Otherwise
it would be possible to leave it out and that would appear to work in the
configure phase but in fact mix stuff up when using a self-built 64-bit
tool-chain merged into a r8b,c,d NDK.

Sigh, maybe we shouldn't even try to have the configury generic enough to work
with any NDK version (which probably it doesn't anyway), but explicitly accept
only a small set of NDKs, like r8b,c,d (which probably are the only that we
work with anyway).

Change-Id: Iecdf3a2d841e7b29598228ae49f48eca9640a82c

Change-Id: I59edc4c437abccc201823d97f1cbec230d273b05
Reviewed-on: https://gerrit.libreoffice.org/1529Reviewed-by: Luboš Luňák <l.lunak@suse.cz>
Tested-by: Luboš Luňák <l.lunak@suse.cz>

Restore all cases to expect /mingw/ included in the path.

Change-Id: I5465c9176b0b53f9a148fe50373f38c71f179746

The bit-values do overlap, 3rd and 4th case were never reached.

Change-Id: Iaaf39a11811c4e28c34260a7eab7fa0476165d1b
Reviewed-on: https://gerrit.libreoffice.org/1497Reviewed-by: Tomáš Chvátal <tchvatal@suse.cz>
Tested-by: Tomáš Chvátal <tchvatal@suse.cz>

That means that there is corresponding .po file for given language.

As a slight optimization, do not even try to run uiex if _no_
translation would be produced.

Change-Id: I901e88b20edfb55e4f8bc661bacf8218b603bdcb

This got broken in a084ea60.

When running a unit test under GDB, we do not want to prefix the
cppunittester executable with the LD_LIBRARY_PATH, because that has
already happened before the "gdb --args" part of the command line.

Change-Id: If3f81ba3fc3e5260142d7e9c2d4a78e9ca63382c
Reviewed-on: https://gerrit.libreoffice.org/1532Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>

The form: OuterCtor( InnerCtor(array[i]).method() )
with explicit ctor(s), unused optional arg on ctor+method
--> error 'parameter can not have variably modified type'
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1).
Min fix: force precedence/associativity in type resolution.
fdo#58417 BTs inside 1 of these ctor calls.

Change-Id: I4d8b979df0fc827758b1e9a336031671425486ea
Reviewed-on: https://gerrit.libreoffice.org/1531Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>

OOXML spec says:
"[szCs] specifies the font size which shall be applied to all
complex script characters in the contents of this run when displayed"

Change-Id: I0faf599e38ef5a2e2005bb6f98874639be7d8287
Reviewed-on: https://gerrit.libreoffice.org/1454Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
Tested-by: Miklos Vajna <vmiklos@suse.cz>

All these are years old, guessing from some comments as old
as Windows 9x support. These workarounds do not seem to be needed now.

Change-Id: If67baa5cdefcec33b28696c764b1ed96143b7ccd

Change-Id: I23bd979aa39a8062f65f66e701cfd8ca3a18da8c

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

Change-Id: I0f57a5a3f9d4f710715a478439e87409378f151e

As that'd be like forcing a remake every single time.

Change-Id: I224baa5e62454afd998d1cb35144b1594d54d759
Reviewed-on: https://gerrit.libreoffice.org/1352Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Change-Id: I17dde604a94989e0f3fb0c8a6c0e3e6e1f362574
Reviewed-on: https://gerrit.libreoffice.org/1472Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

Change-Id: If1f3dbbbef07004ec02a65563524c6c17dc16c00

instead of SetSizePixel etc.

Change-Id: I17246821f1805bda9da0503e4fab05be5724512c

Change-Id: Ia17d3f4d14319adec6b0b20dced5daf5b8018c36