Change-Id: Idd127d949837a4b327a77217abe70f50e3633d78

Change-Id: I63f7914b52af51b55a51d39953a1ee58636243a3

Project: help  23e837dd59c455baeae5f8d691fad3e3b9db52d6

...and replace gb_CppunitTest_unset_headless with
gb_CppunitTest_use_vcl_non_headless.

Change-Id: Ibd859f98ed8df09988ca26ffcee26e06e25d8313

Change-Id: I9d4255f0ddcaf375706556d0c0baf2a5a0762bbf

Change-Id: I64cf70cf7f1f77c38a8a4804b705ce8a0441e487

Currently font names like "微软雅黑" (Microsoft YaHei) are
written as "????" in the RTF export; to avoid that, set the \fcharset
of the font entry to something that at least is able to encode
the font name and alternate name.

This requires a new function since the existing
rtl_TextEncodingToWinCharset was changed in
b88fe998 to return "default" 0x01
(for OOXML) which is quite unhelpful for RTF.

This is not entirely satisfactory, as of course that is no guarantee
that the encoding can represent all of the actual text that has the
font applied; hence there are some \'3f in the fall-back encoded text
of the heading of the bugdoc, which indicates that the detected
Shift-JIS is insufficient and GB-2132 would be required; but it's not
obvious how to do better here without iterating over all the text
twice, and that still leaves the possibility that all text that has a
particular font applied cannot be represented by a single non-Unicode
encoding.

But since we always write text as the \u Unicode + legacy fall-back,
this should not be a big problem since modern RTF readers will simply
read the Unicode.

Change-Id: Ie6a42294c501d014dd9f0df82638519412ca19bb

The font name is encoded in the font's charset given by \fcharset.

Change-Id: Id9520649a1eb3b55f4314e140abda7399f23d925

...by blacklisting the problematic service

Change-Id: I524a7c7af2cb374911db7b204021c3d2bcd1fdd6

...as test code using gb_CppunitTest_use_vcl is implicitly run with Solar Mutex locked

Change-Id: I480b4bcce7c6a94922019679099b0883b3ee1030

Change-Id: I5c6bd3ea267f1ea84b46e46aa508a27d00903347

Change-Id: Id8acd1bda30156da8cf5f61537f76f778e1b9c74

Change-Id: If4ad2fe763bffdb64119f7f2a5797aae588fbbf8

Change-Id: Ie487d86b95f49812cd2f4620d6d652b7422e6139

Change-Id: I5e90d51440afa4e317bc07ccb937f606edbc9eb9

Change-Id: I86bb00f134aaf95a48ac0a5d594c632d03f0e9d5

Project: help  179e4d655622b1926a2de0e8bc93627961fcc3c7

... to prevent confusion with our internal usage.

Change-Id: I273b80882cbe5029d04ad754c8b0636f5c59a4f6

Change-Id: Ic4da6180e4457309211ed26ba7d2b8382eec76f3

Change-Id: Ib6048bb694c84a1386d70a72c6e6e942b246a80d

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

Change-Id: I200520a28335fb62cecb91175fc6cefc2cfb51ec

Change-Id: I08e112b3816797a848ae9d16fa7002a67c12fc3d

Change-Id: Ic9e44d0050413c9225b030a4be6f71f5adc654fc

Change-Id: I6496a16c4d6791af43a67dae57b9ee218c3444fe

Change-Id: I01f2576e9d8f6a2e677d1fb08097bc81f15bfbe0

Change-Id: I34134f75ac5571a635256d349bf5a2f67ef8ef06

Change-Id: Ibc8a9155e0d51d87aeab04bb559cfb2e92ba4cf1

Change-Id: Ic1521ad9a67c9930e2e4561eacb1e78905310613

Change-Id: Icff9a0f112c80569a4533d5c0c6e789eec3925ee

Change-Id: I596ec18deca1a7bd85bc49f637fc1765e43d1278

Change-Id: Ib751fe39cca72fe1cfc9789e63f28a00abb9113a

... 27fc4354. Thanks sberg.

Change-Id: Ibf0c7926da38ec3835fd0ab21e1383711bfa6034

Change-Id: Ibd4ded85d5d3e1de8bf12934cbe55210d1983b18

Change-Id: I9143e7fffef6e99d25a0fd87712ed26d2d42116e

Change-Id: Ie1f56aed91e7cbfc59e254a111991f958e9a1607

See https://bugs.freedesktop.org/attachment.cgi?id=100839 and other comments

Change-Id: I1187b171caf54997f5e8850ade4a3fb35ad9ec29

Change-Id: I304c7d7157c4167e7fe33af259e732865900d4ca

Change-Id: I1d8af400810b9ffd4586320c706a1f00ef1c1369

a5f62d96 would had liked to let
usage="DATE_TIME" formatindex="55" define the default format of that
usage, which wasn't possible. There is no reason to prevent this.

Change-Id: Ibef453c8a07aa03b0a8bb626b9cf71d362be0699