Issue 24868 - PDF does not export ATM CE fonts at all
Summary: PDF does not export ATM CE fonts at all
Status: CLOSED DUPLICATE of issue 10218
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: hdu@apache.org
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-27 18:25 UTC by lmc
Modified: 2006-01-02 15:12 UTC (History)
1 user (show)

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

Attachments
Correct PDF with Arial fonts. (46.69 KB, application/pdf)
2004-01-27 18:26 UTC, lmc 		no flags Details
Uncorrect PDF with original postscript fonts (GillSansCE) (7.75 KB, application/pdf)
2004-01-27 18:27 UTC, lmc 		no flags Details
Original OpenOffice file in GillSanCE font. (8.15 KB, application/vnd.sun.xml.writer)
2004-01-27 18:28 UTC, lmc 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description lmc 2004-01-27 18:25:12 UTC 
I have bought postscript version of Central European fonts (GillSansCE) directly
from Linotype.com. 

Everything works fine, all documents can be printed, but export to PDF does not
work correctly.

Any document, written with Czech alphabet and converted into PDF has a sign of
"?" instead of the correct Czech character. But usual Windows-default TrueType
Arial works fine even for Czech character in PDF.

Please help, this is a very unpleasant surprise!!
Comment 1 lmc 2004-01-27 18:26:29 UTC 
Created attachment 12750 [details]
Correct PDF with Arial fonts.
Comment 2 lmc 2004-01-27 18:27:45 UTC 
Created attachment 12751 [details]
Uncorrect PDF with original postscript fonts (GillSansCE)
Comment 3 lmc 2004-01-27 18:28:58 UTC 
Created attachment 12752 [details]
Original OpenOffice file in GillSanCE font.
Comment 4 lmc 2004-01-27 18:33:57 UTC 
I can see now,

the file desatero-gill.pdf should be formated in GillSans font, but is not; it
seems to me the font is NOT included within the PDF at all...
Comment 5 christof.pintaske 2004-01-28 10:27:26 UTC 
cp->pl: handling of type1 on windows is not implemented, isn't it ?
Comment 6 philipp.lohmann 2004-01-28 11:42:59 UTC 
pl->hdu: No it's not. You have already an issue for this problem ?
Comment 7 hdu@apache.org 2004-01-28 13:21:50 UTC 
Yes, the Type1 font files are not available with Win32's text API. In other
words the mapping of a device context to a font file's content is currently not
known to OOo, so it cannot embed its data. One has to use ATM's API for this,
which hasn't been implemented yet for our Win32 platform OOo.
Comment 8 vdvo 2005-12-29 03:04:09 UTC 
Dupe of issue 10218?
Comment 9 hdu@apache.org 2006-01-02 15:12:16 UTC 
> Dupe of issue 10218

Yes. Thanks!

*** This issue has been marked as a duplicate of 10218 ***
Comment 10 hdu@apache.org 2006-01-02 15:12:45 UTC 
Closing duplicate.