... for the PythonTest, similar to what vclbootstrapprotector does for
CppunitTest; actually no idea if this is a good idea or a bad idea.

Change-Id: Ia4e2e50fdc9c8deb9faf580a2f3f3308533265eb
Reviewed-on: https://gerrit.libreoffice.org/17540Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>

Change-Id: I83396e7c90d3b182f353a77c9bdf06fd17af92a1

regression from

commit b3abc191
Author: Laurent Balland-Poirier <laurent.balland-poirier@laposte.net>
Date:   Wed Jun 17 15:15:07 2015 +0200

Change-Id: I44cfd85e9f7be65929281169fd297252e00c7317

Change-Id: Ib93b818eeebc2f370535d1b061beabf7e8c65257

Change-Id: I39295d69dd8a48f0f40275830cb6fda4ca0b69f3

Change-Id: I55848b3fedae79d714c8341fd84d505cb83a7c2c

Regression of ece8699f

Change-Id: I1aac18dcb469b30de625c5cbfb5b0dd27fe33364

Show the whole height of the cache bitmap after all (when SAL_LOG
contains vcl.gdi.opengl). The interesting pieces are often at the
bottom, like the tip of the hook of the "j" glyphs that used to bleed
over into the preceding glyphs, usually "i", when they were rendered
into the same chunk.

Add more space between glyphs and at top and bottom of the bitmap, for
anti-aliasing. The glyph ABC widths don't take expansions caused by
anti-aliasing into consideration and are misleading. Hopefully
anti-aliasing can expand the (partially) painted pixels of a glyph
just one column/row in each direction, but for safety use a two-pixel
border. (Defensive programming, eek?)

Some getWidth() instead of GetWidth() etc craziness. Using
<tools/gen.hxx> types truly is programming-by-coincidence as Thorsten
says.

In a dbgutil build, setting the environment variable
VCL_GLYPH_CACHING_HACK_NO_ANTIALIAS causes the code to turn off
anti-aliasing for the fonts used. I used this to verify that it indeed
was anti-aliasing that made the ABC widths inconsistent with
reality. Not sure if it makes sense to keep this code in?

Anyway, now I don't see any leaked pixels in "i" glyphs any more,
touch wood.

Change-Id: If527343ff1dcdb1fa208cd5e7fa4d08f812d0d7b

Change-Id: Iad48cf4949cb4a398a8abee32febaf8e152dade5

Change-Id: I887c358161f7ac4032b9ad9166ff16aa0b19eaa1

Change-Id: Ibf5095fea20314180a4e002295c89f570d66d45f

Change-Id: I1bfb99b1715a907a03af5a30df6c7a41f91fd2fb

Change-Id: I7033e1e60f67e93a31d19ea08513982643dd61ae

Change-Id: I4fdc77c6fde93d9d1ee814f7614a1c4c81e18247

Change-Id: I2120ed72c281d2078e387f7f3ae91004ad95822c
Reviewed-on: https://gerrit.libreoffice.org/17855Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>

Change-Id: Ia7de1cebf6009e770ca1b96bab6d5e121573ccc1

and thus fix xlsx-specific issue that 1st sheet can't be hidden.
Also kill some UNO in the process.

I'm not sure if guarding against all sheets being hidden (by having
at least active sheet visible) is absolutely necessary, but better
be safe than sorry.

Change-Id: I4ad21d223b2effe427ab1d5411c035886f6cc71c

Change-Id: I1b74fdfaa09c4d0d6c296253958e83e78b546a9a

Change-Id: I2665a12251921523045f4071df88ca69ecd5a5c0

Change-Id: I29cb771eb059f560b7cbd449257ffda581b40f11

...became redundant with previous commit
d3d7cb98 "Remove ConvertOSLtoUCBURL."

Change-Id: I08c436dec8ed661eae60a17723fc63e6aafb1f86

"Not all OSL URL's can be mapped to UCB URL's" might have been true in the days
of vnd.sun.star.wfs, but I can't see any good reason for this functionality
today.

Change-Id: Ia887531ee9fa70092766406cee1fc8962576a8ac

together with 58d68a1b
"ConvertURLToSystemPath->getSystemPathFromFileURL" and
28f3464a
"ConvertSystemPathToURL->getFileURLFromSystemPath," this replaces all those
Convert... functionality with direct calls to the corresponding osl::FileBase
functions.

Change-Id: I2876171cd337a5eb939d25d8cf1e0c1253ff73a7

with the variadic variants.

Change-Id: Ibe00b26512a4895a603a084f4e816c74b99894df
Reviewed-on: https://gerrit.libreoffice.org/17850Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>

with the variadic variants.

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

Change-Id: I209fbef9f2ee43031175b68bce86b51724dfeec7

Change-Id: Id3d2e7b404c70307ecccc2571072b12229265cf6

...given that vnd.sun.star.wfs is long gone.  Note that the old code could have
behaved differently in that for one it could have worked for relative URL input
(as osl_getSystemPathFromFileURL is allowed to accept relative URLs) and for
another could have failed for some file URLs (for which
osl_getSystemPathFromFileURL would return something other than osl_File_E_None
for whatever reason), but it looks plausible to assume that what the call sites
are really interested in is whether a given URL is a file URL.

Simplifies those call sites that already have a INetURLObject instance even
further.

Change-Id: Iaee4595d933a760b8321e42414a9ef0865311833

Change-Id: Ie0931d378c72ff5aaa5d50006141eaa651281ba7

Change-Id: I59dbfea2230012447732d12f732ad160a30908e7

Change-Id: I934ad7453f35909f4c3ad999e33453b5b6032480

Now text looks better, for instance the lower-case "t" glyphs on the
Start Centre aren't totally weird any more. But for instance the tip
of the hook of "j" leaks into the "i" texture. I guess I really would
need to render glyphs one by one.

Change-Id: I69ae2d2f7c559530bcfdfc1a4915503fcb3ab4af

Change-Id: I0bbea4ef62c8e94d8b8f1bfb440712da5839e532

Shows text roughly correctly, but many problems. Conditional at
run-time on the SAL_ENABLE_GLYPH_CACHING environment variable in
addition to SAL_FORCEGL.

One obvious thing that needs fixing is making sure that the glyphs are
rendered into the texture without overlap. Compensating negative
values in the ABC::abcA and ABC::abdC width is not enough.

Also, the cache should be changed to actually have "cache"
functionality, i.e. entries should expire based on some criterion.

Change-Id: I66a37d3354a09011a654f15a7d2bd8efaa14ad1e

Change-Id: I780e18b7afee470cff525904687746e163d30bdd

No need to spell out otherwise auto-generated functions.

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

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

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

Change-Id: I1c60c60f9b5318626f42e33091920a4404fb6d1c

The glyphs for %phi and %varphi symbols were swapped in commit
81001f2c (back in 2009), as part of
https://bz.apache.org/ooo/show_bug.cgi?id=105084 (see the document
attached there), but no justification was given.

Given the shape of the symbols after that change contradicts the ones in
the Unicode code charts and other popular math fonts, I simply swapped
them back.

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