backslases and other 'special' characters can mess with
later path handling

Change-Id: Ic21b0eb82b60ffb2e286706be00148582ff9ad58

Change-Id: I11831583a0288a07fd6279411069d169ab854882

Change-Id: I38ed000a0f9c07fe8e1ed26752af8e172998bf2c

lcms2 for instance call MSBuild.exe, naked. it relies on what is found
in the PATH, but apparently MSBuild.exe can be found in many places
including for instance the .NET Framework.
This was causing failure with a VS2013

This patch inspect the registry to see if there is a MSBuild of the
same level than VS2013 and use that information to adjust the PATH
so that we invoke the right version.

Note: starting VS2013, Microsoft is numbering the version of MSBuild
with the same version number than VS itself.. so with VS2013 the version
of MSBuild is 12.0 (vs 4.0 before that)

Change-Id: I04c614116d1d365a10c9b9e0e8ce9571d770c065

Change-Id: I41534baa3cb98fc9af2f12605015a5653e552853

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

Since 9dbf817f (handle scope of
w:pPrChange and w:rPrChange properly (bnc#821804), 2014-10-01), this
caused an assertion failure -> crash.

Change-Id: I680edf58854d0c9be6e77c44c1e6beb1e0442a49

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

Change-Id: I95421d51a2750507aec5a576e161efe578fef812
Reviewed-on: https://gerrit.libreoffice.org/12020Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>

Change-Id: I828f4290c99e750df66548109ef8ae9b496af297

Change-Id: Ie150d2e497053966c5f75cea50c87888fda98659

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

Change-Id: I073372b74d0362eaffdc1dddfbef8767e58b0fd6

Change-Id: I0dd2f1d2efef7995aaf2ab7656c24178a02eb9cd

Change-Id: I72d2c4979b62a025d212ce5ee3b7141c40376fa7

OS/2 Metafile Format

aka

Presentation Manager Metafile File Format

this format appears to not to have a mime-type

Change-Id: I8b2356fb42272a6e0550abf09f46b051d22b64a5

Change-Id: Ic84e57fbfa2b532409865c4364b91be594d252cf

Change-Id: Id2847c55ccab7272919e76542bc0e0570bc9af12

Change-Id: I1a4dec8727d0a27f7fd0396fd22d955f61daaee4

we kind of have to trust this data

Change-Id: I1b74f8ad95008f5e759fd2267c879091edc5d58e

Change-Id: I03a30793e02def731cb6c8f130c48aeb325a2528

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

- Convert Deutsche Mark (DM) to Euro (EUR)
- Fix some whitespace

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

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

Broadcasting it here and marking formula cells dirty prevents them
from being entered into the formula tree at the end.  They get marked
"postponed dirty" during reference update, and are supposed to be
set dirty at the end.

Change-Id: I65977300ee4ee26b6166d170acd2145abcbbf288

Change-Id: I2fe455fc627e4b358507b58f08a3198ac62edad0

Change-Id: I4f9bc7ba26d42bfd3982efeb69bc221fc028c629

Change-Id: I7ac53b340cf3a9f72a90414e09ddd37148ecd28a

Change-Id: Ic79ce25bf4ceb4d715aabdabf3824304b02b1f38

Change-Id: Icf1fc5643271672761b565c30382e70c689c29b4

Change-Id: I6b44707b8d1be526e6c0400d7c7104628b825fc5

Change-Id: I1cf551299bae925b5a5cf0a488b6cc3497d010bf

Change-Id: Ida4309aeb69bde43f70415211490db657c7c7567

Project: translations  781673fea7346b0d148bf85984826c0556fdf1b9

The problem was that in case a paragraph is empty, and it has both a
character style and direct formatting, then the doc model created by the
ODT and DOCX import is like this:

<text>
  <attrset>
    <item whichId="8" which="character font size" value="nHeight: 240, nProp: 100"/>
  </attrset>
  <hints>
    <hint end="0" whichId="52" which="character format" value="name: hello"/>
  </hints>
</text>

I.e. the direct formatting is stored in the attribute set of the text
node directly, while the character style is stored as a hint.

MSWordExportBase::OutputTextNode() tried to read the hints and if there
were not any, then tried to read the attribute set, while in this
situation we need both.

Change-Id: I71fd10f6d00246348e77fee5431cb4e2a7c9b349

Redesign of CurrentDb, CurrentDoc interfaces.
Creation of new Root_.xba class module.
Console logs, TempVars and Dialog collections are unchanged.

Change-Id: I573a75e8fb54b277aef84d4518cc8e5cc21d7270

...since introduction of XLayoutManager's private:resource/menubar/menubar in
3fb2acf5 "INTEGRATION: CWS layoutmanager
(1.52.10); FILE MERGED" etc. and final removal of SID_TOGGLE_MENUBAR bits in
f605b16e "INTEGRATION: CWS sfxcleanup (1.119.8);
FILE MERGED" etc.

What still needs fixing are

  extensions/source/activex/SOActiveX.cxx
  odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/CustomizeView.java
  odk/examples/OLE/activex/SOActiveX.cpp

in a similar way as e.g. 0273d3d8 "INTEGRATION:
CWS jl18 (1.6.8); FILE MERGED."

Change-Id: I52a43fc7186a4f60929ab6246a2da2e715be7510

because the first export has left "dangling" CalcFieldValueHdl Links in
Outliners that got created based on the Drawing Outliner while it had a
temporary CalcFieldValueHdl installed, and didn't get the old CalcFieldValueHdl
installed when the old Drawing Outliner one was re-installed.

Change-Id: I064a154ece488c9a4c3467b753451df7e73ae883

Change-Id: I4a2c49befe4baea10e36e0d612371fe8c91db401

Change-Id: I8eb5158cb2aa39b5eac45c554d722b9de1c8abe8