Bug 47235

Summary: IPA-character stops creation of pdf-file.
Product: DejaVu Reporter: Schneider <hiat>
Component: SansAssignee: Deja Vu bugs <dejavu-bugs>
Status: NEW --- QA Contact:
Severity: major    
Priority: medium CC: hiat
Version: unspecified   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Word-doc-file with IPA-example.

Description Schneider 2012-03-12 07:45:47 UTC
Created attachment 58321 [details]
Word-doc-file with IPA-example.

The Adobe Distiller (v. 7.1) stops with the following message when trying to convert the attached Word-file ("PDF_IPA_DejaVu_Sans_Test_1.doc") to pdf:

=================================================================
%%[ ProductName: Distiller ]%%
DejaVuSans not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: show ]%%

Stack:
()


%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
=================================================================

"DejaVuSans not found, using Courier.". I expected here "DejaVu Sans" instead of "DejaVuSans". The "DejaVu Sans"-font (v. 2.33) ist installed on my pc. On the screen it looks perfect... 

Is this an error in the "DejaVu Sans"-Font? Or is it a problem with the distiller? 

The PDFCreator stops as well converting this doc-file to pdf, but without any helpful protocol. The LibreOffice swriter stops "printing" to pdf via distiller as well (with a similar error-message). But the LibreOffice-integrated pdf-exporter produces a pdf-file from this doc-file. It is unfortunately (foreseeable) unusable, because the spaces between characters are wrong - as seen before on the screen. 

Several years before (2008?) I exported a this very same IPA-Transkript (in an other context) with an older "DejaVu Sans"-Version (2.2x?) to PDF (same distiller-version) without any problems. 

I use: Windows XP, Word 2002, all servicepacks. Adobe distiller 7.1.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.