https://bugs.documentfoundation.org/show_bug.cgi?id=47679
Caolán McNamara <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #13 from Caolán McNamara <[email protected]> --- I don't think comments #9 and '10 are a starsymbol vs opensymbol thing, or related to the fontcvt.cxx conversion tables. I think its an issue with the editengine rtf export which is used for this copy and paste route. (and if you copy into another drawing edit box then ODF is used, not RTF) In ImpEditEngine::WriteRTF we write the fonts and the font charset, opensymbol is flagged as a "symbol" font and we write fcharset2 to set the charset as SYMBOL encoding, but when we write the text we always attempt to write it using eDestEnc which is RTL_TEXTENCODING_MS_1252 (0), the characters in this case can be expressed in MS1252 so they are written as 0x80, 0x87, 0x86, 0xbb which is correct for MS_1252 encoding (https://en.wikipedia.org/wiki/Windows-1252) but nonsense for symbol encoding. Its probably an error that we consider OpenSymbol a "Symbol" font as its not the classic "Symbol" font, but its probably also an error for the rtf export to set a fcharset on the font but then ignore that when writing the text. The cheapest thing to do I think it to specifically not write "fcharset2" for opensymbol in the editeng export. Longer term to probably disentangle what a "SymbolFont" is. -- You are receiving this mail because: You are the assignee for the bug.
