Issue 113851 - Chars from "Symbol" font incorrectly exported to PDF
Summary: Chars from "Symbol" font incorrectly exported to PDF
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 3.3 Beta 1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
Keywords: regression
: 114629 (view as issue list)
Depends on:
Blocks: 92011 113586 111112
  Show dependency tree
Reported: 2010-08-13 02:21 UTC by tab
Modified: 2013-08-07 14:44 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

file with special chars (11.11 KB, text/plain)
2010-08-13 02:24 UTC, tab
no flags Details
pdf export by OO3.2 (27.98 KB, text/plain)
2010-08-13 02:29 UTC, tab
no flags Details
pdf export by OO3.3 --bad (33.17 KB, text/plain)
2010-08-13 02:30 UTC, tab
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tab 2010-08-13 02:21:23 UTC
SpeCh.odt is rendered properly in pdf under OO3.2 --SpeCh32.pdf;
But special chars get changed under OO3.3 --SpeCh33.pdf
Comment 1 tab 2010-08-13 02:24:29 UTC
Created attachment 71084 [details]
file with special chars
Comment 2 tab 2010-08-13 02:29:02 UTC
Created attachment 71085 [details]
pdf export by OO3.2
Comment 3 tab 2010-08-13 02:30:41 UTC
Created attachment 71086 [details]
pdf export by OO3.3 --bad
Comment 4 michael.ruess 2010-08-18 15:37:42 UTC
MRU->PL: the document contains some characters from Symbol font. These are
exported incorrectly to PDF. Regression from 3.2.1 where it worked fine.

MRU->HI / PL: Showstoppper?
Comment 5 philipp.lohmann 2010-08-18 16:38:37 UTC
@hdu: please have a look

looks like "Symbol" matches another font now; in 3.2 the PDF builtin font gets
used. Are you sure that the CheckBox "Embed standard fonts" was not checked in
the PDF export dialog ?
Comment 6 philipp.lohmann 2010-08-18 17:03:19 UTC
Bad effect on Mac, too. Here the builtin Symbol font is actually taken, but the
glyphs output are wrong. Maybe a separate problem though.

Changing platform to "All"
Comment 7 2010-08-18 17:47:43 UTC
The problem on Mac could be issue 92011, the original problem on other platforms could be the new 
OpenSymbol (issue 105084, issue 105085, issue 106815) and the subsequent issue 113586. Complex as 
these matters always are I'll have to debug into it to confirm that suspicion.
It would be interesting to know if it helps if the system-wide OpenSymbol gets deinstalled.
Comment 8 2010-08-19 13:35:07 UTC
It showed that the problem still existed even on systems where the issues mentioned where not 
immanent. The remaining root cause was that the text-encoding converters for single byte charsets such 
as the ones employed for the PDF base14 fonts did not handle "symbol aliasing" from U+F0XX -> S+00XX

Extending these converters to allow symbol-aliasing for the symbol-charsets (symbol and dingbats) 
solves the problem. Done in CWS ooo33gsl06.
Comment 9 2010-08-19 14:30:00 UTC
@mru: please verify in CWS ooo33gsl06
Comment 10 michael.ruess 2010-08-20 07:41:40 UTC
Verified fix in CWS ooo33gsl06.
Comment 11 michael.ruess 2010-09-03 13:14:55 UTC
Checked fix in OOO330m6.
Comment 12 eric.savary 2010-09-21 09:32:27 UTC
*** Issue 114629 has been marked as a duplicate of this issue. ***
Comment 13 eric.savary 2010-09-21 09:33:11 UTC
*** Issue 114629 has been marked as a duplicate of this issue. ***