libxml2 has a problem when a document encoding is specified, even though
documentation says that all internal representation would be in UTF-8 and
language-subtag-registry data already is passed in UTF-8, when specifying the
document encoding to be UTF-8 the output to language-subtag-registry.xml is
conversion garbage, '?' on Linux UTF-8 locale, ISO-8859-1 on Windows. If no
document encoding is specified at all no conversion happens and non-ASCII
values are correctly written as entities.

Change-Id: Icc314cf12cfcf41813ceab7071b6e655909a7c7e

Change-Id: I80bd0329e15cb365091ea6f5c7e1ef3559d681fc

Change-Id: I06a02a97491c2ea0408c881451d17d464fead090

The aWork buffer is missing space for the null terminator, which the
previous String::AllocateBuffer automatically added.
(regression from aac04652)

Change-Id: Ia12ad46dfb95dd59965a073debb95b241b2e97d9

This is a follow-up patch of be88027c
translating the remaing comments that were missed there.

Change-Id: I7866060ef6eec5f92751671bd4fc4bee64db149b

Change-Id: I000fc9c1328aec5924da1557da599e6c7bdcb373

- Only when experimental features is set.

Change-Id: I81e2bba38506757afe202cba5c69560e3fa89f3c

- Move entry to File menu instead of File->Templates.

Change-Id: I3c7df6057f9634d0e3879c90e0760f1fecc98954

Change-Id: I4a26d9039df748c25b6de1e01844bb57b0988e19

Change-Id: Ie9ad44077df03ba8e5e4edb4068982a0f8af353b

Change-Id: I587484f72c5751b07636339c1eb4748cbfe1ed78

Change-Id: If781865ad802c411187c5b5cc4ed71a5deaed4f7

Change-Id: I3291fad1455d289c35543c3b360b9fee620da3e9

Change-Id: I8ae47ffb38febdd467e1e557448189dd09e755bc

Change-Id: I22a759ef55a46dc560ebe5f802c937f1d47bf645

Change-Id: Ic8d149a78b2bc2bf352b7893202d0d0b6730746c

Also checked the following with bin/find-german-comments (all
false positives):
- sysui
- xml2cmp
- udm
- ucb

Change-Id: I2c72f973f5cecf56d70b5419e56338170dd55a2e

Change-Id: I9b7a61f18f987214708195a89f6e346c865c7f9f

Change-Id: I84f4929eb923bc3d05bdf04a8958cb58b5bfb921

Follow-up patch of b803fa25.

Change-Id: I86bea8483cc9a9703cc725eaef641c2df5896af0

Files were originally touched by b803fa25.
This is just a follow-up patch.

Change-Id: I1e35d5e3c3d193bb5dfdb4b743328d8d22466a4d

Change-Id: Ibeb903c03a9c4c8638985847f527ebfa7c2756ce

Change-Id: I9965a5ee383c4380dc1e75abc6a8df17ed69f6fc

Change-Id: Ib61ab9ea33ea94d6175a2110105849279d1ad440

... that was an oversight in 5300f6f7; thanks
Petr for spotting it.

Change-Id: I4d0179165bc3b29d698cd776f7e1aa51fa73ebe3

... as it causes problems on Windows:

file:///C:/lo/core/solver/wntmsci12.pro/share/liblangtag%5Clanguage-subtag-registry.xml:709: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE5 0x6C 0x3C 0x2F
     <description>Norwegian Bokmål</description>

Apart from the encoding issue (looks like that language-subtag-registry.xml
delivered from module liblangtag is generated as MS-1252 rather than UTF-8 on
Windows), what also looks worrying in the error message is the backslash encoded
as %5C (and the entity resolving that URL apparently decoding it somewhat
naively).

Change-Id: I756f911a92b144e3732f63668d36b4ae941f975a

Change-Id: I542e563df68d38691f7c95cebf66aeb32071bd66

Change-Id: I2fb2004f2f755ce337ddd1419acf2510f17622f3

Change-Id: Ia31e33fca6dca47faa1fad1a5879c3902df05835

Change-Id: I11733daf2668c4142052ceb4498f5500e7e291ef

Change-Id: I4836d7f2055c4811f0e6ccdc87dc58895528b3f8

Change-Id: Ic38d0282dba99efe2ecc45142a927ba3d8fa167d

Change-Id: I97312c746e8a76af73851c474b0c6c2491c44803

and don't let the moribund fading-out button pursue the mouse

Change-Id: I6f821f7e8144e9448c1cb65f8ce96102419cd6f0

it seems when the mouse leaves the dashed line, it immediately appears inside
a button (if the mouse motion is not super-fast).

Change-Id: I43c792fdba59feafd761bde8529a8683c07bf3d3

Change-Id: I9366de24414fa10e292e42df08a9658d90e5c1c1

Now that 5c47e5f6 "fdo#51252 Disable copying
share/prereg/bundled to avoid startup crashes" removed the use of share/prereg,
there is no longer need to generate it in the first place (by calling "unopkg
sync" at build or installation time), and so no need for the "unopkg sync" sub-
command, either.  This also allows to simplify some of the jvmfwk code that was
only there so that "unopkg sync" (which can require a JVM) can work in "hostile"
environments (during build and installation).

Change-Id: I52657384f4561bf27948ba4f0f88f4498e90987f

Change-Id: Ia8179d4333434324dd4b5239691402d0e48da5a1