fdo#79384: RTF import: fix literal Shift-JIS text

This is a variable-length encoding, and the second byte may be a RTF
syntax character like \, {, }.

Change-Id: I813ccafda18388af3bf05eb7ce9a0253c627b1c4
(cherry picked from commit 061190a62fcdbfb3a0b266d5afffbd257a3e692e)
fdo#79384: replace the work-around with a different one

Word will reject Shift-JIS following \loch, but apparently OOo could read
and (worse) write such documents, so accept Shift-JIS regardless of run
charset type.

Change-Id: Ib181956e9f218548a52037dd76fa1d3ecdc006bd
(cherry picked from commit d71387ca81b61416b9a7b82cd6cf67d496b81fc2)
RTF import: fix handling of \loch \hich \dbch \ltrch \rtlch

The logic is not immediately obvious from the RTF spec; let's do what
the editengine RTF import does, but without the unnecessary complexity.

Change-Id: I60e69130e6e5aed1f5d237f64b1656c3141e402a
(cherry picked from commit 36246aa9fb57c9fe4e546c91a8274d8828b1424e)
(related: bnc#823675) RTF import: get rid of hacks for \f in LISTLEVEL

These weird hacks are apparently needed only because the \loch \hich
\dbch were mapped wrongly; for the list level destination it's only
important that the existing fonts are not overwritten.

Change-Id: Ie2b9adf332b74c2744e9b1dbc4e878638e5ee078
(cherry picked from commit c087b60b0dd70c4a711ba1b4d556206a136fa468)