Issue 8155 - Docbook and XHTML Save As Failure
Summary: Docbook and XHTML Save As Failure
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 643
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: aidan.butler
QA Contact: issues@sw
URL:
Keywords: oooqa
: 8038 8413 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-10-08 18:08 UTC by Unknown
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

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

Attachments
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 Unknown 2002-10-08 18:08:19 UTC 
P4 1.6, 512MB, RH8, Java 1.4.1

When saving as Docbook or as XHTML, no errors are given, but the resulting files
are 0k.
Comment 1 openoffice 2002-10-08 18:24:25 UTC 
dvo->aidan: I think this is yours... :-)
Comment 2 aidan.butler 2002-10-09 10:19:25 UTC 
aidan->pcompton42 I have tested this with Redhat 6.2, and it worked
fine. It will take time to set up a RH8 test env to confirm.
Comment 3 wilddev 2002-10-14 11:28:07 UTC 
This issue also happens on RH 7.2 and 7.3 I have a nice document setup
and try to export it to DocBook and 0 byte file is the result.
Comment 4 aidan.butler 2002-10-14 12:04:58 UTC 
The problem you are seeing could be a bug that has recently been
fixed. The '&' charactor in the stream is not being escaped which
results in the following occuring.
1. FlatXml: The FlatXml stream is written out correctly producing a
valid file but the '&' is not replaced with "&". When the file is
opened in OpenOffice, the parser is recognises the '&' as an incorrect
entity so therefore throws an exception and does not display the Doc.
2. DocBook and XHTML: When saving the Docbook filter takes the OOo xml
stream and performs an XSLT translation on it. The result is then
parsed, but because the entities have not been declared properly, the
filter fails.

I will make the corrected jars (XMergeBridge.jar and XFlatXml.jar
)available in the XMergeInstall.jar package on
   http://xml.openoffice.org/xmerge/downloads 

The same applies to '<' and '>'
If you attach the document, I will test it.
Comment 5 wilddev 2002-10-15 02:06:54 UTC 
I spoke to Sander Vesik <Sander.Vesik@Sun.COM> about this issue and he
alerted me to the fact that my using jre-1.3.1 could be the problem
(the website suggests 1.3 is the minimum). I've since upgraded to
jre-1.4.0 and am able to export successully to docbook xml. Thanks for
the good work, I'll try to keep bug reports flowing.

I'll test out the new Xmerge packages
Comment 6 wilddev 2002-10-15 02:10:50 UTC 
Oh, I realize also that the Xmerge webpage clearly states jre-1.4 as a
requirement, I was referring to other notes I found about java support
in 1.0.1 OO install.
Comment 7 wilddev 2002-10-15 02:15:52 UTC 
Oh, I realize also that the Xmerge webpage clearly states jre-1.4 as a
requirement, I was referring to other notes I found about java support
in 1.0.1 OO install.
Comment 8 caolanm 2002-10-15 10:57:40 UTC 
changing component from word processor to xml, xmerges parent group
Comment 9 brant 2002-11-24 17:58:03 UTC 
*** Issue 8038 has been marked as a duplicate of this issue. ***
Comment 10 brant 2002-11-24 17:59:57 UTC 
This issue is in 643c on Windows XP still.
Comment 11 brant 2002-11-24 18:01:33 UTC 
*** Issue 8413 has been marked as a duplicate of this issue. ***
Comment 12 aidan.butler 2003-06-20 14:34:01 UTC 
aidan: DocBook no longer uses XMerge, so this problem should have gone
away. There is stull a requirement for jre1.4 and greater
Comment 13 jogi 2005-04-14 13:03:58 UTC 
verified
Comment 14 jogi 2005-04-14 13:04:29 UTC 
closing