Change-Id: If52de6e7fbfef92ab53086c6dcc405dad6cffe2d

Change-Id: I5b2f0e0a0c75eea14903e333eb17613d0499f458

Change-Id: I716d8b190aa4b65b878559a4e5e88a126a56bf99

Change-Id: If23175eebaccc4bfce2d921ed8d1ae66832178de

Change-Id: Ida136f1113b9e1df35559715b74573dabec6ac7d

Change-Id: Ief5b4645a75a86a9df6d52354c17ec5322fdee01

Change-Id: I920cf103a28132b0f8ed6748f9f743d1bf3db2d7

Change-Id: Ib69bdfd66328c1e4e3d8a0a03e4360b23e69a476

Change-Id: I5508b6a04a894c747a49ca19f559ff448334d026

Change-Id: I562ab15e54647248f13276d9213ac5658fb2dc4a

Change-Id: I4eec7a6de077b3571bd8a0b5cb69ede838712736

Change-Id: I6981781d2842d06631216edc7509d96d878285b6

Change-Id: I1e4712c4c6eae890b93936f25632aa8a7422e1db

Change-Id: I9f36b29e329dde3b841f963d9dde3480e80da3f5

Change-Id: Id15b58374df59d03e344cea7f23ae6b5963f668a

Change-Id: Ia618b71047f27a0400b8a9eb2c14e319c66e05dc

tdf#40091 Vertical writing inferior to MS Word
tdf#40335 Using Right-to-left (vertical) for text, the characters
overlap each other. Cursor is placed at the half of the character.

It seems that current implementation use HarfBuzz OpenType layout
API hb_buffer_get_glyph_positions() to layout the text, however
instead of setting text direction to HB_DIRECTION_TTB, it
uses HB_DIRECTION_LTR as its direction and rotates each CJK glyph
to simulate the HB_DIRECTION_TTB. However the API use font width
to position each glyph no matter whether the glyph will be rotated
or not.

Change-Id: Ie35238dd92218f8c4463c0ae1d356ad8609c5f48
Reviewed-on: https://gerrit.libreoffice.org/17774Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

This makes for a better user experience when the idle jobs
haven't yet ran on some text to check for spelling.
This can happen when the user is on a device with insufficient
compute power and/or other idle jobs with higher-priority
take precedence.

This change leap-frogs the spell-checking idle job when the
user might already know they mistyped a word and look for a
quick fix via the context menu.

Change-Id: Id1f7b4555050ded329ebeb56502f893ee7b2bc35
Reviewed-on: https://gerrit.libreoffice.org/17252Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

Also fix some whitespace and Doxygen comments

Change-Id: I0a3440cdff2b1b74b2aa4572fc5c92c1525bfd61
Reviewed-on: https://gerrit.libreoffice.org/17549Reviewed-by: Phillip Sz <phillip.szelat@gmail.com>
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

Change-Id: Id69a03b0379becc4c267a85eb7567bbbd41ccf82
Reviewed-on: https://gerrit.libreoffice.org/17755Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

characters. Now it detects CJK language and ident accordingly:
2 chars for Chinese and 1 chars for the others (Japanese and Korean).

Change-Id: Ib722e90ecae615faa7887ce1c874aacbb93f8a5e
Reviewed-on: https://gerrit.libreoffice.org/17614Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

characters do not take account of hanging punctuation. Note that
placing a cursor next to the hanging puncuation is still not possible,
but the selection and the non-printing characters works fine now.

Change-Id: I22c8c2c5044b46c325236caffec67d9f68c23eed
Reviewed-on: https://gerrit.libreoffice.org/17591Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

Change-Id: Ife1b85cc55e4e0f4d0be84bbcdfc93104160f271
Reviewed-on: https://gerrit.libreoffice.org/17470Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

This is a regression introduced by fixing tdf#47018, which
changed the default NumRule and pushed a lot of SVX_MAX_NUM
to the SvxNumRule constructors.

The changed NumRule default seems not needed to fix the crash;
at least it still doesn't crash as described in the old bug
report after reverting this part of the change.

Change-Id: I908eeb4a827799419d3f28584fdcbc9272cbc76d
Reviewed-on: https://gerrit.libreoffice.org/17527Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

The more redundant cases of whitespace/comments had to go...

Change-Id: Id0bfab5f60f123c0a4d3d9f8468791e0d8046225

Replace ::std::for_each for a more readable range-based for loop in
cases in which the function object to be applied by for_each is more
readable as the body of a for loop.

Change-Id: I6f96833d7f251d44e2308278bb92a7d49fd49bcd
Reviewed-on: https://gerrit.libreoffice.org/17763Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>

Change-Id: If3ce8feec940c7212fe467f39db868630522b17e

we retain the max-short limit but no longer add a null terminating entry

Change-Id: Ie195e0c244cc08643a9c22518c85d70a883752b7

exedir has to be in the c:/foo form, instead of /cygdrive/c/foo,
otherwise a native wrapper set by LO_TRACE won't understand it.

With this, it's possible to use DrMemory on executables invoked by
bin/run.

Change-Id: I5332342fdbf7d9e4859360dd7fbd3d74c149b2dc

Window ( 7VclVBox()) with live children destroyed:  7ToolBox() 10PushButton(Click me; go on)

Change-Id: I7b95198e24ea4d6ab085705096421219b3e16904

Change-Id: I90f784859e9d4f246f570e033b7e18c335588fd0

Change-Id: Iae650d63ccdb95a0a74674b8689813069b750b60

Fix a problem when neon send the token list for
methods modifying a WebDAV resource.

The problem showed up when working whith Sharepoint 2013.
Other WebDAV servers seem unaffected by it.

The If Request Header is currently formed in neon using the
"Tagged-List" format, while Sharepoint 2013 only accepts the
"No-Tag-List" format.

References:
section 7.5 of RFC4918:
http://tools.ietf.org/html/rfc4918#section-7.5

section 10.4 of RFC4918:
http://tools.ietf.org/html/rfc4918#section-10.4

Change-Id: I24d607fde251f1846f0e7b630b627b1500da18ea
Reviewed-on: https://gerrit.libreoffice.org/17423Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Jan Holesovsky <kendy@collabora.com>

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

in other words, don't override user's configuration of string ref
syntax

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

that is, CalcA1 for ODF and ExcelA1 for OOXML

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

Change-Id: Ica385b513d87d639496ac470da296e871b093ab4

6b4c596b "Fix memory leak for BASIC sub (as well
as void function)," from just looking at the few lines of code in isolation, and
their revision history, looked like a plausible and effective approach to fix
the leaks reported by CppunitTest_basci_vba when run under lsan.

However, tdf#92446 indicates that that innocent-looking change had rather dire
consequences.  So revert it and leave a fix for the memory leak to somebody who
actually understands all this code.

Change-Id: Ic81b1c14a1cfb07c6ec4415cc26b2f826adbc8ca

with the variadic variants.

Change-Id: I6acff50f23bcbac58c689caf2a7f07dbd5404e57
Reviewed-on: https://gerrit.libreoffice.org/17734Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>

Change-Id: If432f002804678a80963b02e57eba8d314a6f34c