Bug 126791 - Loading templates in OpenOffice.org Writer doesn't work
Summary: Loading templates in OpenOffice.org Writer doesn't work
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
(Show other bugs)
Version: 2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-26 21:40 UTC by Dee-Ann LeBlanc
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-25 19:45:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dee-Ann LeBlanc 2004-06-26 21:40:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040518 Firefox/0.8

Description of problem:
In OpenOffice.org Writer, when I select Format -> Styles -> Load,
select all of the checkboxes on the bottom, choose From File, navigate
to the file to load the template from (whether in Word or OOo format),
and then load the template, everything seems to work. However, the
styles available in that template are not available in the Stylist,
signifying that perhaps the template didn't load at all.

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

How reproducible:

Steps to Reproduce:
(see above)

Expected Results:  When I do as I described, I should be able to
choose the Custom Styles portion of the Stylist and see the styles I
know are within this template listed there.

Additional info:

Comment 1 Dan Williams 2004-09-18 15:54:35 UTC
should be fixed with what will be 1.1.2-5, cannot reproduce this there.

Comment 2 Dan Williams 2004-09-25 19:45:52 UTC
Please test with the openoffice.org-1.1.2-5 RPMs in Rawhide, it should
be fixed in that version.  If the problem persists with that version,
please reopen this bug.  Thanks!

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