Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451512 - Open office math wont print or export to pdf properly
Summary: Open office math wont print or export to pdf properly
Alias: None
Product: Fedora
Classification: Fedora
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-15 04:59 UTC by Cameron Cross
Modified: 2008-06-16 08:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-06-16 08:02:32 UTC

Attachments (Terms of Use)
pdf of printer output (deleted)
2008-06-15 04:59 UTC, Cameron Cross
no flags Details

System ID Priority Status Summary Last Updated 21999 None None None Never

Description Cameron Cross 2008-06-15 04:59:48 UTC
Description of problem:
Open office math wont print corectly

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Write a formula sheet
2.attempt to print.
Actual results:

Everything is mixed up all over the place. see attached pdf
Expected results:
it simply prints the formulas

Additional info:

Exporting to pdf has the same problem

Comment 1 Cameron Cross 2008-06-15 04:59:48 UTC
Created attachment 309385 [details]
pdf of printer output

Comment 2 Caolan McNamara 2008-06-15 10:05:30 UTC
Use, tools->options->math->settings and disable the print options for 
title row, formula text and borders.

Maybe I should just change to defaults in fedora to disable these by default.

Comment 3 Caolan McNamara 2008-06-16 08:02:32 UTC
I'll set better defaults for future versions of Fedora, in the meantime the
options can be manually changed to get a better result

Note You need to log in before you can comment on or make changes to this bug.