https://bugs.freedesktop.org/show_bug.cgi?id=77979
Michael Stahl <mst...@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Whiteboard|bibisectrequest |rtf_filter Resolution|--- |FIXED Assignee|libreoffice-b...@lists.free |mst...@redhat.com |desktop.org | CC| |mst...@redhat.com, | |vmik...@collabora.co.uk Summary|FILESAVE: RTF font styles |FILESAVE: RTF font names |not retained |that contain non-ASCII | |characters lost on export Version|4.1.5.3 release |3.4 all versions --- Comment #10 from Michael Stahl <mst...@redhat.com> --- the fonts have names that are chinese characters, and an associated charset of UTF-8, which the RTF export maps badly to code page 1252: {\f7\froman\fprq2\fcharset0 ????;} this problem did not occur in the old RTF export in OOo 3.3, which produced this: {\f7\fnil\fprq2\fcharset128 \'94\'f7\'3f\'89\'eb\'fc\'4b;} so apparently using a fall-back from UTF-8 to Shift-JIS... we can't really tell which charset should be the target (especially not if we don't have the actual font and don't know what Unicode code-points it covers) so perhaps something like this is the best that can be done. Word apparently does not support \ucN\u...\'.. in font table, so write only the fall-back charset in the font table. came up with something that seems to work mostly, fixed on master. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs