https://bugs.freedesktop.org/show_bug.cgi?id=52229

--- Comment #9 from Roman Eisele <[email protected]> ---
@ stfhell:
Wow, thank you very much for your investigation!


So, the question is: what to do now about this bug?

Issue (1) is, according to stfhell’s research (and my tests), a bug in Adobe
Reader, not in LibO. Maybe we could file a new LibO bug report, namely an
enhancement request, to make the RTF reader more tolerant about this kind of
wrong text encoding, in order to “fix” Adobe Reader’s wrong Unicode encoding;
but I don’t know if it is worth the work which would be necessary.

Issue (2) was a real bug in LibO, but seems fixed in the current LibO versions,
so RESOLVED/WORKSFORME.

Issue (3) is not really a bug in LibO -- there is just no font
“BAAAAA+TimesNewRomanPSMT”. Maybe we could file a new LibO bug report, again an
enhancement request, to add some font name guessing (this would be not too
difficult in cases like these); I say a new bug report, because this would be
really a new feature, not a bug fix.


Therefore I would suggest to close the present bug as RESOLVED/WORKSFORME
(according to issue (2), the most important one), and, if some of you want, to
file the enhancement requests for (3) and maybe for (1). I can do that, if
nobody else wants to do so.

Any objections? thoughts? questions? ;-)

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to