Issue 72697 - STIX OpenType fonts not recognized
Summary: STIX OpenType fonts not recognized
Status: CLOSED DUPLICATE of issue 43029
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 1.0.0
Hardware: PC Unix, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2006-12-18 10:04 UTC by wsvries
Modified: 2006-12-20 14:16 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description wsvries 2006-12-18 10:04:21 UTC
OO-writer v2.0 build 2.0.0.1 on Linux KDE, Suse 10.0
Installed test STIX fonts (STIX: app. 7000 scientific characters and symbols to
be distributes for free in 2007, www.stixfonts.org).
Writer cannot recognize them. Other applications (e.g. Firefox) work OK with the
fonts.
The fonts are OpenType based on Type1. Opentype based on on TrueType does work
OK, but that is not what we want to distribute.
Test font files also work OK with OO-writer under WinXP.
Wim de Vries
member STIX technical committee
Comment 1 michael.ruess 2006-12-19 12:26:17 UTC
Could you please attach a sample font which will not be recognize, to this issue?
It will be essential for reproducing the bug. If you do not want to share,
please send directly to mru@openoffice.org. Thanks a lot!
Comment 2 hdu@apache.org 2006-12-20 13:17:51 UTC
Because CFF-glyph subsetting is not yet implemented in OOo, it cannot print with
these fonts on UNX platforms, yet. Writer will only use fonts it can print.

Same root cause as in issue 43029.

*** This issue has been marked as a duplicate of 43069 ***
Comment 3 lohmaier 2006-12-20 14:13:40 UTC
probably a typo in the issue number, please recheck.
Comment 4 lohmaier 2006-12-20 14:14:27 UTC
ah, the comment included the right one, reopen to set the correct one..
Comment 5 lohmaier 2006-12-20 14:15:15 UTC
setting the correct ID

*** This issue has been marked as a duplicate of 43029 ***
Comment 6 lohmaier 2006-12-20 14:16:30 UTC
closing duplicate.