Change-Id: I55895a1b55696ed20e3fcdcafa919879bf304398

Change-Id: I63c88bcb41a48142f8b3c20ff4d66ae28811411b

Change-Id: Ib08f5ab8e6155f1b9be100377657678b8c480060

Text flow is perhaps not intended to specify rotation, created data may misbehave on
other applications, and there is no reason for this unnecessary special case.
(Especially obvious because there is no text flow that causes 180 deg rotation.)
Theoretically, you could delete all three if-cases as in the earlier version of this patch,
but that ?could? come at the cost of backwards compatibility.

Change-Id: I0b1cac78e549c2126d7e45298629e28fc76ac95d
Signed-off-by: Lennard <Wasserthal@nefkom.net>
Reviewed-on: https://gerrit.libreoffice.org/1165Reviewed-by: Bosdonnat Cedric <cedric.bosdonnat@free.fr>
Tested-by: Bosdonnat Cedric <cedric.bosdonnat@free.fr>

OUString are immutable so these api, contrary to what happen
with String, do not change the object but create a new copy

Change-Id: Ib48a8d11e485d4b8556f4427880aaaca32d4e82c

Change-Id: I848ac4d934ffde0ae9c4b8b674fcb46c7bd17769

Change-Id: I47e206350331e3edeef9edcb0514eacb66db7c07

It added code that already was there.

Change-Id: I766184e4996a4abcd3f2b383c1aae3b558954fbd

Change-Id: Iff20613231058db92d65cfecc5e4b16dd5395589

Change-Id: Iebf4017ce4c2c48389716eac1bbf7f386ac7a296

Change-Id: I7d64d117183738b86d1869ed629d73675de9c679

Change-Id: Ie02dc3511e262a3b13df38ddbe0b3136f291ac9e

Change-Id: If11b8752c3aa21554c3ee06de07d63639695e284

Change-Id: I20f080b76b864208f0706bef9e87cb299f3845aa

Change-Id: I7e107c37c43a8c9d868b579a2c389de558594a77

Change-Id: Ib4d9175ce4661140a147962b8f45be40f800d85a

Change-Id: Ifcdca197bd2f99a9dddacd82e77ec07d18519a23

Change-Id: I3c445a20e2c8d17c4fc68360dd896d902be46e56

Change-Id: I9979927af016f0b782ae9481a6207649f6455558

Change-Id: I53e5e60f59739bdcedb6e7b13006850e0e5b22c0

Change-Id: I364b1ac36f999f4309b3aab2ef0c55ff2147ef43

plus convert GetKeyWord() and GetStandardName and some
more zforlist implementation conversion

Change-Id: I64abe35a4875d84518a1904ef3121269b79a6df0

Change-Id: Iacd7a20a49c40b6f4db07a14a17cc6301eeb086d

Change-Id: I85d7fd7733814c60a048a7f87d43fbcbb83b0eb0

Change-Id: I9766872069ef5c2ee740dcbd8ac288aa8063a752

Change-Id: Idc7379daf25a226622e5599124df2ab68b98902a

Change-Id: I83f7794a3cc413c7720ad605a22c00efe966e1a5

Change-Id: Ie498b7603cd493b00698c2fa1858ba9a77832ea3

Change-Id: Ib6c6d1a31b037b6e687b063257a9dc813ff3be91

Change-Id: I03aa6278ee3cbbb85ffa9cbe5437493dbc7e463b

Change-Id: I07d379c9a38a60b5950ff4e2970e46f18cac2de2

the original code was converting one character at the time from
whatever codepage of the input stream to unicode just to be able
to substitute the 'euro' character that apparently is somehow
not converted properly (why this is hacked here rather than fixed
in the code page converted is another story)

the change consist in translating the 'native' euro character in whatever
the converter think it should be, then converting the whole string at once
to Unicode and finally replace the 'bad' euro character representation
with the the 'good' one.

This turn the allocation pattern for O(N) to O(1) where N is the length
of the string.

Change-Id: Ie7ffeb813346953f539cf6dc34b43f890d8b970f

Change-Id: Ib849ffb115f7501d90dd56356c56c90edf9fd5e0

Change-Id: Ie7cb50605d9e1e1a21d50a962bdc9b9880c8d06a

Change-Id: Ie4ab10b81897ac32228dc1267b3da00250ff82ea

Change-Id: Ia865ef3859bb120578e2d92a866ddadbeaa943df

Change-Id: I95cd8e97044cd5a65500d3a674995f417c4f2e29

Change-Id: Ideb89b8ced5c3ac2b07a7e270b90e92beef02aad

Change-Id: Ife0fbb28ba2686a9a251757e109f2ac451296192

Change-Id: I8d9e0d01642c04ca7742b68e8926b3966418f841